Here is the output from some snap commands that are probably useful for debugging reasons.
...@...:~$ sudo snap install inadyn
snap "inadyn" is already installed, see "snap refresh --help"
...@...:~$ snap services
Snap Service Startup Current
inadyn daemon enabled inactive
nextcloud apache enabled active
nextcloud mdns-publisher enabled active
nextcloud mysql enabled active
nextcloud nextcloud-cron enabled active
nextcloud php-fpm enabled active
nextcloud redis-server enabled active
nextcloud renew-certs enabled active
snapweb snapweb enabled active
...@...:~$ snap version
...@...:~$ snap list
Name Version Rev Developer Notes
core 16-2.29.3 3443 canonical core
inadyn 0.1 10 snapcrafters -
nextcloud 11.0.5snap2 3685 nextcloud -
pi2-kernel 4.4.0-1030-3 22 canonical kernel
pinano 2.8.7 9 vbota -
snapweb 0.26-10 305 canonical -
wdl-nextcloud 16.04-0.5-6 9 canonical gadget
When I try to edit the configurations and save them using:
sudo pinano $(inadyn.configpath)
I used pinano as snap for the nano-editor, because it was the only one available for the raspberry pi architecture. Do not pay attention on the configurations. I know that they are probably wrong, but one problem at time For the moment I can not save the configurations and have the snap read them.
And the output from the commands you provided:
...@...:~$ sudo journalctl snap.inadyn.daemon.service
Failed to add match 'snap.inadyn.daemon.service': Invalid argument
...@...:~$ sudo systemctl restart snap.inadyn.daemon.service
(This was succefull and did not produce any output, so I am pasting the output from the syslog)
...@...:~$ sudo tail -f /var/log/syslog
Nov 26 20:59:03 nextcloud systemd: Started Service for snap application inadyn.daemon.
Nov 26 20:59:03 nextcloud kernel: [18981.549762] audit: type=1400 audit(1511729943.282:89): apparmor="DENIED" operation="chown" profile="snap.inadyn.daemon" name="/var/snap/inadyn/10/" pid=22015 comm="inadyn" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Nov 26 20:59:03 nextcloud inadyn: Not allowed to change owner of /var/snap/inadyn/10, aborting.
Nov 26 20:59:03 nextcloud systemd: snap.inadyn.daemon.service: Main process exited, code=exited, status=73/n/a
Nov 26 20:59:03 nextcloud systemd: snap.inadyn.daemon.service: Unit entered failed state.
Nov 26 20:59:03 nextcloud systemd: snap.inadyn.daemon.service: Failed with result 'exit-code'.
Nov 26 20:59:03 nextcloud systemd: snap.inadyn.daemon.service: Service hold-off time over, scheduling restart.
Nov 26 20:59:03 nextcloud systemd: Stopped Service for snap application inadyn.daemon.
Nov 26 20:59:03 nextcloud systemd: snap.inadyn.daemon.service: Start request repeated too quickly.
Nov 26 20:59:03 nextcloud systemd: Failed to start Service for snap application inadyn.daemon.
The link you provided probably answers the question why this is happing. Probably the pinano does not have the permissions to write the necessary configurations files (Am I correct???). Is there a way of bypassing this restriction?
Is there a way of resolving that??? In the syslog, I saw the message that your are mentioning. I did not understand what I have to do from the links Although not new to linux, I am really new to snaps and unfortunately did not have the chance to play with them yet