From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 63024711F9 for ; Wed, 8 Jun 2022 13:07:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5279D7112 for ; Wed, 8 Jun 2022 13:06:55 +0200 (CEST) Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 1045570FE for ; Wed, 8 Jun 2022 13:06:52 +0200 (CEST) Received: by mail-lf1-x12b.google.com with SMTP id i29so15909697lfp.3 for ; Wed, 08 Jun 2022 04:06:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=uL5l4Sn89cY80aeEsWo1wNfpWo/PKimof2VmyFDA4K4=; b=jYdIBHnjiaGm5eOrKLvgot/WL0U/z9B/9QOwHV+jpSRjmglu4mAgrPgMCzcAoNC1jQ LgXmAIvEZY4VkKmDIfL4jAOZveR9+dLtE8Fcebhdduku/gyZIroiY6PVdXWejFY7MiZM YdFvWVeu5uMPtg1c+KGpLFkUjedv7R/2Fq9kcDV3pP3taeu6aTvppTXC/2/IetdAko+9 T9HxrMwikQxHy6kRDEWINguR+kDHRr0vmnVNe8NT5g43mvR2GxqQglKcl3z4iEbJz96K rS2JMUa2UNn5VaTzrCkdIrWeR4gTwJe8rZOv1qz00t4BdYkH+E2KZwDysVETFSG3JR7h elOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=uL5l4Sn89cY80aeEsWo1wNfpWo/PKimof2VmyFDA4K4=; b=cMe4y1JLHfDgFQW9LnZ7PFZOZvfjv4Rad6FN4yD4PjNvke7A0VN8P3zOFE3rUVo7Ht KVSfJFLAqPJvOFor2YbtS+EAmN4VHs5EXhemNyXBaefFFZTB1hEGXIHGW6kAdpG3O5Ii PdZH4qNt78ZBTgoIw8vbsDXwmX6ZeJxy84zwCaIP6kKdtntI4AjcogVgOvS2B+lJ07aI E8RUtwQGl+d+I+YJaNf/SiLpBTUNyRVu9nAEbKMJoAe5uz50b4HMaSItUzV68ISY1AiF F97i31uidOWve++rsMy8UDCdfdHHxtg/lxNeMULVQR+BhxVkB0a2uSXJzM6RuD1aEgdU UkwA== X-Gm-Message-State: AOAM533uSwMDVghM2KQzqOdm1NFdYHjbTmdggiCyqWPd1Jd+zpKwZdg7 1xIsPYXXr2mOyTMFd2HmXNocNsCn/X+NUTnSgwtF2wUmiZg= X-Google-Smtp-Source: ABdhPJxf82Y5YtSCUFE2men2egCBmheuVcvaoO10U7/kBn5FekwmEBx40KmVJKVC/j/5zQgdl6erwJo7ZKLbj08rZdk= X-Received: by 2002:a05:6512:3f01:b0:46b:a5ba:3b89 with SMTP id y1-20020a0565123f0100b0046ba5ba3b89mr21299818lfa.28.1654686405872; Wed, 08 Jun 2022 04:06:45 -0700 (PDT) MIME-Version: 1.0 References: <19fec87f-3c95-b03c-5a50-de649771cc3a@dkfz-heidelberg.de> In-Reply-To: <19fec87f-3c95-b03c-5a50-de649771cc3a@dkfz-heidelberg.de> From: Gilberto Ferreira Date: Wed, 8 Jun 2022 08:06:09 -0300 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 0 AWL 0.155 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_ENVFROM_END_DIGIT 0.25 Envelope-from freemail username ends in digit FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message POISEN_SPAM_PILL_4 0.1 random spam to be learned in bayes RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] Service "systemd-tmpfiles-setup" fails since upgrade to PVE 7.x X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2022 11:07:25 -0000 Hi Did you make a full reboot after upgrade? Silly question, but still... Em qua., 8 de jun. de 2022 =C3=A0s 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 > =E2=97=8F systemd-tmpfiles-setup.service - Create Volatile Files and Dire= ctories > 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=3D/usr/bin/systemd-tmpfiles --create --remove > --boot --exclude-prefix=3D/dev (code=3Dexited, status=3D1/FAILURE) > Main PID: 55 (code=3Dexited, status=3D1/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=3Dexited, status=3D1/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=3Dexited, status=3D1/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 >