From: Gilberto Ferreira <gilberto.nunes32@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Service "systemd-tmpfiles-setup" fails since upgrade to PVE 7.x
Date: Wed, 8 Jun 2022 08:06:09 -0300 [thread overview]
Message-ID: <CAOKSTBsW0oai-d7jOCoBm-bn32e15Wj1_X7oDkBwYTCJ5K8c0Q@mail.gmail.com> (raw)
In-Reply-To: <19fec87f-3c95-b03c-5a50-de649771cc3a@dkfz-heidelberg.de>
Hi
Did you make a full reboot after upgrade?
Silly question, but still...
Em qua., 8 de jun. de 2022 às 07:13, Frank Thommen <
f.thommen@dkfz-heidelberg.de> escreveu:
> Dear all,
>
> since the upgrade of our PVE environment from 6.x to 7.2-4 last week,
> our monitoring (CheckMK) registers, that the service
> "systemd-tmpfiles-setup" fails in all containers (not in the VMs,
> though). The containers have been created from the provided CentOS 7.9
> templates and are fully updated. The containers have all been created
> under PVE 5.x and 6.x.
>
> I'm not familiar with "systemd-tmpfiles-setup" and I could not relate
> similar failure reports found in the net to our situation.
>
> The status that we get is:
> --------------------------------------------------------------
> [root@odcf-vm119 ~]# systemctl status systemd-tmpfiles-setup.service
> ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
> Loaded: loaded
> (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor
> preset: disabled)
> Active: failed (Result: exit-code) since Tue 2022-06-07 12:28:04
> CEST; 23h ago
> Docs: man:tmpfiles.d(5)
> man:systemd-tmpfiles(8)
> Process: 55 ExecStart=/usr/bin/systemd-tmpfiles --create --remove
> --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
> Main PID: 55 (code=exited, status=1/FAILURE)
>
> Jun 07 12:28:03 odcf-vm119 systemd[1]: Starting Create Volatile Files
> and Directories...
> Jun 07 12:28:03 odcf-vm119 systemd-tmpfiles[55]: Failed to create
> directory or subvolume "/var/lib/machines": Operation not permitted
> Jun 07 12:28:04 odcf-vm119 systemd-tmpfiles[55]: Failed to create
> directory or subvolume "/tmp": Operation not permitted
> Jun 07 12:28:04 odcf-vm119 systemd-tmpfiles[55]: Failed to create
> directory or subvolume "/var/tmp": Operation not permitted
> Jun 07 12:28:04 odcf-vm119 systemd[1]: systemd-tmpfiles-setup.service:
> main process exited, code=exited, status=1/FAILURE
> Jun 07 12:28:04 odcf-vm119 systemd[1]: Failed to start Create Volatile
> Files and Directories.
> Jun 07 12:28:04 odcf-vm119 systemd[1]: Unit
> systemd-tmpfiles-setup.service entered failed state.
> Jun 07 12:28:04 odcf-vm119 systemd[1]: systemd-tmpfiles-setup.service
> failed.
> [root@odcf-vm119 ~]#
> --------------------------------------------------------------
>
> journalctl tells me (manual extract from `journalctl -t systemd`):
> --------------------------------------------------------------
> Jun 07 12:28:03 odcf-vm119 systemd[1]: Starting Create Volatile Files
> and Directories...
> Jun 07 12:28:04 odcf-vm119 systemd[1]: Started Load/Save Random Seed.
> Jun 07 12:28:04 odcf-vm119 systemd[1]: systemd-tmpfiles-setup.service:
> main process exited, code=exited, status=1/FAILURE
> Jun 07 12:28:04 odcf-vm119 systemd[1]: Failed to start Create Volatile
> Files and Directories.
> Jun 07 12:28:04 odcf-vm119 systemd[1]: Unit
> systemd-tmpfiles-setup.service entered failed state.
> Jun 07 12:28:04 odcf-vm119 systemd[1]: systemd-tmpfiles-setup.service
> failed.
> --------------------------------------------------------------
>
> and (`journalctl -t systemd-tmpfiles`):
> --------------------------------------------------------------
> -- Logs begin at Tue 2022-06-07 12:28:03 CEST, end at Wed 2022-06-08
> 12:00:47 CEST. --
> Jun 07 12:28:03 odcf-vm119 systemd-tmpfiles[55]: Failed to create
> directory or subvolume "/var/lib/machines": Operation not permitted
> Jun 07 12:28:04 odcf-vm119 systemd-tmpfiles[55]: Failed to create
> directory or subvolume "/tmp": Operation not permitted
> Jun 07 12:28:04 odcf-vm119 systemd-tmpfiles[55]: Failed to create
> directory or subvolume "/var/tmp": Operation not permitted
> --------------------------------------------------------------
>
>
> Can anyone tell, what the problem could be or in which direction we
> should try to search for the problem?
>
>
> I might also just migrate all containers to VMs, if that is a good or
> recommended solution to get rid of this problem. I currently don't see
> the benefit of containers over VMs anyway at this moment :-)
>
> Cheers and thanks in advance
> Frank
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2022-06-08 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 10:08 Frank Thommen
2022-06-08 11:06 ` Gilberto Ferreira [this message]
2022-06-08 12:27 ` Frank Thommen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOKSTBsW0oai-d7jOCoBm-bn32e15Wj1_X7oDkBwYTCJ5K8c0Q@mail.gmail.com \
--to=gilberto.nunes32@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox