Question

5

How to see why "snapd.refresh.service" failed to start on startup?

rated 0 times [ 5] [ 0] / answers: 1 / hits: 3619 / 1 Year ago, tue, february 7, 2023, 3:19:15

After upgrading to snapd version 2.0.8 I have noticed that I get an error message about snapd.refresh.service failing to start on startup, the error tells me which command to run in order to see why it is failing, however the message disappears so quickly that I can't see what that command is.

I understand that this is probably a bug, and I plan to report it as such, however I was wondering if anybody had any idea of the command it could have been? I think it might have been a systemd command but I'm not entirely sure. Is there somewhere where the message would have been logged (I have already tried syslog and dmesg but it is not there)?

I am running Ubuntu GNOME 16.04 with GNOME 3.20.

For anyone who is interested there is already a report filed on the matter here.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ickump

Add To Favorites

Follow

Total Points: 234

Total Questions: 124

Total Answers: 111

Location: Jordan

Member since Fri, Apr 8, 2022

2 Years ago

answered 1 Year ago rinstracte · Accepted Answer

You can also use systemctl status to look at the tail of the logs, plus any other information that systemd has about that service:

systemctl status snapd.refresh.service

For example:

$ systemctl status lightdm.service   

● lightdm.service - Light Display Manager

   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)

  Drop-In: /etc/systemd/system/lightdm.service.d

           └─override.conf

        /lib/systemd/system/display-manager.service.d

           └─xdiagnose.conf

   Active: active (running) since Sun 2016-06-12 09:27:09 IST; 2 days ago

     Docs: man:lightdm(1)

 Main PID: 2218 (lightdm)

   CGroup: /system.slice/lightdm.service

           ├─2218 /usr/sbin/lightdm

           └─2245 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch



Jun 12 09:27:12 host lightdm[2278]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory

Jun 12 09:27:12 host lightdm[2278]: PAM adding faulty module: pam_kwallet5.so

Jun 12 09:27:13 host lightdm[2278]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)

Jun 12 09:27:28 host lightdm[2490]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory

Jun 12 09:27:28 host lightdm[2490]: PAM adding faulty module: pam_kwallet.so

Jun 12 09:27:28 host lightdm[2490]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory

Jun 12 09:27:28 host lightdm[2490]: PAM adding faulty module: pam_kwallet5.so

Jun 12 09:27:28 host lightdm[2490]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "muru"

Jun 12 09:27:36 host lightdm[2490]: pam_unix(lightdm:session): session opened for user muru by (uid=0)

Jun 15 05:53:19 host systemd[1]: [/etc/systemd/system/lightdm.service.d/override.conf:2] Executable path is not absolute, ignoring: true

Information of note:

state of the service (enabled/disabled) as well as the state set by the vendor (package, in this case)

location of service file, plus locations of any overriding files (the "Drop-In" files)

PID, cgroup and child processes