[pve-devel] trousers error in latest test repo?

[pve-devel] trousers error in latest test repo?

[Victor Hooi]

Hi,

I just installed a new box (Intel NUC7i5BNK) with Proxmox 7.0-2, and then
ran an apt update/dist-upgrade, using the PVE test repos:

There seems to be some error whilst upgrading some "trousers" module:

Setting up trousers (0.3.14+fixed1-1.2) ...
> Job for trousers.service failed because the control process exited with
> error code.
> See "systemctl status trousers.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript trousers, action "start" failed.
> ● trousers.service - LSB: starts tcsd
>      Loaded: loaded (/etc/init.d/trousers; generated)
>      Active: failed (Result: exit-code) since Tue 2021-10-05 15:43:15 PDT;
> 4ms ago
>        Docs: man:systemd-sysv-generator(8)
>     Process: 32424 ExecStart=/etc/init.d/trousers start (code=exited,
> status=30)
>         CPU: 10ms


Oct 05 15:43:15 mgmt1 systemd[1]: Starting LSB: starts tcsd...
> Oct 05 15:43:15 mgmt1 trousers[32424]: Starting Trusted Computing daemon:
> tcsd/etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator
> Oct 05 15:43:15 mgmt1 TCSD[32429]: TrouSerS resetting mode of /var/lib/tpm
> from 40755 to: 700
> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TDDL[32429]: TrouSerS ioctl: (25)
> Inappropriate ioctl for device
> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TDDL[32429]: TrouSerS Falling back
> to Read/Write device support.
> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TCS[32429]: TrouSerS ERROR: TCS
> GetCapability failed with result = 0x1e
> Oct 05 15:43:15 mgmt1 trousers[32430]:  failed!
> Oct 05 15:43:15 mgmt1 systemd[1]: trousers.service: Control process
> exited, code=exited, status=30/n/a
> Oct 05 15:43:15 mgmt1 systemd[1]: trousers.service: Failed with result
> 'exit-code'.
> Oct 05 15:43:15 mgmt1 systemd[1]: Failed to start LSB: starts tcsd.
> dpkg: error processing package trousers (--configure):
>  installed trousers package post-installation script subprocess returned
> error exit status 1


However, this also then causes issues when attempting to finalise other
packages as well:

dpkg: dependency problems prevent configuration of swtpm-tools:
>  swtpm-tools depends on trousers (>= 0.3.9); however:
>   Package trousers is not configured yet.


dpkg: error processing package swtpm-tools (--configure):
>  dependency problems - leaving unconfigured
> Setting up swtpm (0.6.99+1) ...
> Setting up pve-firewall (4.2-3) ...
> Setting up libzpool5linux (2.1.1-pve1) ...
> Setting up gnutls-bin (3.7.1-5) ...
> Setting up corosync (3.1.5-pve1) ...
> dpkg: dependency problems prevent configuration of qemu-server:
>  qemu-server depends on swtpm-tools; however:
>   Package swtpm-tools is not configured yet.


dpkg: error processing package qemu-server (--configure):
>  dependency problems - leaving unconfigured
> Setting up zfsutils-linux (2.1.1-pve1) ...
> Installing new version of config file /etc/zfs/zfs-functions ...
> Setting up zfs-initramfs (2.1.1-pve1) ...
> dpkg: dependency problems prevent configuration of pve-manager:
>  pve-manager depends on qemu-server (>= 6.2-17); however:
>   Package qemu-server is not configured yet.


dpkg: error processing package pve-manager (--configure):
>  dependency problems - leaving unconfigured
> Setting up zfs-zed (2.1.1-pve1) ...
> Installing new version of config file /etc/zfs/zed.d/zed-functions.sh ...
> dpkg: dependency problems prevent processing triggers for pve-ha-manager:
>  pve-ha-manager depends on qemu-server (>= 6.0-15); however:
>   Package qemu-server is not configured yet.


