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 B442F7202D for ; Wed, 6 Oct 2021 10:52:58 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A291B96CF for ; Wed, 6 Oct 2021 10:52:28 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id B4AF596C4 for ; Wed, 6 Oct 2021 10:52:27 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 83C464549B; Wed, 6 Oct 2021 10:52:27 +0200 (CEST) Message-ID: <59539fdd-ee31-5b6a-fa3e-e049a7baac45@proxmox.com> Date: Wed, 6 Oct 2021 10:51:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:93.0) Gecko/20100101 Thunderbird/93.0 Content-Language: en-US To: Victor Hooi Cc: Proxmox VE development discussion References: <8cd3661e-8f46-0bcd-8f94-cab86e45caf4@proxmox.com> From: Thomas Lamprecht In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 1.202 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -1.964 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [stackexchange.com, proxmox.com] Subject: Re: [pve-devel] trousers error in latest test repo? X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2021 08:52:58 -0000 On 06.10.21 10:39, Victor Hooi wrote: > Hi, >=20 > Nope, I haven't edited /etc/init.d/trousers. (I did view it, because of= this > post > > and > curiosity but didn't make any changes). >=20 > I just tested a reinstall, as suggested - I still get an error: hmm, but the installation or a new update itself exits Ok now, or? As mentioned an error message can still be expected, I'll look into makin= g it seem less scary but FWICT there's no underlying cause that can get fixed,= at least short of rewriting tpm stuff; which I'd like to avoid ;-)=20 >=20 > root@mgmt1:/etc/apt/sources.list.d# apt install --reinstall trousers >> Reading package lists... Done >> Building dependency tree... Done >> Reading state information... Done >> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not >> upgraded. >> Need to get 137 kB of archives. >> After this operation, 0 B of additional disk space will be used. >> Get:1 http://download.proxmox.com/debian/pve bullseye/pvetest amd64 >> trousers amd64 0.3.14+fixed1-1.2+pve1 [137 kB] >> Fetched 137 kB in 1s (115 kB/s) >> (Reading database ... 49780 files and directories currently installed.= ) >> Preparing to unpack .../trousers_0.3.14+fixed1-1.2+pve1_amd64.deb ... >> Unpacking trousers (0.3.14+fixed1-1.2+pve1) over (0.3.14+fixed1-1.2+pv= e1) >> ... >> Setting up trousers (0.3.14+fixed1-1.2+pve1) ... >> Job for trousers.service failed because the control process exited wit= h >> error code. >> See "systemctl status trousers.service" and "journalctl -xe" for detai= ls. >> invoke-rc.d: initscript trousers, action "restart" failed. >> =E2=97=8F trousers.service - LSB: starts tcsd >> Loaded: loaded (/etc/init.d/trousers; generated) >> Active: failed (Result: exit-code) since Wed 2021-10-06 01:37:06 = PDT; >> 24ms ago >> Docs: man:systemd-sysv-generator(8) >> Process: 199367 ExecStart=3D/etc/init.d/trousers start (code=3Dexi= ted, >> status=3D30) >> CPU: 9ms >=20 >=20 > Oct 06 01:37:06 mgmt1 systemd[1]: Starting LSB: starts tcsd... > Oct 06 01:37:06 mgmt1 tcsd[199372]: TCSD TDDL[199372]: TrouSerS ioctl: = (25) > Inappropriate ioctl for device > Oct 06 01:37:06 mgmt1 tcsd[199372]: TCSD TDDL[199372]: TrouSerS Falling= > back to Read/Write device support. > Oct 06 01:37:06 mgmt1 tcsd[199372]: TCSD TCS[199372]: TrouSerS ERROR: T= CS > GetCapability failed with result =3D 0x1e > Oct 06 01:37:06 mgmt1 trousers[199367]: Starting Trusted Computing daem= on: > tcsd > Oct 06 01:37:06 mgmt1 trousers[199373]: failed! > Oct 06 01:37:06 mgmt1 systemd[1]: trousers.service: Control process exi= ted, > code=3Dexited, status=3D30/n/a > Oct 06 01:37:06 mgmt1 systemd[1]: trousers.service: Failed with result > 'exit-code'. > Oct 06 01:37:06 mgmt1 systemd[1]: Failed to start LSB: starts tcsd. > Processing triggers for man-db (2.9.4-2) ... >=20 > What do you mean by whether I have a node? Ah sorry for the confusion, I did mean a device file-node (not a PVE node= ), but your ls output does not seem to suggest that you have any.. >=20 > root@mgmt1:/etc/apt/sources.list.d# ls -l /dev/tmp* >> ls: cannot access '/dev/tmp*': No such file or directory >=20