Cumulus Support

Posted: **Thu 10 Nov 2022 12:16 pm**

Hi, I have installed this version onto my RPI and can connect to the RPI just fine but Cumulusmx is not running and comes up with an error when I try to run it manually. Using the sudo systemctl status cumulusmx command it give me this...

cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Thu 2022-11-10 12:09:45 GMT; 2min 6s ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 516 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
Process: 565 ExecStopPost=/bin/rm -f /tmp/CumulusMX.exe.lock (code=exited, status=0/SUCCESS)
Main PID: 517 (code=killed, signal=ABRT)
CPU: 8.823s

Nov 10 12:09:30 raspberrypi systemd[1]: Starting CumulusMX service...
Nov 10 12:09:30 raspberrypi systemd[1]: Started CumulusMX service.
Nov 10 12:09:45 raspberrypi systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
Nov 10 12:09:45 raspberrypi systemd[1]: cumulusmx.service: Failed with result 'signal'.
Nov 10 12:09:45 raspberrypi systemd[1]: cumulusmx.service: Consumed 8.823s CPU time.

It has worked fine for me with previous versions

Anyone come across this as well / any suggestions on how to fix?

Thanks

Posted: **Thu 10 Nov 2022 1:40 pm**

Did you happen to update your rPi?

I am running v3.22.3 and when I updated my rPi two days ago it broke my CumulusMX.

I restored from my backup, updated and it broke again. I reinstalled everything from scratch including updating to current and all is good again.

Posted: **Tue 15 Nov 2022 9:41 am**

I installed the latest RPI version of CumulusMX onto a new SD card, so could swap back very easily if there was a problem.
The latest version comes with is it called Bullseye? which is a later version of the OS than on my old SD card.
I did try updating the OS but that did not help.

Posted: **Tue 15 Nov 2022 10:49 am**

High metofficemk, i use this cumulusmx.service on a RPI4B with Debian Bullseye

Code: Select all

[Unit]
Description=CumulusMX service
Documentation=https://cumuluswiki.org/a/Main_Page
After=network-online.target

[Service]
User=root
Group=root
ExecStart=/usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -d:/opt/CumulusMX CumulusMX.exe -service
Type=forking
ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

root@raspberrypi:~# sudo systemctl status cumulusmx
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor pre>
Active: activating (start) since Tue 2022-11-15 11:38:27 CET; 8s ago
Docs: https://cumuluswiki.org/a/Main_Page
Cntrl PID: 23427 (mono)
Tasks: 15 (limit: 4915)
CPU: 5.059s
CGroup: /system.slice/cumulusmx.service
└─23427 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -d:/opt/C>

Nov 15 11:38:27 raspberrypi systemd[1]: Starting CumulusMX service...
Nov 15 11:38:30 raspberrypi mono[23427]: Cumulus running at: http://localhost:8>
Nov 15 11:38:32 raspberrypi mono[23427]: 15/11/2022 11:38:32
Nov 15 11:38:32 raspberrypi mono[23427]: Type Ctrl-C to terminate
Nov 15 11:38:32 raspberrypi mono[23427]: Downloading Archive Data
Nov 15 11:38:32 raspberrypi mono[23427]: - No Archive data available
Nov 15 11:38:32 raspberrypi mono[23427]: Downloading Archive Data
Nov 15 11:38:32 raspberrypi mono[23427]: - No Archive data available
lines 1-18/18 (END)...skipping...

Sjaak.

Posted: **Tue 15 Nov 2022 1:22 pm**

@metofficemk, which model of rPi do you have?
Does it generate an MXdiags file? If so, can you post it please.

Posted: **Fri 06 Jan 2023 11:25 am**

I have the same problem with a fresh install on blank SD card of version 3.23.0.
I have had this issue for over a year, just been hoping a new version will fix the issue, but no

I run sudo systemctl status cumulusmx , and it always fails as "Active: failed (Result: signal)" I have no idea what this means or what to do.
See details below...

● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Fri 2023-01-06 10:43:45 GMT; 21min ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 585 ExecStopPost=/bin/rm -f /tmp/CumulusMX.exe.lock (code=exited, status=0/SUCCESS)
Main PID: 524 (code=killed, signal=ABRT)
CPU: 8.912s