dpkg: error processing package pve-ha-manager (--configure):
>  dependency problems - leaving triggers unprocessed
> Processing triggers for initramfs-tools (0.140) ...
> update-initramfs: Generating /boot/initrd.img-5.11.22-5-pve
> Running hook script 'zz-proxmox-boot'..
> Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount
> namespace..
> Copying and configuring kernels on /dev/disk/by-uuid/5994-C1A0
> Copying kernel and creating boot-entry for 5.11.22-4-pve
> Copying kernel and creating boot-entry for 5.11.22-5-pve
> Processing triggers for libc-bin (2.31-13) ...
> Processing triggers for man-db (2.9.4-2) ...
> Processing triggers for mailcap (3.69) ...
> Errors were encountered while processing:
>  trousers
>  swtpm-tools
>  qemu-server
>  pve-manager
>  pve-ha-manager
> E: Sub-process /usr/bin/dpkg returned an error code (1)


Does anybody know what this is?

Is it related to this? (Apparently an error in the init.d script - although
I'm not sure where this script comes from)

https://unix.stackexchange.com/questions/633563/can-not-start-trousers-service-giving-error-trousers-ioctl-25-inappropriat

Thanks,
Vic

Re: [pve-devel] trousers error in latest test repo?

[Thomas Lamprecht]

On 06.10.21 00:51, Victor Hooi wrote:
> Hi,
> 
> I just installed a new box (Intel NUC7i5BNK) with Proxmox 7.0-2, and then
> ran an apt update/dist-upgrade, using the PVE test repos:
> 
> There seems to be some error whilst upgrading some "trousers" module:
> 
> Setting up trousers (0.3.14+fixed1-1.2) ...
>> Job for trousers.service failed because the control process exited with
>> error code.
>> See "systemctl status trousers.service" and "journalctl -xe" for details.
>> invoke-rc.d: initscript trousers, action "start" failed.
>> ● trousers.service - LSB: starts tcsd
>>      Loaded: loaded (/etc/init.d/trousers; generated)
>>      Active: failed (Result: exit-code) since Tue 2021-10-05 15:43:15 PDT;
>> 4ms ago
>>        Docs: man:systemd-sysv-generator(8)
>>     Process: 32424 ExecStart=/etc/init.d/trousers start (code=exited,
>> status=30)
>>         CPU: 10ms
> 
> 
> Oct 05 15:43:15 mgmt1 systemd[1]: Starting LSB: starts tcsd...
>> Oct 05 15:43:15 mgmt1 trousers[32424]: Starting Trusted Computing daemon:
>> tcsd/etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator
>> Oct 05 15:43:15 mgmt1 TCSD[32429]: TrouSerS resetting mode of /var/lib/tpm
>> from 40755 to: 700
>> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TDDL[32429]: TrouSerS ioctl: (25)
>> Inappropriate ioctl for device
>> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TDDL[32429]: TrouSerS Falling back
>> to Read/Write device support.
>> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TCS[32429]: TrouSerS ERROR: TCS
>> GetCapability failed with result = 0x1e
>> Oct 05 15:43:15 mgmt1 trousers[32430]:  failed!
>> Oct 05 15:43:15 mgmt1 systemd[1]: trousers.service: Control process
>> exited, code=exited, status=30/n/a
>> Oct 05 15:43:15 mgmt1 systemd[1]: trousers.service: Failed with result
>> 'exit-code'.
>> Oct 05 15:43:15 mgmt1 systemd[1]: Failed to start LSB: starts tcsd.
>> dpkg: error processing package trousers (--configure):
>>  installed trousers package post-installation script subprocess returned
>> error exit status 1
> 
> 
> However, this also then causes issues when attempting to finalise other
> packages as well:
> 
> dpkg: dependency problems prevent configuration of swtpm-tools:
>>  swtpm-tools depends on trousers (>= 0.3.9); however:
>>   Package trousers is not configured yet.
> 
> 
> dpkg: error processing package swtpm-tools (--configure):
>>  dependency problems - leaving unconfigured
>> Setting up swtpm (0.6.99+1) ...
>> Setting up pve-firewall (4.2-3) ...
>> Setting up libzpool5linux (2.1.1-pve1) ...
>> Setting up gnutls-bin (3.7.1-5) ...
>> Setting up corosync (3.1.5-pve1) ...
>> dpkg: dependency problems prevent configuration of qemu-server:
>>  qemu-server depends on swtpm-tools; however:
>>   Package swtpm-tools is not configured yet.
> 
> 
> dpkg: error processing package qemu-server (--configure):
>>  dependency problems - leaving unconfigured
>> Setting up zfsutils-linux (2.1.1-pve1) ...
>> Installing new version of config file /etc/zfs/zfs-functions ...
>> Setting up zfs-initramfs (2.1.1-pve1) ...
>> dpkg: dependency problems prevent configuration of pve-manager:
>>  pve-manager depends on qemu-server (>= 6.2-17); however:
>>   Package qemu-server is not configured yet.
> 
> 
> dpkg: error processing package pve-manager (--configure):
>>  dependency problems - leaving unconfigured
>> Setting up zfs-zed (2.1.1-pve1) ...
>> Installing new version of config file /etc/zfs/zed.d/zed-functions.sh ...
>> dpkg: dependency problems prevent processing triggers for pve-ha-manager:
>>  pve-ha-manager depends on qemu-server (>= 6.0-15); however:
>>   Package qemu-server is not configured yet.
> 
> 
> dpkg: error processing package pve-ha-manager (--configure):
>>  dependency problems - leaving triggers unprocessed
>> Processing triggers for initramfs-tools (0.140) ...
>> update-initramfs: Generating /boot/initrd.img-5.11.22-5-pve
>> Running hook script 'zz-proxmox-boot'..
>> Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount
>> namespace..
>> Copying and configuring kernels on /dev/disk/by-uuid/5994-C1A0
>> Copying kernel and creating boot-entry for 5.11.22-4-pve
>> Copying kernel and creating boot-entry for 5.11.22-5-pve
>> Processing triggers for libc-bin (2.31-13) ...
>> Processing triggers for man-db (2.9.4-2) ...
>> Processing triggers for mailcap (3.69) ...
>> Errors were encountered while processing:
>>  trousers
>>  swtpm-tools
>>  qemu-server
>>  pve-manager
>>  pve-ha-manager
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> 
> Does anybody know what this is?

It's related to TPM, swtmp-tools pulls it in and that in turn gets pulled in by
qemu-server which now provides TPM support for guests.

It seems it init script was a bit borked[0], but that only shows up on some systems,
FWICT ones that where updated from pre PVE 6 or even older.

I re-build the upstream package with a more resilient postinst and init script and
uploaded that to pvetest as `trousers` in version `0.3.14+fixed1-1.2+pve1` (fwiw,
the "fixed" part in the version was already there and not my invention ;)

An error may still get printed on update, but it should not fail the whole update
itself anymore (which has no use on its own).

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895201

hope that helps,
Thomas

Re: [pve-devel] trousers error in latest test repo?

[Victor Hooi]

Hi Thomas,

Ah - interesting - as a data-point, this was a new install of Proxmox 7.0-2
(from the ISO image), and then I ran an apt update, apt dist-upgrade
directly after first boot.

I just did an apt update, apt dist-upgrade again - and there was one
package to update (trousers).

I am still getting an error with this version:

Unpacking trousers (0.3.14+fixed1-1.2+pve1) over (0.3.14+fixed1-1.2) ...
> Setting up trousers (0.3.14+fixed1-1.2+pve1) ...
> Installing new version of config file /etc/init.d/trousers ...
> Job for trousers.service failed because the control process exited with
> error code.
> See "systemctl status trousers.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript trousers, action "start" failed.
> ● trousers.service - LSB: starts tcsd
>      Loaded: loaded (/etc/init.d/trousers; generated)
>      Active: failed (Result: exit-code) since Wed 2021-10-06 01:13:08 PDT;
> 4ms ago
>        Docs: man:systemd-sysv-generator(8)
>     Process: 192905 ExecStart=/etc/init.d/trousers start (code=exited,
> status=30)
>         CPU: 9ms


Oct 06 01:13:08 mgmt1 systemd[1]: Starting LSB: starts tcsd...
> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TDDL[192910]: TrouSerS ioctl:
> (25) Inappropriate ioctl for device
> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TDDL[192910]: TrouSerS Falling
> back to Read/Write device support.
> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TCS[192910]: TrouSerS ERROR: TCS
> GetCapability failed with result = 0x1e
> Oct 06 01:13:08 mgmt1 trousers[192905]: Starting Trusted Computing daemon:
> tcsd
> Oct 06 01:13:08 mgmt1 trousers[192911]:  failed!
> Oct 06 01:13:08 mgmt1 systemd[1]: trousers.service: Control process
> exited, code=exited, status=30/n/a
> Oct 06 01:13:08 mgmt1 systemd[1]: trousers.service: Failed with result
> 'exit-code'.
> Oct 06 01:13:08 mgmt1 systemd[1]: Failed to start LSB: starts tcsd.


I should note that the spec sheet for the NUC7i5BNK says it does not have a
TPM - would that be related at all to these errors?

Thanks,
Victor

On Wed, 6 Oct 2021 at 18:17, Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:

> On 06.10.21 00:51, Victor Hooi wrote:
> > Hi,
> >
> > I just installed a new box (Intel NUC7i5BNK) with Proxmox 7.0-2, and then
> > ran an apt update/dist-upgrade, using the PVE test repos:
> >
> > There seems to be some error whilst upgrading some "trousers" module:
> >
> > Setting up trousers (0.3.14+fixed1-1.2) ...
> >> Job for trousers.service failed because the control process exited with
> >> error code.
> >> See "systemctl status trousers.service" and "journalctl -xe" for
> details.
> >> invoke-rc.d: initscript trousers, action "start" failed.
> >> ● trousers.service - LSB: starts tcsd
> >>      Loaded: loaded (/etc/init.d/trousers; generated)
> >>      Active: failed (Result: exit-code) since Tue 2021-10-05 15:43:15
> PDT;
> >> 4ms ago
> >>        Docs: man:systemd-sysv-generator(8)
> >>     Process: 32424 ExecStart=/etc/init.d/trousers start (code=exited,
> >> status=30)
> >>         CPU: 10ms
> >
> >
> > Oct 05 15:43:15 mgmt1 systemd[1]: Starting LSB: starts tcsd...
> >> Oct 05 15:43:15 mgmt1 trousers[32424]: Starting Trusted Computing
> daemon:
> >> tcsd/etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator
> >> Oct 05 15:43:15 mgmt1 TCSD[32429]: TrouSerS resetting mode of
> /var/lib/tpm
> >> from 40755 to: 700
> >> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TDDL[32429]: TrouSerS ioctl:
> (25)
> >> Inappropriate ioctl for device
> >> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TDDL[32429]: TrouSerS Falling
> back
> >> to Read/Write device support.
> >> Oct 05 15:43:15 mgmt1 tcsd[32429]: TCSD TCS[32429]: TrouSerS ERROR: TCS
> >> GetCapability failed with result = 0x1e
> >> Oct 05 15:43:15 mgmt1 trousers[32430]:  failed!
> >> Oct 05 15:43:15 mgmt1 systemd[1]: trousers.service: Control process
> >> exited, code=exited, status=30/n/a
> >> Oct 05 15:43:15 mgmt1 systemd[1]: trousers.service: Failed with result
> >> 'exit-code'.
> >> Oct 05 15:43:15 mgmt1 systemd[1]: Failed to start LSB: starts tcsd.
> >> dpkg: error processing package trousers (--configure):
> >>  installed trousers package post-installation script subprocess returned
> >> error exit status 1
> >
> >
> > However, this also then causes issues when attempting to finalise other
> > packages as well:
> >
> > dpkg: dependency problems prevent configuration of swtpm-tools:
> >>  swtpm-tools depends on trousers (>= 0.3.9); however:
> >>   Package trousers is not configured yet.
> >
> >
> > dpkg: error processing package swtpm-tools (--configure):
> >>  dependency problems - leaving unconfigured
> >> Setting up swtpm (0.6.99+1) ...
> >> Setting up pve-firewall (4.2-3) ...
> >> Setting up libzpool5linux (2.1.1-pve1) ...
> >> Setting up gnutls-bin (3.7.1-5) ...
> >> Setting up corosync (3.1.5-pve1) ...
> >> dpkg: dependency problems prevent configuration of qemu-server:
> >>  qemu-server depends on swtpm-tools; however:
> >>   Package swtpm-tools is not configured yet.
> >
> >
> > dpkg: error processing package qemu-server (--configure):
> >>  dependency problems - leaving unconfigured
> >> Setting up zfsutils-linux (2.1.1-pve1) ...
> >> Installing new version of config file /etc/zfs/zfs-functions ...
> >> Setting up zfs-initramfs (2.1.1-pve1) ...
> >> dpkg: dependency problems prevent configuration of pve-manager:
> >>  pve-manager depends on qemu-server (>= 6.2-17); however:
> >>   Package qemu-server is not configured yet.
> >
> >
> > dpkg: error processing package pve-manager (--configure):
> >>  dependency problems - leaving unconfigured
> >> Setting up zfs-zed (2.1.1-pve1) ...
> >> Installing new version of config file /etc/zfs/zed.d/zed-functions.sh
> ...
> >> dpkg: dependency problems prevent processing triggers for
> pve-ha-manager:
> >>  pve-ha-manager depends on qemu-server (>= 6.0-15); however:
> >>   Package qemu-server is not configured yet.
> >
> >
> > dpkg: error processing package pve-ha-manager (--configure):
> >>  dependency problems - leaving triggers unprocessed
> >> Processing triggers for initramfs-tools (0.140) ...
> >> update-initramfs: Generating /boot/initrd.img-5.11.22-5-pve
> >> Running hook script 'zz-proxmox-boot'..
> >> Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private
> mount
> >> namespace..
> >> Copying and configuring kernels on /dev/disk/by-uuid/5994-C1A0
> >> Copying kernel and creating boot-entry for 5.11.22-4-pve
> >> Copying kernel and creating boot-entry for 5.11.22-5-pve
> >> Processing triggers for libc-bin (2.31-13) ...
> >> Processing triggers for man-db (2.9.4-2) ...
> >> Processing triggers for mailcap (3.69) ...
> >> Errors were encountered while processing:
> >>  trousers
> >>  swtpm-tools
> >>  qemu-server
> >>  pve-manager
> >>  pve-ha-manager
> >> E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> >
> > Does anybody know what this is?
>
> It's related to TPM, swtmp-tools pulls it in and that in turn gets pulled
> in by
> qemu-server which now provides TPM support for guests.
>
> It seems it init script was a bit borked[0], but that only shows up on
> some systems,
> FWICT ones that where updated from pre PVE 6 or even older.
>
> I re-build the upstream package with a more resilient postinst and init
> script and
> uploaded that to pvetest as `trousers` in version `0.3.14+fixed1-1.2+pve1`
> (fwiw,
> the "fixed" part in the version was already there and not my invention ;)
>
> An error may still get printed on update, but it should not fail the whole
> update
> itself anymore (which has no use on its own).
>
> [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895201
>
> hope that helps,
> Thomas
>
>

Re: [pve-devel] trousers error in latest test repo?

[Thomas Lamprecht]

Hi Victor,

On 06.10.21 10:15, Victor Hooi wrote:
> Ah - interesting - as a data-point, this was a new install of Proxmox 7.0-2
> (from the ISO image), and then I ran an apt update, apt dist-upgrade
> directly after first boot.

very interesting indeed, I mainly tested on a cluster that was installed with PVE
6.2 and a development VM that was originally a Bullseye pre-release ISO, it worked
out OK on both.

> 
> I just did an apt update, apt dist-upgrade again - and there was one
> package to update (trousers).
> 
> I am still getting an error with this version:

Hmm first I thought that could be the "stop-before-upgrade" of the old, broken
version, but that makes not much sense as your error is on a "start".
Did you edit `/etc/init.d/trousers` before the upgrade?

And could you please still try `apt install --reinstall trousers` to verify if
it was that.

> 
> Unpacking trousers (0.3.14+fixed1-1.2+pve1) over (0.3.14+fixed1-1.2) ...
>> Setting up trousers (0.3.14+fixed1-1.2+pve1) ...
>> Installing new version of config file /etc/init.d/trousers ...
>> Job for trousers.service failed because the control process exited with
>> error code.
>> See "systemctl status trousers.service" and "journalctl -xe" for details.
>> invoke-rc.d: initscript trousers, action "start" failed.
>> ● trousers.service - LSB: starts tcsd
>>      Loaded: loaded (/etc/init.d/trousers; generated)
>>      Active: failed (Result: exit-code) since Wed 2021-10-06 01:13:08 PDT;
>> 4ms ago
>>        Docs: man:systemd-sysv-generator(8)
>>     Process: 192905 ExecStart=/etc/init.d/trousers start (code=exited,
>> status=30)
>>         CPU: 9ms
> 
> Oct 06 01:13:08 mgmt1 systemd[1]: Starting LSB: starts tcsd...
>> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TDDL[192910]: TrouSerS ioctl:
>> (25) Inappropriate ioctl for device
>> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TDDL[192910]: TrouSerS Falling
>> back to Read/Write device support.
>> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TCS[192910]: TrouSerS ERROR: TCS
>> GetCapability failed with result = 0x1e
>> Oct 06 01:13:08 mgmt1 trousers[192905]: Starting Trusted Computing daemon:
>> tcsd
>> Oct 06 01:13:08 mgmt1 trousers[192911]:  failed!
>> Oct 06 01:13:08 mgmt1 systemd[1]: trousers.service: Control process
>> exited, code=exited, status=30/n/a
>> Oct 06 01:13:08 mgmt1 systemd[1]: trousers.service: Failed with result
>> 'exit-code'.
>> Oct 06 01:13:08 mgmt1 systemd[1]: Failed to start LSB: starts tcsd.
> 
> I should note that the spec sheet for the NUC7i5BNK says it does not have a
> TPM - would that be related at all to these errors?

Well yes, that was an issue with the old version, it checked that in a wrong way.
But the newer, just uploaded package adapted that part, which was also tested by
creating and dropping a fake /deb/tmp1 node, so it should work out.

Or do you have a node?

ls -l /dev/tmp* 

cheers,
Thomas

Re: [pve-devel] trousers error in latest test repo?

[Victor Hooi]

Hi,

Nope, I haven't edited /etc/init.d/trousers. (I did view it, because of this
post
<https://unix.stackexchange.com/questions/633563/can-not-start-trousers-service-giving-error-trousers-ioctl-25-inappropriat>
and
curiosity but didn't make any changes).

I just tested a reinstall, as suggested - I still get an error:

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+pve1)
> ...
> Setting up trousers (0.3.14+fixed1-1.2+pve1) ...
> Job for trousers.service failed because the control process exited with
> error code.
> See "systemctl status trousers.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript trousers, action "restart" failed.
> ● 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=/etc/init.d/trousers start (code=exited,
> status=30)
>         CPU: 9ms


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: TCS
GetCapability failed with result = 0x1e
Oct 06 01:37:06 mgmt1 trousers[199367]: Starting Trusted Computing daemon:
tcsd
Oct 06 01:37:06 mgmt1 trousers[199373]:  failed!
Oct 06 01:37:06 mgmt1 systemd[1]: trousers.service: Control process exited,
code=exited, status=30/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) ...

