Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

snapd issues #35

Open
mirkobrombin opened this issue Dec 25, 2022 · 3 comments
Open

snapd issues #35

mirkobrombin opened this issue Dec 25, 2022 · 3 comments
Labels

Comments

@mirkobrombin
Copy link
Member

mirkobrombin commented Dec 25, 2022

Reports from Discord:

error: cannot communicate with server: Post "http://localhost/v2/snaps/hello-world": dial unix /run/snapd.socket: connect: connection refused
Job for snapd.service failed because the control process exited with error code.
See "systemctl status snapd.service" and "journalctl -xeu snapd.service" for details.
snapd.service: Triggering OnFailure= dependencies
snapd.service - Snap Daemon
     Loaded: loaded (/lib/systemd/system/snapd.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-12-25 08:04:11 UTC; 1min 4s ago
TriggeredBy: \C3\97 snapd.socket
    Process: 1208 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
   Main PID: 1208 (code=exited, status=1/FAILURE)
        CPU: 82ms

Dec 25 08:04:11 vanilla systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
Dec 25 08:04:11 vanilla systemd[1]: Stopped Snap Daemon.
Dec 25 08:04:11 vanilla systemd[1]: snapd.service: Start request repeated too quickly.
Dec 25 08:04:11 vanilla systemd[1]: snapd.service: Failed with result 'exit-code'.
Dec 25 08:04:11 vanilla systemd[1]: Failed to start Snap Daemon.

Related apparmor log:

Dec 25 08:18:06 vanilla apparmor.systemd[3596]: Restarting AppArmor
Dec 25 08:18:06 vanilla apparmor.systemd[3596]: Reloading AppArmor profiles
Dec 25 08:18:06 vanilla apparmor.systemd[3603]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3604]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3602]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3605]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3606]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3608]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Dec 25 08:18:06 vanilla apparmor.systemd[3607]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3630]: AppArmor parser error for /etc/apparmor.d/lsb_release in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3633]: AppArmor parser error for /etc/apparmor.d/nvidia_modprobe in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3637]: AppArmor parser error for /etc/apparmor.d/sbin.dhclient in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3641]: AppArmor parser error for /etc/apparmor.d/usr.bin.man in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3645]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3649]: AppArmor parser error for /etc/apparmor.d/usr.sbin.cupsd in profile /etc/apparmor.d/tunables/global at line 15: Could not open 'tunables/home'
Dec 25 08:18:06 vanilla apparmor.systemd[3651]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Dec 25 08:18:06 vanilla apparmor.systemd[3596]: Error: At least one profile failed to load
Dec 25 08:18:06 vanilla systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
@mirkobrombin mirkobrombin converted this from a draft issue Dec 25, 2022
@mirkobrombin mirkobrombin moved this from Todo to In Progress in 22.10 First Release Dec 25, 2022
@mirkobrombin
Copy link
Member Author

After a further investigation, I found many issues:

  • the ABRoot files hierarchy is not supported (can be fixed with proper arguments during the build process)
  • libudev.so.1 is not being loaded despite available in the system
  • the snapd installation is missing some files in the apparmor profiles path

since this will take more time, I'll postpone the task after the stable and disable that option in the First Setup.

@mirkobrombin mirkobrombin moved this from In Progress to After stable (discussing) in 22.10 First Release Dec 25, 2022
@devajmeireles
Copy link

After a further investigation, I found many issues:

  • the ABRoot files hierarchy is not supported (can be fixed with proper arguments during the build process)
  • libudev.so.1 is not being loaded despite available in the system
  • the snapd installation is missing some files in the apparmor profiles path

since this will take more time, I'll postpone the task after the stable and disable that option in the First Setup.

Hey! Mirko, you is able to see a solution for that?

@mirkobrombin
Copy link
Member Author

ABRoot now supports systemd during the transaction but snapd need to be repacked to change the original snaps installation path since the root is too small.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: After stable (discussing)
Development

No branches or pull requests

2 participants