Closed MDAR closed 1 year ago
Trying this once more, I spotted this in the output while installing SnapD again
Setting up apparmor (2.13.2-10) ...
Created symlink /etc/systemd/system/sysinit.target.wants/apparmor.service → /lib/systemd/system/apparmor.service.
Reloading AppArmor profiles
AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/usr.bin.man at line 47: Could not open 'local/usr.bin.man'
AppArmor parser error for /etc/apparmor.d/usr.bin.man in /etc/apparmor.d/usr.bin.man at line 47: Could not open 'local/usr.bin.man'
Error: At least one profile failed to load
I thought the same had just happened to an Odroid C2 that I had to update for a customer, but it turned out that Velbus-TCP just needed enabling again
snap enable velbus-tcp
As referenced in the issue above, nobody else can replicate this, so it must have been an anomaly with a series of updates.
I've setup six (Odroid C4) machines from scratch today and every one was perfect.
Hi
I updated a machine to the latest Debian version and Snap Velbus-TCP appeared to stop working.
Snap reported that it was running, but nothing could connect to the defined ports (as they have been for the last year)
snap get velbus-tcp -d
Would return the correct configuration, but Angry IP scanner could not see the open ports.As a "bull in a china shop" approach, I eventually removed / purged all traces of SNAPD and started again.
This revealed something more insteresting.
When I tried to install the Velbus-TCP snap package, I got this error.
Have you got any ideas what I should do to resolve this?
FYI
I am running an Odorid C4 with the latest version of DietPi
for now, I have rolled back to using Velserv.
The script I use to install SNAPD and Velbus-TCP is here
www.mdar.co.uk/dl/velbus/velbus-tcp.sh
I have tried these commands and got these errors
This is what
systemctl status snapd
has to say for itselfForcing an installation of Version 1.6.0 did not get me any futher