What do you mean by whether I have a node?

root@mgmt1:/etc/apt/sources.list.d# ls -l /dev/tmp*
> ls: cannot access '/dev/tmp*': No such file or directory


Thanks,
Victor

On Wed, 6 Oct 2021 at 19:32, Thomas Lamprecht <t.lamprecht@proxmox.com>
wrote:

> Hi Victor,
>
> On 06.10.21 10:15, Victor Hooi wrote:
> > Ah - interesting - as a data-point, this was a new install of Proxmox
> 7.0-2
> > (from the ISO image), and then I ran an apt update, apt dist-upgrade
> > directly after first boot.
>
> very interesting indeed, I mainly tested on a cluster that was installed
> with PVE
> 6.2 and a development VM that was originally a Bullseye pre-release ISO,
> it worked
> out OK on both.
>
> >
> > I just did an apt update, apt dist-upgrade again - and there was one
> > package to update (trousers).
> >
> > I am still getting an error with this version:
>
> Hmm first I thought that could be the "stop-before-upgrade" of the old,
> broken
> version, but that makes not much sense as your error is on a "start".
> Did you edit `/etc/init.d/trousers` before the upgrade?
>
> And could you please still try `apt install --reinstall trousers` to
> verify if
> it was that.
>
> >
> > Unpacking trousers (0.3.14+fixed1-1.2+pve1) over (0.3.14+fixed1-1.2) ...
> >> Setting up trousers (0.3.14+fixed1-1.2+pve1) ...
> >> Installing new version of config file /etc/init.d/trousers ...
> >> Job for trousers.service failed because the control process exited with
> >> error code.
> >> See "systemctl status trousers.service" and "journalctl -xe" for
> details.
> >> invoke-rc.d: initscript trousers, action "start" failed.
> >> ● trousers.service - LSB: starts tcsd
> >>      Loaded: loaded (/etc/init.d/trousers; generated)
> >>      Active: failed (Result: exit-code) since Wed 2021-10-06 01:13:08
> PDT;
> >> 4ms ago
> >>        Docs: man:systemd-sysv-generator(8)
> >>     Process: 192905 ExecStart=/etc/init.d/trousers start (code=exited,
> >> status=30)
> >>         CPU: 9ms
> >
> > Oct 06 01:13:08 mgmt1 systemd[1]: Starting LSB: starts tcsd...
> >> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TDDL[192910]: TrouSerS ioctl:
> >> (25) Inappropriate ioctl for device
> >> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TDDL[192910]: TrouSerS Falling
> >> back to Read/Write device support.
> >> Oct 06 01:13:08 mgmt1 tcsd[192910]: TCSD TCS[192910]: TrouSerS ERROR:
> TCS
> >> GetCapability failed with result = 0x1e
> >> Oct 06 01:13:08 mgmt1 trousers[192905]: Starting Trusted Computing
> daemon:
> >> tcsd
> >> Oct 06 01:13:08 mgmt1 trousers[192911]:  failed!
> >> Oct 06 01:13:08 mgmt1 systemd[1]: trousers.service: Control process
> >> exited, code=exited, status=30/n/a
> >> Oct 06 01:13:08 mgmt1 systemd[1]: trousers.service: Failed with result
> >> 'exit-code'.
> >> Oct 06 01:13:08 mgmt1 systemd[1]: Failed to start LSB: starts tcsd.
> >
> > I should note that the spec sheet for the NUC7i5BNK says it does not
> have a
> > TPM - would that be related at all to these errors?
>
> Well yes, that was an issue with the old version, it checked that in a
> wrong way.
> But the newer, just uploaded package adapted that part, which was also
> tested by
> creating and dropping a fake /deb/tmp1 node, so it should work out.
>
> Or do you have a node?
>
> ls -l /dev/tmp*
>
> cheers,
> Thomas
>
>
>