Jan 06 10:43:10 raspberrypi systemd[1]: Starting CumulusMX service...
Jan 06 10:43:10 raspberrypi systemd[1]: Started CumulusMX service.
Jan 06 10:43:45 raspberrypi systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
Jan 06 10:43:45 raspberrypi systemd[1]: cumulusmx.service: Failed with result 'signal'.
Jan 06 10:43:45 raspberrypi systemd[1]: cumulusmx.service: Consumed 8.912s CPU time.

Can you please help me to solve this, thank you

I do have a much older version running fine but it would be good to have the updated version going.
Any questions just let me know.
Thanks

Posted: **Fri 06 Jan 2023 11:41 am**

metofficemk wrote: ↑Fri 06 Jan 2023 11:25 am I do have a much older version running fine but it would be good to have the updated version going.
Any questions just let me know.
Thanks

You could start by answering the questins that Mark asked you on November. What RPi model are you using? Pi zero, Pi2, Pi3, or Pi4? And send the mxdiags log file if one is generated.

—
Sami

Posted: **Fri 06 Jan 2023 12:31 pm**

ive just tested the img on pi 3 and it all seem to work fine

try my config file

Code: Select all

[Unit]
Description=CumulusMX service
Documentation=https://cumuluswiki.org/a/Main_Page
After=network-online.target

[Service]
User=root
Group=root
ExecStart=/usr/bin/mono-service -d:/home/pi/usb-drive/CumulusMX/Cmx-WLL CumulusMX.exe -service
Type=forking
ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock

[Install]
WantedBy=multi-user.target

Posted: **Fri 06 Jan 2023 3:43 pm**

Hi Dazza1223

Thanks for your post.
Do I simply copy and past your lines into the files on the SD card called config.txt?
It currently looks like this...

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# Disable compensation for displays with overscan
disable_overscan=1

