3204 crash

[HansR]

I installed 3204 this morning but it crashes at the point where it should start sending the interval datafiles.
I tried it three times (attached the last time with debug/data on) and all three times it failed.
Attached are the logfile and the ServiceConsoleLog.

I go back to 3203.

[mcrossley]

I don't see any issues in the either console log or the MXdiags log file?

[HansR]

True, it just quits.
The only thing it indicates is where

[mcrossley]

The email sending is fully trapped, so it is unlikely the error is in CMX.
You definitely have the Mimekit.dll v3.4.0 in the CMX folder?

[mcrossley]

And Mailkit.dll v3.3.0?

[HansR]

The email sending is fully trapped, so it is unlikely the error is in CMX.
You definitely have the Mimekit.dll v3.4.0 in the CMX folder?

I always copy the complete directory tree over to the installation. So I assume yes (can't check that because I reinstalled 3203 which has the 3.3.0 version of that library).

I will reinstall 3204 again and check that before starting, then start and see what happens.

[HansR]

It is the same effect and the key is - I think - that I don't receive that email of the battery low warning (I do receive it from 3203). So it appears to be the sending of the mail. Somewhere even if fully trapped. My account is correct says 3203, it has always worked from the moment the email feature was implemented.

[Edit:] And just to be complete: yes the versions of those libraries are correct.

[HansR]

When I ask the systemctl status it says:

Code: Select all

sep 03 15:52:58 rpiCMX3 systemd[1]: Starting CumulusMX service...
sep 03 15:52:58 rpiCMX3 systemd[1]: Started CumulusMX service.
sep 03 16:00:06 rpiCMX3 systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
sep 03 16:00:06 rpiCMX3 systemd[1]: cumulusmx.service: Failed with result 'signal'.
sep 03 16:00:06 rpiCMX3 systemd[1]: cumulusmx.service: Consumed 56.276s CPU time.

So it receives an abort signal from somewhere (the mail lib?)

[Edit:] The journal does not give anymore beyond that

[mcrossley]

Which email provider are you using?
I'm using Gmail and mine are still working with 3204.

The email package was updated in 3204, I'll check and see if they have anyone else reporting issues...

[HansR]

Which email provider are you using?

I am using gmail too.

I don't know how linux uses caching dll's. Could it be that the previous version is still in memory?
I'll try a reboot anyway.

[mcrossley]

Could you also switch on email logging and post the SMTP log file.

[HansR]

I did do a restart and monitored with htop. I managed to get the following screenshot a split second before the crash, maybe you can get something out of it:

sscreenshot 2022-09-03.jpg

I'll switch on the email logging now.

[HansR]

In th mean time I found a mono-crash json file: mono_crash.edaf9aa46.5.json is attached (as .txt).
Logfile will follow at next crash.

[HansR]

I can't find an email log. Where should it be and what is the file name?

Beside that I saw that just before the activation of the GNU debugger as shown in the image, the mono-hang-watchdog is activated for just a moment.

[HansR]

I'll update mono to the current version for bullseye.