Eos-update-notifier.service error

General system Newbie
1

Greetings lovely community,

I uninstalled the eos-update-notifier package some time ago since I update my system at least once a day anyways. I was recently going through some of my logs trying to troubleshoot a possible wireplumber issue, when I stumbled upon this error that I pulled from Gnome Logs:

12:03:02 PM systemd: Failed to start EOS update notifier service.
12:03:02 PM (notifier): eos-update-notifier.service: Failed at step EXEC spawning /usr/bin/eos-update-notifier: No such file or directory

Screenshot from 2022-07-07 13-33-28

I guess when I had eos-update-notifier installed, it had a service running checking for updates, but since I’ve uninstalled it (weeks, if not months ago), it looks like the service still attempts to start even though it’s no longer installed.

I haven’t noticed this to affect anything at all in my system, but I think it’d be a good idea to get rid of it so I am curious what’s the best way to stop/disable or remove the eos-update-notifier.service from my system when eos-update-notifier is already uninstalled or do I just ignore it? Thanks for any help!

2

What say

systemctl --user status eos-update-notifier.service
systemctl --user status eos-update-notifier.timer

?

3 
[scott@EndeavourOS ~]$ systemctl --user status eos-update-notifier.service
Ă— eos-update-notifier.service - EOS update notifier service
     Loaded: loaded (/home/scott/.config/systemd/user/eos-update-notifier.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-07-07 12:03:02 EDT; 1h 42min ago
TriggeredBy: â—Ź eos-update-notifier.timer
    Process: 3955 ExecStart=/usr/bin/eos-update-notifier -systemd (code=exited, status=203/EXEC)
   Main PID: 3955 (code=exited, status=203/EXEC)
        CPU: 857us

Jul 07 12:03:02 EndeavourOS systemd[1018]: Starting EOS update notifier service...
Jul 07 12:03:02 EndeavourOS systemd[3955]: eos-update-notifier.service: Failed to locate executable /usr/bin/eos-update-notifier: No such file or directory
Jul 07 12:03:02 EndeavourOS systemd[3955]: eos-update-notifier.service: Failed at step EXEC spawning /usr/bin/eos-update-notifier: No such file or directory
Jul 07 12:03:02 EndeavourOS systemd[1018]: eos-update-notifier.service: Main process exited, code=exited, status=203/EXEC
Jul 07 12:03:02 EndeavourOS systemd[1018]: eos-update-notifier.service: Failed with result 'exit-code'.
Jul 07 12:03:02 EndeavourOS systemd[1018]: Failed to start EOS update notifier service.

[scott@EndeavourOS ~]$ systemctl --user status eos-update-notifier.timer
â—Ź eos-update-notifier.timer - EOS update notifier runs periodically (weekly) and soon after a reboot
     Loaded: loaded (/home/scott/.config/systemd/user/eos-update-notifier.timer; enabled; vendor preset: enabled)
     Active: active (waiting) since Thu 2022-07-07 11:57:18 EDT; 1h 48min ago
      Until: Thu 2022-07-07 11:57:18 EDT; 1h 48min ago
    Trigger: Mon 2022-07-11 00:00:00 EDT; 3 days left
   Triggers: â—Ź eos-update-notifier.service

Jul 07 11:57:18 EndeavourOS systemd[1018]: Started EOS update notifier runs periodically (weekly) and soon after a reboot.
4

Remove both of these files. You won’t be getting anymore those “Failed to start …” after reboot.

1 Like
5 
[scott@EndeavourOS ~]$ ls ~/.config/systemd/user
eos-update-notifier.service      eos-update-notifier.timer.bak
eos-update-notifier.service.bak  timers.target.wants
eos-update-notifier.timer

Looks like it’s safe to remove 4 (possibly 5?) files in there, correct? (2 of them are backups)

The timers.target.wants is a folder and inside that folder is a file called eos-update-notifier.timer

[scott@EndeavourOS ~]$ ls ~/.config/systemd/user/timers.target.wants
eos-update-notifier.timer
6

Yes, remove them all.

1 Like
7

Done and did a reboot, message errors are gone, thanks!

1 Like
8

Removing those files should do the job, but you could also have done

systemctl --user disable eos-update-notifier.timer

to stop systemd trying to use that timer.
The error message was only showing that systemd tried to use the timer that didn’t exist anymore.

2 Likes
9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.