[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1

[all]

[pi4]
# Run as fast as firmware / board allows
arm_boost=1

[all]

Do I add your lines to the bottom of the file?

Thanks

Posted: **Fri 06 Jan 2023 4:14 pm**

no u edit this file

fist stop cmx bye running

sudo systemctl stop cumulusmx

sudo nano /etc/systemd/system/cumulusmx.service

and replace it with my one

Code: Select all

[Unit]
Description=CumulusMX service
Documentation=https://cumuluswiki.org/a/Main_Page
After=network-online.target

[Service]
User=root
Group=root
ExecStart=/usr/bin/mono-service -d:/home/install/CumulusMX CumulusMX.exe -service
Type=forking
ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock

[Install]
WantedBy=multi-user.target

then run

sudo systemctl daemon-reload

and

sudo systemctl enable cumulusmx

then start cmx

sudo systemctl start cumulusmx

Posted: **Fri 06 Jan 2023 11:08 pm**

I've just re read your posts you state that u have downloaded a rpi image fresh on a sd card well there is ur problem as ur trying to run cmx twice as it automatically run the first boot anyway so ur trying to run it twice completely in a different directory

The directory is home/opt I think top off my head I will check tomorrow

Posted: **Sat 07 Jan 2023 6:51 pm**

SamiS wrote: ↑Fri 06 Jan 2023 11:41 am
metofficemk wrote: ↑Fri 06 Jan 2023 11:25 am I do have a much older version running fine but it would be good to have the updated version going.
Any questions just let me know.
Thanks
You could start by answering the questins that Mark asked you on November. What RPi model are you using? Pi zero, Pi2, Pi3, or Pi4? And send the mxdiags log file if one is generated.

The reason we are asking the hardware you use, is that if you are using Pi Zero, Pi 1 or an very early Pi2, then you have to remove an reinstall mono-complete -package so it will be compiled to work on the earlier processor model. This happens by running following commands:

sudo apt remove mono-complete
sudo apt install mono-complete

At least on Pi Zero it will take several hours to complete.

Also if you look at the MXdiags folder on /opt/CumulusMX/MXdiags, there should be a ServiceConsoleLog.txt and another logfile that is named by the date and time of the latest startup attempt. It could give valuable information about the problem instead of trying to guess what is wrong.

--
Sami

Posted: **Sat 07 Jan 2023 7:57 pm**

I am using a Raspberry Pi W Zero 1.1. My output from pinout is
```
Revision : 9000c1
SoC : BCM2835
RAM : 512MB
```

I am able to run mono --version without any obvious error

```
cmx@raspberrypi:/opt/CumulusMX $ mono --version
Mono JIT compiler version 6.12.0.182 (tarball Tue Jun 14 22:53:32 UTC 2022)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: normal
Notifications: epoll
Architecture: armel,vfp+hard
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: preemptive
GC: sgen (concurrent by default)
```

I tried using your config file, but it did not make any difference.

There are no files in /opt/CumulusMX/MXdiags. Should I be looking somewhere else?

I tried to launch CumulusMX.exe with -debug directly and got this output:

```
cmx@raspberrypi:/opt/CumulusMX $ sudo mono CumulusMX.exe -debug

=================================================================
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 0x3069254336x
Finished thread summarizer pause from 0x3069254336x.
Failed to create breadcrumb file (null)/crash_hash_0x15b1c4952

Waiting for dumping threads to resume

=================================================================
External Debugger Dump:
=================================================================
[New LWP 742]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
0xb6b84034 in __GI___wait4 (pid=744, stat_loc=0xbe801024, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
27 ../sysdeps/unix/sysv/linux/wait4.c: No such file or directory.
Id Target Id Frame
* 1 Thread 0xb6f11ac0 (LWP 741) "mono" 0xb6b84034 in __GI___wait4 (pid=744, stat_loc=0xbe801024, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
2 Thread 0xb5fff400 (LWP 742) "SGen worker" futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/nptl/futex-internal.h:186

Thread 2 (Thread 0xb5fff400 (LWP 742) "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 0x002f510c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb6f11ac0 (LWP 741) "mono"):
#0 0xb6b84034 in __GI___wait4 (pid=744, stat_loc=0xbe801024, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1 0x0009cfe8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 741) 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>
=================================================================
Aborted
cmx@raspberrypi:/opt/CumulusMX $
```

I tried reinstalling mono using these two commands:

```
sudo apt autoremove mono-complete
sudo apt install mono-complete
```

This is running now, so I'll leave it going overnight and let you know, thanks

Posted: **Sat 07 Jan 2023 8:16 pm**

metofficemk wrote: ↑Sat 07 Jan 2023 7:57 pm I am using a Raspberry Pi W Zero 1.1. My output from pinout is
```
=================================================================
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.

I tried reinstalling mono using these two commands:

```
sudo apt autoremove mono-complete
sudo apt install mono-complete
```

This is running now, so I'll leave it going overnight and let you know, thanks

Since you are using Pi Zero and Mono seems to crash brutally when trying to start CMX, most likely the issue will be resolved by the mono reinstall. This is not the first time we've seen this during last years. The early crash also explains why your MXdiags is empty.

Unfortunately the reinstall of mono includes recompiling of some binaries, and therefore it takes a very long time to complete. Many have thought that it has frozen, but hang tight. It should take less than 24 hours

--
Sami

Posted: **Sat 07 Jan 2023 9:43 pm**

It did not take that long to reinstall Mono?

I now have this...
cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2023-01-07 20:17:27 GMT; 1h 23min ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 237 ExecStart=/usr/bin/mono-service -d:/home/install/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
Process: 363 ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock (code=exited, status=1/FAILURE)
Main PID: 239 (code=exited, status=1/FAILURE)
CPU: 1.159s

Jan 07 20:17:19 raspberrypi systemd[1]: Starting CumulusMX service...
Jan 07 20:17:22 raspberrypi systemd[1]: Started CumulusMX service.
Jan 07 20:17:26 raspberrypi mono[239]: CumulusMX.exe: Could not change to directory /home/install/CumulusMX
Jan 07 20:17:27 raspberrypi systemd[1]: cumulusmx.service: Main process exited, code=exited, status=1/FAILURE
Jan 07 20:17:27 raspberrypi rm[363]: /bin/rm: cannot remove '/tmp/CumulusMX.exe.lock': No such file or directory
Jan 07 20:17:27 raspberrypi systemd[1]: cumulusmx.service: Control process exited, code=exited, status=1/FAILURE
Jan 07 20:17:27 raspberrypi systemd[1]: cumulusmx.service: Failed with result 'exit-code'.
Jan 07 20:17:27 raspberrypi systemd[1]: cumulusmx.service: Consumed 1.159s CPU time.

Its a different reason for failing

Cumulus Support

Problem with version 3.22.0 for RPI

Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI

Re: Problem with version 3.22.0 for RPI