Score:0

Mount attempt receives SIGTERM from systemd (249) after unknown timeout

ch flag

I am attempting to mount three mountpoints on a remote, parallel filesystem, using fstab. Periodically, one of the the three mounts will not succeed. An inspection of the journal suggests that systemd is sending a SIGTERM to the failing mount, approximately 69 seconds after the mount attempt. It is not clear to me where the 69 second timeout is originating, or configured.

Aug 08 17:37:25 vrr-20230804-cst-client-1 mount[883]: Mounting 10.114.96.165/fs3 on /mnt/fs3

Aug 08 17:38:34 vrr-20230804-cst-client-1 systemd[1]: mnt\x2dfs1.mount: Mount process exited, code=killed, status=15/TERM

Aug 08 17:38:34 vrr-20230804-cst-client-1 mount[883]: SIGTERM received, quitting

The x-systemd.mount-timeout parameter is currently set to 300 seconds in the /etc/fstab entries.

Thoughts?

Terrance avatar
id flag
Possibly in this answer https://askubuntu.com/a/1264626/231142
Vincent avatar
ch flag
Sorry, I did not elaborate -- the x-systemd.mount-timeout parameter is set to 5 minutes in the /ets/fstab file.
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.