From: Kenneth Goldman <kgoldman(a)us.ibm.com>
Sent: Tuesday, March 9, 2021 2:17 PM
Subject: [tpm2] Re: abrmd crashing - how to debug?
> From: Tadeusz Struk <tstruk(a)gmail.com>
> To: Kenneth Goldman <kgoldman(a)us.ibm.com>, tpm2(a)lists.01.org
> Date: 03/09/2021 02:51 PM
> Subject: [EXTERNAL] Re: [tpm2] abrmd crashing - how to debug?
> Hi Ken,
> On 3/5/21 2:29 PM, Kenneth Goldman wrote:
> > Ubuntu focal with WSL, abrmd compiled from source
> > After about 5 minutes of sending commands, abrmd crashes. I
> originally found it with keylime, but I can reproduce it with a simple
> bash loop on pcrread.
> > abrmd exits, the tool output is:
> > ** (process:21067): CRITICAL **: 17:25:10.862: failed to allocate
> dbus proxy object: Could not connect: Connection refused
> > WARNING:tcti:src/tss2-tcti/tctildr.c:79:tcti_from_init() TCTI init
> for function 0x7ff5f6dbbe10 failed with a0008
> > WARNING:tcti:src/tss2-tcti/tctildr.c:109:tcti_from_info() Could
> not initialize TCTI named: tcti-abrmd
> > ERROR:tcti:src/tss2-tcti/tctildr-dl.c:154:tcti_from_file() Could
> not initialize TCTI file: tabrmd
> > ERROR:tcti:src/tss2-tcti/tctildr.c:416:Tss2_TctiLdr_Initialize_Ex
> () Failed to instantiate TCTI
> > ERROR: Could not load tcti, got:
> > How would I debug?
> > I would expect that nothing that a single application does should
> crash abrmd.
> I think it's not the abrmd that's failing, but the application that is
> trying to use tcti-abrmd to communicate with abrmd running in the
> It can not get the dbus handler so it just prints an error and fails.
> Can you look for some system dbus logs to see if there are any errors there?
Sorry, but abrmd exits - with no error message. Its window just goes back to the
command prompt. I'd call that a crash, assuming it should never exit.
It shouldn't under almost all situations. However, some asserts exist on client state,
like this bug:
But the fact that there's no message seems odd. What's the exit code? I would
imagine we would see
Something like a segfault message or something else if it truly crashed.
If you tell me where 'the system dbus logs' are, I'd be willing to post them.
Since you're just running it as a process from a shell and not a system service, all
the logs will be to stderr/stdout.
Can you enable env variable G_MESSAGES_DEBUG=all when you run tpm2-abrmd and send us the