Re: [pve-devel] trousers error in latest test repo?

[Thomas Lamprecht]

On 06.10.21 10:39, Victor Hooi wrote:
> Hi,
> 
> Nope, I haven't edited /etc/init.d/trousers. (I did view it, because of this
> post
> <https://unix.stackexchange.com/questions/633563/can-not-start-trousers-service-giving-error-trousers-ioctl-25-inappropriat>
> and
> curiosity but didn't make any changes).
> 
> 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 making 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 ;-) 

> 
> 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+pve1)
>> ...
>> Setting up trousers (0.3.14+fixed1-1.2+pve1) ...
>> Job for trousers.service failed because the control process exited with
>> error code.
>> See "systemctl status trousers.service" and "journalctl -xe" for details.
>> invoke-rc.d: initscript trousers, action "restart" failed.
>> ● 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=/etc/init.d/trousers start (code=exited,
>> status=30)
>>         CPU: 9ms
> 
> 
> 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: TCS
> GetCapability failed with result = 0x1e
> Oct 06 01:37:06 mgmt1 trousers[199367]: Starting Trusted Computing daemon:
> tcsd
> Oct 06 01:37:06 mgmt1 trousers[199373]:  failed!
> Oct 06 01:37:06 mgmt1 systemd[1]: trousers.service: Control process exited,
> code=exited, status=30/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) ...
> 
> 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..

> 
> root@mgmt1:/etc/apt/sources.list.d# ls -l /dev/tmp*
>> ls: cannot access '/dev/tmp*': No such file or directory
> 

Re: [pve-devel] trousers error in latest test repo?

[Thomas Lamprecht]

On 06.10.21 10:39, Victor Hooi wrote:
> root@mgmt1:/etc/apt/sources.list.d# ls -l /dev/tmp*
>> ls: cannot access '/dev/tmp*': No such file or directory

argh, misspelled tpm with tmp -.- can you retry:

ls -l /dev/tpm*

- Thomas