From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Victor Hooi <victorhooi@yahoo.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] trousers error in latest test repo?
Date: Wed, 6 Oct 2021 10:32:45 +0200 [thread overview]
Message-ID: <c43f435a-fb1f-304e-1c69-3edf71d2e705@proxmox.com> (raw)
In-Reply-To: <CAMnnoU+hH7W=mgfejkMuZa_bK+G3Bwn9GGnYpQL+77wUKwq2hA@mail.gmail.com>
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
next prev parent reply other threads:[~2021-10-06 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMnnoUKQCHYBCz6_chonTW9Az73N1kgTBGs6Bsw2K=CqdGK17g.ref@mail.gmail.com>
2021-10-05 22:51 ` Victor Hooi
2021-10-06 7:17 ` Thomas Lamprecht
2021-10-06 8:15 ` Victor Hooi
2021-10-06 8:32 ` Thomas Lamprecht [this message]
2021-10-06 8:39 ` Victor Hooi
2021-10-06 8:51 ` Thomas Lamprecht
2021-10-06 9:03 ` Thomas Lamprecht
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=c43f435a-fb1f-304e-1c69-3edf71d2e705@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=victorhooi@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal