Cumulus Support

Hello
This evening I decided to re-install CumulusMX on my raspberry pi zero from scratch (I had a very old - but working - installation of Cumulus MX).
I downloaded the 3.18 iso, installed with the raspberry tool and booted. But Cumulus crashes.

With systemctl status cumulusmx I get:


● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Tue 2022-06-28 00:44:00 CEST; 6min ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 587 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCES>
Process: 602 ExecStopPost=/bin/rm -f /tmp/CumulusMX.exe.lock (code=exited, status=0/SUCCESS)
Main PID: 588 (code=killed, signal=ABRT)
CPU: 8.913s

giu 28 00:43:49 raspberrypi systemd[1]: Starting CumulusMX service...
giu 28 00:43:50 raspberrypi systemd[1]: Started CumulusMX service.
giu 28 00:44:00 raspberrypi systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
giu 28 00:44:00 raspberrypi systemd[1]: cumulusmx.service: Failed with result 'signal'.
giu 28 00:44:00 raspberrypi systemd[1]: cumulusmx.service: Consumed 8.913s CPU time.





If I try to start up manually with mono CumulusMX.exe I get

=================================================================
Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

=================================================================
Native stacktrace:
=================================================================
(No frames)


=================================================================
Telemetry Dumper:
=================================================================
Entering thread summarizer pause from 0x3069717184x
Finished thread summarizer pause from 0x3069717184x.
Failed to create breadcrumb file (null)/crash_hash_0x15b1c4952

Waiting for dumping threads to resume

=================================================================
External Debugger Dump:
=================================================================
[New LWP 631]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
0xb6bf84d4 in __GI___wait4 (pid=633, stat_loc=0xbeb37004, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
27 ../sysdeps/unix/sysv/linux/wait4.c: File o directory non esistente.
Id Target Id Frame
* 1 Thread 0xb6f82ac0 (LWP 630) "mono" 0xb6bf84d4 in __GI___wait4 (pid=633, stat_loc=0xbeb37004, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
2 Thread 0xb5fff400 (LWP 631) "SGen worker" futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/nptl/futex-internal.h:186

Thread 2 (Thread 0xb5fff400 (LWP 631) "SGen worker"):
#0 futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/nptl/futex-internal.h:186
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x0, cond=0x40d268) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x40d268, mutex=0x0) at pthread_cond_wait.c:638
#3 0x002f50e4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb6f82ac0 (LWP 630) "mono"):
#0 0xb6bf84d4 in __GI___wait4 (pid=633, stat_loc=0xbeb37004, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1 0x0009cfd8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 630) detached]

=================================================================
Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0xb4513360):0xb4513350 00 00 00 ea d4 d7 66 00 00 00 9f e7 10 00 8d e5 ......f.........
0xb4513360 5b f0 7f f5 10 00 9d e5 00 10 80 e5 18 d0 8d e2 [...............
0xb4513370 00 81 bd e8 40 41 2d e9 1c d0 4d e2 00 60 a0 e1 ....@A-...M..`..
0xb4513380 10 10 8d e5 00 00 56 e3 0d 00 00 0b 08 10 86 e2 ......V.........

=================================================================
Managed Stacktrace:
=================================================================
at System.Exception:.cctor <0x00038>
at System.Object:runtime_invoke_void <0x0007f>
at <unknown> <0xffffffff>
at System.SystemException:.ctor <0x0001b>
at System.OutOfMemoryException:.ctor <0x0001b>
at <Module>:runtime_invoke_void__this___object <0x0010b>
=================================================================


I followed the steps on the wiki https://cumuluswiki.org/a/Raspberry_Pi_Image (changed the locale and the timezone as stated), but it seems Mono is the problem...

Note I have the same hardware as before (same raspberry, same sd, same Fine Offset weather station connected)

Can someone help me?

Thanks

UPDATE:

I dist-updated the system and now cumulus boots correctly. Strange behavior, I expected a pre-packed ISO worked out-of-the-box... BTW you can close, thanks!

The image will not work "out of the box" on older pi Zeros as they had a different processor architecture.
On those machines you need to remove/reinstall mono (effectively what your update probably did) as it compiles some components according to your processor architecture on install.