Cumulus Support

Posted: **Wed 02 Jun 2021 9:33 pm**

With a newly downlaoded Raspberry Pi Image, updated manually to build 3133 and copied in my old data, CumulusMX is starting then immediately failing. Can someone tell me what's wrong from this:

Further investigation: same SD card runs fine on a Pi4. It's looking like a mono incompatibility with PiZero?
Mark (or other?), can you tell me the zip file name for previous Raspberry Pi images, which previously worked? As you didn't make an image for each build, it's impossible to find the zip file without knowing which builds exist (the server displays a few files at https://cumuluswiki.org/Downloads - but nothing recent and no Pi images)

pi@cumulusmx:/tmp $ sudo systemctl start cumulusmx
pi@cumulusmx:/tmp $ sudo systemctl status cumulusmx
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-06-02 22:20:57 BST; 4s ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 624 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
Main PID: 625 (mono)
Tasks: 3 (limit: 877)
CGroup: /system.slice/cumulusmx.service
├─625 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -d:/opt/CumulusMX CumulusMX.exe -service
└─628 /usr/bin/gdb -batch -x /tmp/mono-gdb-commands.625 -nx

Jun 02 22:20:57 cumulusmx systemd[1]: Starting CumulusMX service...
Jun 02 22:20:57 cumulusmx systemd[1]: Started CumulusMX service.
pi@cumulusmx:/tmp $ sudo systemctl status cumulusmx
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Wed 2021-06-02 22:21:10 BST; 41s ago
Docs: https://cumuluswiki.org/a/Main_Page
Process: 624 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
Process: 635 ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock (code=exited, status=1/FAILURE)
Main PID: 625 (code=killed, signal=ABRT)

Jun 02 22:20:57 cumulusmx systemd[1]: Starting CumulusMX service...
Jun 02 22:20:57 cumulusmx systemd[1]: Started CumulusMX service.
Jun 02 22:21:10 cumulusmx systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
Jun 02 22:21:10 cumulusmx rm[635]: /bin/rm: cannot remove '/tmp/CumulusMX.exe.lock': No such file or directory
Jun 02 22:21:10 cumulusmx systemd[1]: cumulusmx.service: Control process exited, code=exited, status=1/FAILURE
Jun 02 22:21:10 cumulusmx systemd[1]: cumulusmx.service: Failed with result 'signal'.

and I get this if I try to run CumulusMX manually:

pi@cumulusmx:/opt/CumulusMX $ sudo mono CumulusMX.exe

=================================================================
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:
=================================================================
Could not exec mono-hang-watchdog, expected on path '/etc/../bin/mono-hang-watchdog' (errno 2)
Entering thread summarizer pause from 0x3070130448x
Finished thread summarizer pause from 0x3070130448x.
Failed to create breadcrumb file (null)/crash_hash_0x15b1c4952

Waiting for dumping threads to resume

=================================================================
External Debugger Dump:
=================================================================
[New LWP 673]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__waitpid (options=0, stat_loc=0xbef9d054, pid=675) at ../sysdeps/unix/sysv/linux/waitpid.c:30
30 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
Id Target Id Frame
* 1 Thread 0xb6fe7910 (LWP 672) "mono" __waitpid (options=0, stat_loc=0xbef9d054, pid=675) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2 Thread 0xb5fff430 (LWP 673) "SGen worker" futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/unix/sysv/linux/futex-internal.h:88

Thread 2 (Thread 0xb5fff430 (LWP 673)):
#0 futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x0, cond=0x40d268) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x40d268, mutex=0x0) at pthread_cond_wait.c:655
#3 0x002f495c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb6fe7910 (LWP 672)):
#0 __waitpid (options=0, stat_loc=0xbef9d054, pid=675) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 __waitpid (pid=675, stat_loc=0xbef9d054, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2 0x0009cbc4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 672) detached]

=================================================================
Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0xb4513338):0xb4513328 00 00 00 ea fc d7 66 00 00 00 9f e7 10 00 8d e5 ......f.........
0xb4513338 5b f0 7f f5 10 00 9d e5 00 10 80 e5 18 d0 8d e2 [...............
0xb4513348 00 81 bd e8 40 41 2d e9 1c d0 4d e2 00 60 a0 e1 ....@A-...M..`..
0xb4513358 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

Posted: **Thu 03 Jun 2021 11:03 am**

Did the image run OK before you upgraded it?

I only test the image on Model 3 or above.

Posted: **Thu 03 Jun 2021 12:57 pm**

There is an older image here: https://cumuluswiki.org/Downloads/rpi-CMX-3.10.5.zip

Posted: **Thu 03 Jun 2021 12:59 pm**

I was running a previous image (I think the first version?) on a Pi ZeroW, with CumulusMX manually subsequently updated with version changes.

I needed to re-install to a blank SD card as the previous one was destroyed by a failed 'sudo apt-get upgrade' - there was an error during kernel update which made the OS unbootable. I was able to read the data OK.

So with the old Pi Image zip filename(s) I should be able to use that and update CumulusMX to current version. Happy to report back on what happens.
(The Wiki says to get the old image by just changing the filename to the relevant version - but the server will not reveal which versions exist)

Posted: **Thu 03 Jun 2021 3:29 pm**

PiZero is working fine with the v3.10.5 image updated with CumulusMX build 3133 (v3.11.4).

Now, dare I try 'sudo apt-get-upgrade' ?

Posted: **Sun 13 Jun 2021 6:26 pm**

Hi, I'm a former user of Cumulus just getting back into things again with a new station.
My old station packed up a few years ago, and then I moved house and didn't get round to replacing it until now.
It looks like I've missed some big exciting changes round here over the last few years, it's great that Mark has been willing and able to pick the project up and keep it alive. I'm looking forward to uisng it.

Excitement aside, I'm experiencing a similar issue to Cortmalaw, but with an original pi model B.
Using the latest published pi image, written to a 16GB SD using Rasberry Pi's imager, the image boots up and SSH works fine, but the cumulusmx service seems to be dying as it starts.

The error message I see when I run sudo systemctl status cumulusmx is:

Code: Select all

● cumulusmx.service - CumulusMX service
   Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Sun 2021-06-13 18:08:13 BST; 39min ago
     Docs: https://cumuluswiki.org/a/Main_Page
  Process: 292 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
  Process: 383 ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock (code=exited, status=1/FAILURE)
 Main PID: 294 (code=killed, signal=ABRT)

Jun 13 18:07:49 cumulusmx systemd[1]: Starting CumulusMX service...
Jun 13 18:07:51 cumulusmx systemd[1]: Started CumulusMX service.
Jun 13 18:08:13 cumulusmx systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
Jun 13 18:08:13 cumulusmx rm[383]: /bin/rm: cannot remove '/tmp/CumulusMX.exe.lock': No such file or directory
Jun 13 18:08:13 cumulusmx systemd[1]: cumulusmx.service: Control process exited, code=exited, status=1/FAILURE
Jun 13 18:08:13 cumulusmx systemd[1]: cumulusmx.service: Failed with result 'signal'.

If I try to start the service manually, I get the following:

Code: Select all

pi@cumulusmx:~ $ sudo systemctl start cumulusmx
pi@cumulusmx:~ $ systemctl status cumulusmx
● cumulusmx.service - CumulusMX service
   Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2021-06-13 19:02:10 BST; 12s ago
     Docs: https://cumuluswiki.org/a/Main_Page
  Process: 499 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
 Main PID: 500 (mono)
    Tasks: 3 (limit: 877)
   CGroup: /system.slice/cumulusmx.service
           ├─500 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -d:/opt/CumulusMX CumulusMX.exe -service
           └─503 /usr/bin/gdb -batch -x /tmp/mono-gdb-commands.500 -nx

Jun 13 19:02:10 cumulusmx systemd[1]: Starting CumulusMX service...
Jun 13 19:02:10 cumulusmx systemd[1]: Started CumulusMX service.

This looks good, but the admin console is not available, then when I check the status again:

Code: Select all

pi@cumulusmx:~ $ systemctl status cumulusmx
● cumulusmx.service - CumulusMX service
   Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Sun 2021-06-13 19:02:28 BST; 16s ago
     Docs: https://cumuluswiki.org/a/Main_Page
  Process: 499 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
  Process: 509 ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock (code=exited, status=1/FAILURE)
 Main PID: 500 (code=killed, signal=ABRT)

Jun 13 19:02:10 cumulusmx systemd[1]: Starting CumulusMX service...
Jun 13 19:02:10 cumulusmx systemd[1]: Started CumulusMX service.
Jun 13 19:02:28 cumulusmx systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
Jun 13 19:02:28 cumulusmx rm[509]: /bin/rm: cannot remove '/tmp/CumulusMX.exe.lock': No such file or directory
Jun 13 19:02:28 cumulusmx systemd[1]: cumulusmx.service: Control process exited, code=exited, status=1/FAILURE
Jun 13 19:02:28 cumulusmx systemd[1]: cumulusmx.service: Failed with result 'signal'.

I tried the older version linked above, but that never boots for me. I've tried imaging it a couple of times, as well as trying different cards, but it never gets to a point where I can SSH to the pi, and the webserver never starts. I can see by watching my router's DHCP table that the reservation I have attached to the Pi's MAC sits in the waiting state, so I don't think it's even getting as far as initialising the NIC.

Any ideas to get either version up, or is it a case of abandon this older pi and get hold of a model 3 or better?
I've got CumulusMX running on one of my windows machines so I can try things out for now, but that's not a long term solution for me, I definitely want to end up with something linux and self contained like the pi.

Posted: **Wed 16 Jun 2021 4:00 pm**

I swapped my MX from a Windows PC, to a Raspberry Pi computer, a long time ago. I use my RPi for almost everything I used to do on my PC. My unreliable PC is rarely on!

ben-s wrote: ↑Sun 13 Jun 2021 6:26 pm Any ideas to get either version up, or is it a case of abandon this older pi and get hold of a model 3 or better?
I've got CumulusMX running on one of my windows machines so I can try things out for now, but that's not a long term solution for me, I definitely want to end up with something linux and self contained like the pi.

It appears from posts in this forum that people are successfully using MX on various Raspberry Pi models.

In this post it is said that (on 20 April) the Mono-complete included in the image was updated. That Raspberry Pi image was prepared using a model 3, so the latest image might work better on that model. It might be that recent past images (from that date onwards) do not work on older RPi models.

ben-s wrote: ↑Sun 13 Jun 2021 6:26 pm I tried the older version linked above, but that never boots for me. I've tried imaging it a couple of times, as well as trying different cards, but it never gets to a point where I can SSH to the pi, and the webserver never starts. I can see by watching my router's DHCP table that the reservation I have attached to the Pi's MAC sits in the waiting state, so I don't think it's even getting as far as initialising the NIC.

You might want to try an even older image from before that update, see earliest listed at https://cumuluswiki.org/a/Software#Older_releases as that might have a mono.complete that would work better on your existing RPI model. You will need to work through the page history and edits by mcrossley to see which earlier raspberry pi images exist as they were not created for all releases.

You can always upgrade just the MX component after that.

Posted: **Wed 16 Jun 2021 9:29 pm**

Thanks for the advice
So far I have ditched the pi 1 in favour of a new pi 3, which is working reasonably well now, aside from some persistent crashing issues, which I think (hope!) were caused by a dying SD card.
I've stuck a new card in it today, so hopefully that will let the thing stay up for more than a few hours!

I don't want to end up stuck using outdated software, so I'm happier that I can keep the OS and other software up to date with the newer machine.

Ultimately I want to stick Apache on the same machine, to serve a web front end all in one box like I used to do with my old windows cumulus setup.
It's a shame that CMX doesn't have a local save option as well as the FTP upload, but I'm hoping to get round that with one or two ideas I'm mulling over.

Posted: **Thu 17 Jun 2021 1:57 am**

It's a shame that CMX doesn't have a local save option as well as the FTP upload, but I'm hoping to get round that with one or two ideas I'm mulling over.

Good things can happen for those who wait for it

Enjoy,
Paul

Posted: **Thu 17 Jun 2021 11:33 am**

PaulMy wrote: ↑Thu 17 Jun 2021 1:57 am Good things can happen for those who wait for it

Interesting... Perhaps I should hold my horses rather than bodging something then?

Posted: **Thu 17 Jun 2021 12:49 pm**

ben-s wrote: ↑Thu 17 Jun 2021 11:33 am Perhaps I should hold my horses rather than bodging something then

The copy feature was first requested here a year ago.
MX development has been so rapid in the last 12 months that other changes have pushed the copy feature back.

The next release, 3.12.0, as anyone can discover from what the developer has published, should clear a lot of the requests on the to do list, including this.
We cannot know when Mark will finish work on that release, or indeed how much more is left to work out for that release, so you decide whether you are willing to wait.

ben-s wrote: ↑Wed 16 Jun 2021 9:29 pm the pi 1 in favour of a new pi 3, which is working reasonably well now
...
to serve a web front end,

Like you plan to do, my RPi drives a web server too, so I am sure you will be ok.

Posted: **Fri 18 Jun 2021 3:33 pm**

sfws wrote: ↑Thu 17 Jun 2021 12:49 pm Like you plan to do, my RPi drives a web server too, so I am sure you will be ok.

How are you running your webserver?
When I first set the system up with the duff card, I installed Apache and set up FTP so Cumulus could FTP into the Apache folder, which worked but felt hacky.

It seems to be stable with the new card now, so I'm debating whether to implement thesame thing again.

Posted: **Mon 04 Oct 2021 8:17 am**

mcrossley wrote: ↑Thu 03 Jun 2021 12:57 pm There is an older image here: https://cumuluswiki.org/Downloads/rpi-CMX-3.10.5.zip

Having the same issue trying to get MX running on an older pi

I'm having trouble tracking down any older images at all using the methods described - only lots of 404's?

Posted: **Mon 04 Oct 2021 12:03 pm**

Only the last couple of releases are available for download. I don't want to be trying to support old versions.

Posted: **Mon 04 Oct 2021 11:31 pm**

mcrossley wrote: ↑Mon 04 Oct 2021 12:03 pm Only the last couple of releases are available for download. I don't want to be trying to support old versions.

No worries - I was just thinking I would backtrack a bit to see if I could locate a working version/when it stopped etc.

Code: Select all

pi@cumulusmx:~ $ sudo systemctl status cumulusmx
â cumulusmx.service - CumulusMX service
   Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Mon 2021-10-04 19:46:44 AEDT; 14h ago
     Docs: https://cumuluswiki.org/a/Main_Page
  Process: 249 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
  Process: 389 ExecStopPost=/bin/rm /tmp/CumulusMX.exe.lock (code=exited, status=1/FAILURE)
 Main PID: 252 (code=killed, signal=ABRT)

Oct 04 19:46:18 cumulusmx systemd[1]: Starting CumulusMX service...
Oct 04 19:46:21 cumulusmx systemd[1]: Started CumulusMX service.
Oct 04 19:46:44 cumulusmx systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
Oct 04 19:46:44 cumulusmx rm[389]: /bin/rm: cannot remove '/tmp/CumulusMX.exe.lock': No such file or directory
Oct 04 19:46:44 cumulusmx systemd[1]: cumulusmx.service: Control process exited, code=exited, status=1/FAILURE
Oct 04 19:46:44 cumulusmx systemd[1]: cumulusmx.service: Failed with result 'signal'.
pi@cumulusmx:~ $

Code: Select all

pi@cumulusmx:/opt/CumulusMX $ sudo mono CumulusMX.exe

=================================================================
        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:
=================================================================
Could not exec mono-hang-watchdog, expected on path '/etc/../bin/mono-hang-watchdog' (errno 2)
Entering thread summarizer pause from 0x3069679936x
Finished thread summarizer pause from 0x3069679936x.
Failed to create breadcrumb file (null)/crash_hash_0x15b1c4952

Waiting for dumping threads to resume

=================================================================
        External Debugger Dump:
=================================================================
[New LWP 582]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__waitpid (options=0, stat_loc=0xbed26054, pid=584) at ../sysdeps/unix/sysv/linux/waitpid.c:30
30      ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
  Id   Target Id                                 Frame
* 1    Thread 0xb6f79940 (LWP 581) "mono"        __waitpid (options=0, stat_loc=0xbed26054, pid=584) at ../sysdeps/unix/sysv/linux/waitpid.c:30
  2    Thread 0xb5fff400 (LWP 582) "SGen worker" futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/unix/sysv/linux/futex-internal.h:88

Thread 2 (Thread 0xb5fff400 (LWP 582)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x0, cond=0x40d268) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x40d268, mutex=0x0) at pthread_cond_wait.c:655
#3  0x002f495c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb6f79940 (LWP 581)):
#0  __waitpid (options=0, stat_loc=0xbed26054, pid=584) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1  __waitpid (pid=584, stat_loc=0xbed26054, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2  0x0009cbc4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 581) detached]

=================================================================
        Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0xb4513338):0xb4513328  00 00 00 ea fc d7 66 00 00 00 9f e7 10 00 8d e5  ......f.........
0xb4513338  5b f0 7f f5 10 00 9d e5 00 10 80 e5 18 d0 8d e2  [...............
0xb4513348  00 81 bd e8 40 41 2d e9 1c d0 4d e2 00 60 a0 e1  ....@A-...M..`..
0xb4513358  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
pi@cumulusmx:/opt/CumulusMX $

Cumulus Support

Raspberry Pi Image - stops immediately

Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately

Re: Raspberry Pi Image - stops immediately