Score:1

Systemd not finding linked service after reboot (22.04)

au flag

A service file resides at /home/user/workspace/xyz.service. Using systemctl enable with the absolute path puts a link in /etc/systemd/system/ so I can run it as service xyz restart. However, I am unable to use the service after rebooting ("Unit xyz.service not found"). The link is still there in /etc/systemd/system/, and running systemctl daemon-reload lets me use the service again.

Similar behavior can be caused when the service file is located on a partition not available during systemd startup. I have ZFS encryption so maybe that is interfering? It is the standard setup (per the Ubuntu installer) so /etc and /home should be decrypted together on the rpool. Any ideas?

Majal avatar
cn flag
Happened to me as well. My home directory is in an encrypted drive that needs decryption, which means a late mount. I'd also like to know what really happens here.
Majal avatar
cn flag
I think this explains it: https://unix.stackexchange.com/a/494647/105126
Matthew Foran avatar
au flag
Thanks Majal. I was hoping for something more elegant but that will do it.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.