superm1
commented
3 years ago In the unit can you please add --verbose to the execution call and see if it provides more context on the failure?
Closed equaeghe closed 2 years ago
superm1
commented
3 years ago In the unit can you please add --verbose to the execution call and see if it provides more context on the failure?
equaeghe
commented
3 years ago It seems to give exactly the same output. (How do I check that indeed --verbose was used? I used systemctl edit fwupd-refresh.service to modify the unit file.)
superm1
commented
3 years ago Hmm. Presumably that reloads the unit automatically.
Do you by chance have your user directories on NFS or anything else "non-standard"? LDAP?
equaeghe
commented
3 years ago No special setup. Generally typical desktop installation (on a laptop), but of course something must be atypical…
Running /usr/bin/fwupdmgr refresh --no-metadata-check as in the ExecStart line of the unit file works fine. There must be something in the context created by the rest of the unit file that is the cause.
superm1
commented
3 years ago The reason I was asking about NFS/LDAP is I know DynamicUsers in that unit has caused problems for people. I'm at a bit of a loss though. Can you strace the service maybe?
hughsie
commented
3 years ago Okay, feel free to re-open if you have any further details.
equaeghe
commented
3 years ago I looked at the issue again. For some reason, my custom service file (with --verbose added) was not used. Now it was (also including strace). So now using
ExecStart=strace /usr/bin/fwupdmgr refresh --no-metadata-check --verboseThis gave
May 05 13:43:57 TUE023621 systemd[1]: Starting Refresh fwupd metadata and update motd...
░░ Subject: A start job for unit fwupd-refresh.service has begun execution
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit fwupd-refresh.service has begun execution.
░░
░░ The job identifier is 3979.
May 05 13:43:57 TUE023621 strace[237233]: (fwupdmgr:237233): GLib-DEBUG: 13:43:57.967: setenv()/putenv() are not thread-safe and should not be used after threads are created
May 05 13:43:57 TUE023621 systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ An ExecStart= process belonging to unit fwupd-refresh.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
May 05 13:43:57 TUE023621 systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ The unit fwupd-refresh.service has entered the 'failed' state with result 'exit-code'.
May 05 13:43:57 TUE023621 systemd[1]: Failed to start Refresh fwupd metadata and update motd.
░░ Subject: A start job for unit fwupd-refresh.service has failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit fwupd-refresh.service has finished with a failure.
░░
░░ The job identifier is 3979 and the job result is failed.There appears one GLib issue that is new. Please reopen.
superm1
commented
3 years ago Seems that strace didn't add any value to the equation. Can you try to whittle down the extra clauses in the unit to find out what's borking things? I'd start out with taking out DynamicUsers
equaeghe
commented
3 years ago I did not see the issue any more the last few boots. An update of fwupd to 1.5.9 happened, but the first boot after that, I thought the problem was still there. In any case, I'm closing this and can always come back in case the problem turns out to still be present in some way.
mfat
commented
2 years ago This issue still affects me on a fully updated DEBIAN 11.
aleksandaratanasov
commented
2 years ago I have a freshly installed Ubuntu Server 20.04 with the latest cockpit (from the Ubuntu repos) and I am facing this issue too.
:~$ sudo systemctl status fwupd-refresh.service
fwupd-refresh.service - Refresh fwupd metadata and update motd
Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static; vendor >
Active: failed (Result: exit-code) since Tue 2022-04-12 18:53:17 UTC; 12h >
TriggeredBy: fwupd-refresh.timer
Docs: man:fwupdmgr(1)
Main PID: 204262 (code=exited, status=1/FAILURE)If a patch has already provided I would like to ask whether it will be made available for Ubuntu Server 20.04 LTS.
superm1
commented
2 years ago I have a freshly installed Ubuntu Server 20.04 with the latest cockpit (from the Ubuntu repos) and I am facing this issue too.
:~$ sudo systemctl status fwupd-refresh.service fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static; vendor > Active: failed (Result: exit-code) since Tue 2022-04-12 18:53:17 UTC; 12h > TriggeredBy: fwupd-refresh.timer Docs: man:fwupdmgr(1) Main PID: 204262 (code=exited, status=1/FAILURE)If a patch has already provided I would like to ask whether it will be made available for Ubuntu Server 20.04 LTS.
What version of fwupd? Anything in the journal on the failure beyond this?
monster1612
commented
2 years ago on my Ubuntu Server 20.04.4 LTS instance that's also running Cockpit (264 from focal-backports) and version 1.7.5-3 of the fwupd package, I get the same error even if I try to manually start the fwupd-refresh service.
sudo journalctl -xe produces this:the issue, for me, seems to have started roughly 2 days ago.
ealap
commented
2 years ago I also face the same issue after upgrading from Ubuntu 21.10 to 22.04. Modifying the service file by setting the option DynamicUser to no seems to have resolved it for me.
Reverting the value to yes will once again reproduce the issue. I just hope I am not missing out on something important by disabling this option.
daddiofaddio
commented
2 years ago Running Ubuntu Server 20.04 with fwupd version 1.7.5. Same issue as everyone above. Running "sudo journalctl -xe" produces same output as @monster1612. Started 2 days ago. As @ealap mentioned, editing /usr/lib/systemd/system/fwupd-refresh.service and changing "DynamicUser" to "no" appears to resolve the issue for now.
superm1
commented
2 years ago I have a suspicion this is related to the permissions on the files or directories related to this process then. Maybe it's stateful based on an old version being upgraded?
If you guys can please look at /var/cache and /var/lib for fwupd related directories and look at permissions we can compare what is different from a working system.
monster1612
commented
2 years ago I have a suspicion this is related to the permissions on the files or directories related to this process then. Maybe it's stateful based on an old version being upgraded?
If you guys can please look at /var/cache and /var/lib for fwupd related directories and look at permissions we can compare what is different from a working system.
ls -lash /var/cache/fwupd*ls -lash /var/cache/private/fwupdmgr/fwupd* (following symlink)ls -lash /var/lib/fwupd*
cybersi
commented
2 years ago Running Ubuntu Server 20.04 with fwupd version 1.7.5. Same issue as everyone above. Running "sudo journalctl -xe" produces same output as @monster1612. Started 2 days ago. As @ealap mentioned, editing /usr/lib/systemd/system/fwupd-refresh.service and changing "DynamicUser" to "no" appears to resolve the issue for now.
i'm experiencing the same on 20.04 and fwupd 1.7.5. At first I thought I caused it by (auto)removing the libfwupdplugin1 library. I did try reinstalling it but it did not help. Disabling DynamicUser does the trick.
My permissions:
ls -lash /var/cache/fwupd*
0 lrwxrwxrwx 1 root root 16 Apr 18 11:22 /var/cache/fwupdmgr -> private/fwupdmgr
/var/cache/fwupd:
total 4.5M
4.0K drwxr-xr-x 2 root root 4.0K Apr 18 10:01 .
4.0K drwxr-xr-x 13 root root 4.0K Apr 18 11:22 ..
4.4M -rw-r--r-- 1 root root 4.4M Apr 18 10:01 metadata.xmlb
4.0K -rw-r--r-- 1 root root 1.6K Mar 12 23:40 metainfo.xmlb
112K -rw-r--r-- 1 root root 112K Mar 12 23:40 quirks.xmlb ls -lash /var/lib/fwupd*
total 60K
4.0K drwxr-xr-x 7 root root 4.0K Mar 12 23:40 .
4.0K drwxr-xr-x 44 root root 4.0K Mar 12 17:55 ..
4.0K drwx------ 3 root root 4.0K Apr 18 10:01 gnupg
4.0K drwxr-xr-x 3 root root 4.0K Mar 12 23:40 metadata
32K -rw-r--r-- 1 root root 32K Mar 12 23:40 pending.db
4.0K drwxr-xr-x 2 root root 4.0K Feb 25 2021 pki
4.0K drwxr-xr-x 2 root root 4.0K Mar 12 23:40 quirks.d
4.0K drwxr-xr-x 3 root root 4.0K Feb 26 2021 remotes.dCurrent permissions and permissions from working backup dated 4/11/22:
**Current Permissions
ls -lash /var/cache/fwupd*
/var/cache/fwupd:
total 4.5M
4.0K drwxr-xr-x 2 root root 4.0K Apr 15 10:36 .
4.0K drwxr-xr-x 23 root root 4.0K Apr 17 08:52 ..
4.4M -rw-r--r-- 1 root root 4.4M Apr 15 10:36 metadata.xmlb
4.0K -rw-r--r-- 1 root root 1.6K Mar 10 10:52 metainfo.xmlb
112K -rw-r--r-- 1 root root 112K Mar 10 10:52 quirks.xmlb
/var/cache/fwupdmgr:
total 12K
4.0K drwxr-xr-x 3 root root 4.0K Feb 20 2021 .
4.0K drwxr-xr-x 23 root root 4.0K Apr 17 08:52 ..
4.0K drwxr-xr-x 2 root root 4.0K Aug 9 2021 fwupd
ls -lash /var/lib/fwupd*
total 60K
4.0K drwxr-xr-x 7 root root 4.0K Mar 10 10:52 .
4.0K drwxr-xr-x 77 root root 4.0K Apr 12 10:29 ..
4.0K drwx------ 3 root root 4.0K Apr 15 10:36 gnupg
4.0K drwxr-xr-x 3 root root 4.0K Mar 10 10:52 metadata
32K -rw-r--r-- 1 root root 32K Mar 10 10:52 pending.db
4.0K drwxr-xr-x 2 root root 4.0K Feb 20 2021 pki
4.0K drwxr-xr-x 2 root root 4.0K Mar 10 10:52 quirks.d
4.0K drwxr-xr-x 3 root root 4.0K Feb 20 2021 remotes.d**Permissions from working backup - 4/11/22
ls -lash /var/cache/fwupd*
0 lrwxrwxrwx 1 root root 16 Feb 20 2021 /var/cache/fwupdmgr -> private/fwupdmgr
/var/cache/fwupd:
total 4.4M
0 drwxr-xr-x 2 root root 83 Apr 10 20:34 .
4.0K drwxr-xr-x 22 root root 4.0K Feb 26 17:45 ..
4.3M -rw-r--r-- 1 root root 4.3M Apr 10 20:34 metadata.xmlb
4.0K -rw-r--r-- 1 root root 1.6K Mar 10 10:52 metainfo.xmlb
112K -rw-r--r-- 1 root root 112K Mar 10 10:52 quirks.xmlb
ls -lash /var/lib/fwupd*
total 36K
0 drwxr-xr-x 7 root root 125 Mar 10 10:52 .
4.0K drwxr-xr-x 78 root root 4.0K Feb 26 17:45 ..
0 drwx------ 3 root root 109 Apr 10 20:34 gnupg
0 drwxr-xr-x 3 root root 26 Mar 10 10:52 metadata
32K -rw-r--r-- 1 root root 32K Mar 10 10:52 pending.db
0 drwxr-xr-x 2 root root 54 Feb 20 2021 pki
0 drwxr-xr-x 2 root root 10 Mar 10 10:52 quirks.d
0 drwxr-xr-x 3 root root 26 Feb 20 2021 remotes.dCan those of you affected try to add "--verbose" into the launch command in the fwupd-refresh systemd unit? After you do, make sure you do systemctl daemon-reload fwupd-refresh.service. Please share the journal output from the failure with this in place.
superm1
commented
2 years ago I'm wondering if this might actually be https://github.com/systemd/systemd/issues/22737
cybersi
commented
2 years ago Can those of you affected try to add "--verbose" into the launch command in the fwupd-refresh systemd unit? After you do, make sure you do
systemctl daemon-reload fwupd-refresh.service. Please share the journal output from the failure with this in place.
Apr 18 18:13:47 borg-eth systemd[1]: Starting Refresh fwupd metadata and update motd...
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): GLib-DEBUG: 18:13:47.532: setenv()/putenv() are not thread-safe and should not be used after threads are created
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): GLib-GIO-DEBUG: 18:13:47.534: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_fast: "/system/proxy/" (establishing: 0, active: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_fast: "/system/proxy/http/" (establishing: 0, active: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_fast: "/system/proxy/https/" (establishing: 0, active: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_fast: "/system/proxy/ftp/" (establishing: 0, active: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_fast: "/system/proxy/socks/" (establishing: 0, active: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_established: "/system/proxy/" (establishing: 1)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: unwatch_fast: "/system/proxy/" (active: 1, establishing: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_established: "/system/proxy/http/" (establishing: 1)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: unwatch_fast: "/system/proxy/http/" (active: 1, establishing: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_established: "/system/proxy/https/" (establishing: 1)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: unwatch_fast: "/system/proxy/https/" (active: 1, establishing: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_established: "/system/proxy/ftp/" (establishing: 1)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: unwatch_fast: "/system/proxy/ftp/" (active: 1, establishing: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: watch_established: "/system/proxy/socks/" (establishing: 1)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): dconf-DEBUG: 18:13:47.534: unwatch_fast: "/system/proxy/socks/" (active: 1, establishing: 0)
Apr 18 18:13:47 borg-eth fwupdmgr[2755]: (fwupdmgr:2755): GLib-GIO-DEBUG: 18:13:47.535: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’
Apr 18 18:13:47 borg-eth systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Apr 18 18:13:47 borg-eth systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Apr 18 18:13:47 borg-eth systemd[1]: Failed to start Refresh fwupd metadata and update motd.
Can those of you affected try to add "--verbose" into the launch command in the fwupd-refresh systemd unit? After you do, make sure you do
systemctl daemon-reload fwupd-refresh.service. Please share the journal output from the failure with this in place.sudo journalctl -fu fwupd-refresh.service -- Logs begin at Tue 2021-12-14 08:31:44 CET. -- Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: unwatch_fast: "/system/proxy/socks/" (active: 0, establishing: 1) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/http/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/https/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/ftp/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/socks/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): GLib-GIO-DEBUG: 17:56:54.754: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’ Apr 18 17:56:54 borg-eth systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Apr 18 17:56:54 borg-eth systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Apr 18 17:56:54 borg-eth systemd[1]: Failed to start Refresh fwupd metadata and update motd.
Dang nothing too helpful there.
Can you try to prefix it with strace?
cybersi
commented
2 years ago Can those of you affected try to add "--verbose" into the launch command in the fwupd-refresh systemd unit? After you do, make sure you do
systemctl daemon-reload fwupd-refresh.service. Please share the journal output from the failure with this in place.sudo journalctl -fu fwupd-refresh.service -- Logs begin at Tue 2021-12-14 08:31:44 CET. -- Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: unwatch_fast: "/system/proxy/socks/" (active: 0, establishing: 1) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/http/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/https/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/ftp/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): dconf-DEBUG: 17:56:54.754: watch_established: "/system/proxy/socks/" (establishing: 0) Apr 18 17:56:54 borg-eth fwupdmgr[2595]: (fwupdmgr:2595): GLib-GIO-DEBUG: 17:56:54.754: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’ Apr 18 17:56:54 borg-eth systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Apr 18 17:56:54 borg-eth systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Apr 18 17:56:54 borg-eth systemd[1]: Failed to start Refresh fwupd metadata and update motd.Dang nothing too helpful there.
Can you try to prefix it with strace?
Apr 18 18:17:07 borg-eth systemd[1]: Starting Refresh fwupd metadata and update motd...
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): GLib-DEBUG: 18:17:07.798: setenv()/putenv() are not thread-safe and should not be used after threads are created
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): GLib-GIO-DEBUG: 18:17:07.804: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.804: watch_fast: "/system/proxy/" (establishing: 0, active: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_fast: "/system/proxy/http/" (establishing: 0, active: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_established: "/system/proxy/" (establishing: 1)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_fast: "/system/proxy/https/" (establishing: 0, active: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_established: "/system/proxy/http/" (establishing: 1)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_fast: "/system/proxy/ftp/" (establishing: 0, active: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_established: "/system/proxy/https/" (establishing: 1)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_fast: "/system/proxy/socks/" (establishing: 0, active: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.805: watch_established: "/system/proxy/ftp/" (establishing: 1)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.806: unwatch_fast: "/system/proxy/" (active: 1, establishing: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.806: watch_established: "/system/proxy/socks/" (establishing: 1)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.806: unwatch_fast: "/system/proxy/http/" (active: 1, establishing: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.806: unwatch_fast: "/system/proxy/https/" (active: 1, establishing: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.806: unwatch_fast: "/system/proxy/ftp/" (active: 1, establishing: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): dconf-DEBUG: 18:17:07.806: unwatch_fast: "/system/proxy/socks/" (active: 1, establishing: 0)
Apr 18 18:17:07 borg-eth strace[3301]: (fwupdmgr:3301): GLib-GIO-DEBUG: 18:17:07.807: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’
Apr 18 18:17:07 borg-eth systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Apr 18 18:17:07 borg-eth systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Apr 18 18:17:07 borg-eth systemd[1]: Failed to start Refresh fwupd metadata and update motd.I mean to strace the launch command, we should be seeing system calls. Like this:
ExecStart=strace fwupdmgr refresh --verbose
cybersi
commented
2 years ago I mean to strace the launch command, we should be seeing system calls. Like this:
ExecStart=strace fwupdmgr refresh --verbose
This is what I used:
[Unit] Description=Refresh fwupd metadata and update motd Documentation=man:fwupdmgr(1) After=network.target
[Service] Type=oneshot CacheDirectory=fwupdmgr StandardError=null DynamicUser=yes RestrictAddressFamilies=AF_NETLINK AF_UNIX AF_INET AF_INET6 SystemCallFilter=~@mount ProtectKernelModules=yes ProtectControlGroups=yes RestrictRealtime=yes SuccessExitStatus=2 ExecStart=strace /usr/bin/fwupdmgr refresh --verbose
monster1612
commented
2 years ago I mean to strace the launch command, we should be seeing system calls. Like this:
ExecStart=strace fwupdmgr refresh --verbose
I modified the ExecStart command exactly as @cybersi documented, and got similar output.
sudo journalctl -xedaddiofaddio
commented
2 years ago My results are also similar after changing launch to ExecStart=strace fwupdmgr refresh --verbose:
Apr 18 04:09:13 server.io systemd[1]: Starting Refresh fwupd metadata and update motd...
-- Subject: A start job for unit fwupd-refresh.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit fwupd-refresh.service has begun execution.
--
-- The job identifier is 8198.
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): GLib-DEBUG: 04:09:13.113: setenv()/putenv() are not thread-safe and should not be used after threads are created
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): GLib-GIO-DEBUG: 04:09:13.115: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_fast: "/system/proxy/" (establishing: 0, active: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_fast: "/system/proxy/http/" (establishing: 0, active: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_fast: "/system/proxy/https/" (establishing: 0, active: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_fast: "/system/proxy/ftp/" (establishing: 0, active: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_fast: "/system/proxy/socks/" (establishing: 0, active: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_established: "/system/proxy/" (establishing: 1)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: unwatch_fast: "/system/proxy/" (active: 1, establishing: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_established: "/system/proxy/http/" (establishing: 1)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: unwatch_fast: "/system/proxy/http/" (active: 1, establishing: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_established: "/system/proxy/https/" (establishing: 1)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: unwatch_fast: "/system/proxy/https/" (active: 1, establishing: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_established: "/system/proxy/ftp/" (establishing: 1)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: unwatch_fast: "/system/proxy/ftp/" (active: 1, establishing: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: watch_established: "/system/proxy/socks/" (establishing: 1)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): dconf-DEBUG: 04:09:13.115: unwatch_fast: "/system/proxy/socks/" (active: 1, establishing: 0)
Apr 18 04:09:13 server.io fwupdmgr[342231]: (fwupdmgr:342231): GLib-GIO-DEBUG: 04:09:13.116: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’
Apr 18 04:09:13 server.io systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit fwupd-refresh.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Apr 18 04:09:13 server.io systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit fwupd-refresh.service has entered the 'failed' state with result 'exit-code'.
Apr 18 04:09:13 server.io systemd[1]: Failed to start Refresh fwupd metadata and update motd.
-- Subject: A start job for unit fwupd-refresh.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit fwupd-refresh.service has finished with a failure.
--
-- The job identifier is 8198 and the job result is failed.I'm really not sure then. We might need to add a lot more debugging to the code to figure out where exactly things fail for y'all with DynamicUser.
I'm tempted to remove that key, but then we would also need to create a dedicated user for the refresh process to use.
I suppose the other option is we could set up the daemon to be able to automatically refresh on its own with a forked process but that's a whole other can of worms.
ealap
commented
2 years ago I was able to print the error logs by changing the service option StandardError from null to syslog. Now I have this recorded from journalctl
Apr 19 18:14:57 [..] systemd[1]: Starting Refresh fwupd metadata and update motd...
Subject: A start job for unit fwupd-refresh.service has begun execution
Defined-By: systemd
Support: http://www.ubuntu.com/support
A start job for unit fwupd-refresh.service has begun execution.
The job identifier is 14669.
Apr 19 18:14:57 [..] systemd[400365]: Found pre-existing public CacheDirectory= directory /var/cache/fwupdmgr, migrating to /var/cache/private/fwupdmgr.
Apr 19 18:14:57 [..] systemd[400365]: Apparently, service previously had DynamicUser= turned off, and has now turned it on.
Apr 19 18:14:57 [..] fwupdmgr[400365]: setenv()/putenv() are not thread-safe and should not be used after threads are created
Apr 19 18:14:57 [..] fwupdmgr[400365]: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_fast: "/system/proxy/" (establishing: 0, active: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_fast: "/system/proxy/http/" (establishing: 0, active: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_fast: "/system/proxy/https/" (establishing: 0, active: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_fast: "/system/proxy/ftp/" (establishing: 0, active: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_fast: "/system/proxy/socks/" (establishing: 0, active: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: unwatch_fast: "/system/proxy/" (active: 0, establishing: 1)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unwatch_fast: "/system/proxy/http/" (active: 0, establishing: 1)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unwatch_fast: "/system/proxy/https/" (active: 0, establishing: 1)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unwatch_fast: "/system/proxy/ftp/" (active: 0, establishing: 1)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unwatch_fast: "/system/proxy/socks/" (active: 0, establishing: 1)
Apr 19 18:14:57 [..] fwupdmgr[400365]: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_established: "/system/proxy/" (establishing: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_established: "/system/proxy/http/" (establishing: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_established: "/system/proxy/https/" (establishing: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_established: "/system/proxy/ftp/" (establishing: 0)
Apr 19 18:14:57 [..] fwupdmgr[400365]: unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.
Apr 19 18:14:57 [..] fwupdmgr[400365]: Failed to connect to daemon: Exhausted all available authentication mechanisms (tried: EXTERNAL) (available: EXTERNAL)
Apr 19 18:14:57 [..] fwupdmgr[400365]: watch_established: "/system/proxy/socks/" (establishing: 0)
Apr 19 18:14:57 [..] systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Subject: Unit process exited
Defined-By: systemd
Support: http://www.ubuntu.com/support
An ExecStart= process belonging to unit fwupd-refresh.service has exited.
The process' exit code is 'exited' and its exit status is 1.
Apr 19 18:14:57 [..] systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: http://www.ubuntu.com/support
The unit fwupd-refresh.service has entered the 'failed' state with result 'exit-code'.
Apr 19 18:14:57 [..] systemd[1]: Failed to start Refresh fwupd metadata and update motd.
Subject: A start job for unit fwupd-refresh.service has failed
Defined-By: systemd
Support: http://www.ubuntu.com/support
A start job for unit fwupd-refresh.service has finished with a failure.
The job identifier is 14669 and the job result is failed.
So this might be the error you need?
unable to create directory '/.cache/dconf': Read-only file system. dconf will not work properly.Actually this looks like the error to me that we care about:
Failed to connect to daemon: Exhausted all available authentication mechanisms (tried: EXTERNAL) (available: EXTERNAL)
What that means is that the failure is occurring here: https://github.com/fwupd/fwupd/blob/01aaa97bcdb6d1f32ae8c52cb4c5428e28fef577/src/fu-util.c#L4406
Something about the environment that the unit is running under is preventing it from authenticating with the daemon.
In one terminal if you start up sudo dbus-monitor --system interface=org.freedesktop.fwupd you can see if the daemon even gets the message from the service. I'm guessing it doesn't.
As for why, that's another layer of the onion.
Meth0d007
commented
2 years ago Just wanted to add my +1 on this.
Since last night ubuntu 20 LTS updates (i suspect systemd) we are seeing these errors in our monitoring:
● fwupd-refresh.service - Refresh fwupd metadata and update motd
Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-04-20 11:19:05 UTC; 8min ago
TriggeredBy: ● fwupd-refresh.timer
Docs: man:fwupdmgr(1)
Process: 108516 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=1/FAILURE)
Main PID: 108516 (code=exited, status=1/FAILURE)
Apr 20 11:19:05 srvbookstack systemd[1]: Starting Refresh fwupd metadata and update motd...
Apr 20 11:19:05 srvbookstack systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Apr 20 11:19:05 srvbookstack systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Apr 20 11:19:05 srvbookstack systemd[1]: Failed to start Refresh fwupd metadata and update motd.Start-Date: 2022-04-19 19:09:48
Commandline: apt upgrade -y
Install: linux-headers-5.4.0-109:amd64 (5.4.0-109.123, automatic), linux-modules-extra-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic), linux-modules-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic), linux-headers-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic), linux-image-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic)
Upgrade: linux-headers-generic:amd64 (5.4.0.107.111, 5.4.0.109.113), libsystemd0:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), linux-image-generic:amd64 (5.4.0.107.111, 5.4.0.109.113), udev:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), libudev1:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), systemd-timesyncd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), apport:amd64 (2.20.11-0ubuntu27.21, 2.20.11-0ubuntu27.23), python3-distupgrade:amd64 (1:20.04.37, 1:20.04.38), ubuntu-release-upgrader-core:amd64 (1:20.04.37, 1:20.04.38), python3-apport:amd64 (2.20.11-0ubuntu27.21, 2.20.11-0ubuntu27.23), systemd-sysv:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), libpam-systemd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), systemd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), libnss-systemd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), linux-generic:amd64 (5.4.0.107.111, 5.4.0.109.113), python3-problem-report:amd64 (2.20.11-0ubuntu27.21, 2.20.11-0ubuntu27.23)
End-Date: 2022-04-19 19:11:00Just wanted to add my +1 on this.
Since last night ubuntu 20 LTS updates (i suspect systemd) we are seeing these errors in our monitoring:
● fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2022-04-20 11:19:05 UTC; 8min ago TriggeredBy: ● fwupd-refresh.timer Docs: man:fwupdmgr(1) Process: 108516 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=1/FAILURE) Main PID: 108516 (code=exited, status=1/FAILURE) Apr 20 11:19:05 srvbookstack systemd[1]: Starting Refresh fwupd metadata and update motd... Apr 20 11:19:05 srvbookstack systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Apr 20 11:19:05 srvbookstack systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Apr 20 11:19:05 srvbookstack systemd[1]: Failed to start Refresh fwupd metadata and update motd.Start-Date: 2022-04-19 19:09:48 Commandline: apt upgrade -y Install: linux-headers-5.4.0-109:amd64 (5.4.0-109.123, automatic), linux-modules-extra-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic), linux-modules-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic), linux-headers-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic), linux-image-5.4.0-109-generic:amd64 (5.4.0-109.123, automatic) Upgrade: linux-headers-generic:amd64 (5.4.0.107.111, 5.4.0.109.113), libsystemd0:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), linux-image-generic:amd64 (5.4.0.107.111, 5.4.0.109.113), udev:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), libudev1:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), systemd-timesyncd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), apport:amd64 (2.20.11-0ubuntu27.21, 2.20.11-0ubuntu27.23), python3-distupgrade:amd64 (1:20.04.37, 1:20.04.38), ubuntu-release-upgrader-core:amd64 (1:20.04.37, 1:20.04.38), python3-apport:amd64 (2.20.11-0ubuntu27.21, 2.20.11-0ubuntu27.23), systemd-sysv:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), libpam-systemd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), systemd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), libnss-systemd:amd64 (245.4-4ubuntu3.15, 245.4-4ubuntu3.16), linux-generic:amd64 (5.4.0.107.111, 5.4.0.109.113), python3-problem-report:amd64 (2.20.11-0ubuntu27.21, 2.20.11-0ubuntu27.23) End-Date: 2022-04-19 19:11:00
Are you sure it didn't happen before this? If so we should have a good pointer at patches that went into systemd in that version.
If you can correlate from the journal please.
Meth0d007
commented
2 years ago Yes i am sure, we have not seen this error in our monitoring until yesterday right after the apt updates. Last night was a maintenance window where updates have beein installed via apt, after the reboot i see the failed service state was picked up by our monitoring. The only thing that changed you see in the apt/history.log above, so systemd is imho a very safe bet.
rdiez
commented
2 years ago After 2 weeks off, I updated my Ubuntu 20.04.4 yesterday, and I started getting this failure today. I noticed because I am running Prometheus to monitor failed systemd services.
Meth0d007
commented
2 years ago I have confirmed this on every Ubuntu 20 LTS we operate (around 15) . All of them have gotten a bunch of updates at least yesterday and on all of them have fwupd-refresh.service failed now. The only updates i can relate to this are kernel, udev and systemd.
superm1
commented
2 years ago Here is the changelog for that release: https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 The most likely suspect is https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 which is actually the same thing I linked above with new systemd. https://github.com/systemd/systemd/issues/22737
superm1
commented
2 years ago FYI, I can repro this with Ubuntu 22.04 as well now with the updated systemd there that I checked. Anyone else affected by this that it's filling up monitoring logs I think you should systemctl mask fwupd-refresh.service until a systemd solution is made available.
superm1
commented
2 years ago Something I realized odd about this situation is that we actually do ship a fwupd-refresh.preset that should default the unit to disabled. So why are all of these failures happening when it's disabled?
superm1
commented
2 years ago Maybe the preset doesn't work with static units is the reason? I just am surprised that this is only reported by Ubuntu.
zwets
commented
2 years ago Maybe the preset doesn't work with static units is the reason? I just am surprised that this is only reported by Ubuntu.
The file /usr/lib/systemd/system-preset/fwupd-refresh.preset is distributed with Ubuntu. I would indeed think that what needs disabling is the timer rather than the unit.
superm1
commented
2 years ago So the preset doesn't work with timers of static units. But shouldn't that still affect Fedora too?
superm1
commented
2 years ago Oh... I get it. fedora defaults to disabled if no preset, ubuntu defaults to enabled if no preset. That's why we see it in Ubuntu with timers. OK. I'll think about what can be done here from upstream fwupd perspective.
loca5790
commented
2 years ago @superm1 I'm noticing the same issue, Ubuntu 22.04, it looks like the suggestion is mask it?
superm1
commented
2 years ago You can either make a dedicated user, mask it, or turn off dynamic user.
DemonRx
commented
2 years ago I was able to get the service to exit successfully without changing DynamicUser=yes to no.
I just added User=root, and this resolved the service failing.
My reference for finding this solution is from https://github.com/systemd/systemd/issues/10025
Therefore the extra security of using DynamicUser will not be lost since it can remain active.
demon@Impish:~$ systemctl daemon-reload; service fwupd-refresh restart; service fwupd-refresh status
○ fwupd-refresh.service - Refresh fwupd metadata and update motd
Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static)
Active: inactive (dead) since Sun 2022-05-08 00:07:23 EDT; 69ms ago
TriggeredBy: ● fwupd-refresh.timer
Docs: man:fwupdmgr(1)
Process: 23090 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=2)
Main PID: 23090 (code=exited, status=2)
CPU: 141ms
May 08 00:07:22 Impish systemd[1]: Starting Refresh fwupd metadata and update motd...
May 08 00:07:23 Impish systemd[1]: fwupd-refresh.service: Deactivated successfully.
May 08 00:07:23 Impish systemd[1]: Finished Refresh fwupd metadata and update motd.
cidrbl0ck
commented
2 years ago Wanted to comment here, I found this page while searching for a solution to the exact same issue in this thread. I didn't see mention above of what the fwupd-refresh.timer file should contain.. but mine has
disable fwupd-refresh.service
Should this mean that the .service daemon should be disabled? If so, that's not what's been going on.
Also wondering if the fixes are still: "You can either make a dedicated user, mask it, or turn off dynamic user." ?
superm1
commented
2 years ago Should this mean that the .service daemon should be disabled? If so, that's not what's been going on.
IIRC If the timer is in place it still runs even if service is disabled.
Also wondering if the fixes are still: "You can either make a dedicated user, mask it, or turn off dynamic user." ?
Debian/Ubuntu fwupd 1.8.x packages will create a dedicated user for this use. Other distros might need to adopt something similar in the packaging.
cidrbl0ck
commented
2 years ago Thanks superm1, We're really trying to keep to official LTS sources, the 'fwupd/jammer' caps out at version 1.7.5-3 if I'm looking at this correctly. But, if the .service or even the .preset can be disabled or masked without system harm then that might be the path forward for now.
superm1
commented
2 years ago Here's the bug report for Ubuntu 22.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969976. As I type this, the SRU is in progress.
Describe the bug I have the systemd
fwupd-refresh.timerenabled. It normally triggers thefwupd-refresh.service. That service fails:Steps to Reproduce Seems to happen every time the service is triggered. Manually, I have managed to refresh.
Expected behavior The service generally runs without errors.
fwupd version information
Installed with Gentoo portage (
emerge …)fwupd device information
Additional questions