Bug#1041014: marked as done (systemd-timesyncd.service: Failed to execute /lib/systemd/systemd-timesyncd: Permission dienied)

[AlMa]

On 14.07.23 14:54, Michael Biebl wrote:
> It's possible that the upgrade process between 11 and 12 did not run 
> properly and something was broken.
> 
Yes, maybe (another issue from the upgrade process: #1041052).

> As I wrote, the output from systemd doesn't look like the root cause of 
> your issues but only a symptom.
> 
> Hard to say with basically zero information.

It's more than zero. You mean you don't see potential sources of the 
root cause. I agree, neither do I.  We still have more information, 
namely, concerning the parts which are NOT broken, e.g., the permissions 
of /, /tmp, and /var/tmp.  In the meantime, consider the screenshot of 
journal -xb just before the error in the attachment ("screenshot" is 
highlighted because it has been searched for; further, the host name is 
blurred).

A third issue should be mentioned (the first two being a failure to 
execute /lib/systemd/systemd-timesyncd and obscure "ERRNO" and 
"'exit-code'").
Namely, it's pointless to attempt to start timesyncd before Internet 
access has been established.  In my case, Internet access usually gets 
established by NetworkManager via DHCP over WiFi (and seldom I attach an 
Ethernet cable), but NetworkManager has not even been launched at the 
time systemd-timesyncd is attempted to be started.  Running first 
`systemctl start NetworkManager`, waiting for a connection, and then 
running `systemctl start systemd-timesyncd` still yields "Failed to 
execute /lib/systemd/systemd-timesyncd: Permission dienied", so these 
issues are independent.

Gratefully,

AlMa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot_of_journal_xb.png
Type: image/png
Size: 15693060 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230714/8933ab54/attachment-0001.png>