Problems installing on Pi B+

[jonmiles]

Hi all,

I am having problems setting up cumulus on a Raspberry Pi B+

I appreciate its an old pi, but its what i have.

I have created the image as per the instructions on here, and it boots fine.

i have uninstalled and reinstalled mono but still have the following error when i start the service:

Code: Select all

● cumulusmx.service - CumulusMX service
     Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Fri 2023-01-20 20:22:36 GMT; 47min ago
       Docs: https://cumuluswiki.org/a/Main_Page
    Process: 726 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
    Process: 738 ExecStopPost=/bin/rm -f /tmp/CumulusMX.exe.lock (code=exited, status=0/SUCCESS)
   Main PID: 727 (code=killed, signal=ABRT)
        CPU: 13.798s

Jan 20 20:22:20 raspberrypi systemd[1]: Starting CumulusMX service...
Jan 20 20:22:20 raspberrypi systemd[1]: Started CumulusMX service.
Jan 20 20:22:36 raspberrypi systemd[1]: cumulusmx.service: Main process exited, code=killed, status=6/ABRT
Jan 20 20:22:36 raspberrypi systemd[1]: cumulusmx.service: Failed with result 'signal'.
Jan 20 20:22:36 raspberrypi systemd[1]: cumulusmx.service: Consumed 13.798s CPU time.

/opt/CumulusMX/MXdiags folder is empty and my setup is as follows:

Code: Select all

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

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

[Install]
WantedBy=multi-user. Target

I have searched the forums but to no avail so would appreciate any help please.

[mcrossley]

Did you uninstall/reinstall "mono-complete"?

Do you have a file like "mono_crash.0.0.json" in the Cumulus folder?

[jonmiles]

thank you for your reply.

yes uninstalled and installed mono

also yes to the file

Code: Select all

{
  "protocol_version" : "0.0.6",
  "configuration" : {
    "version" : "(6.12.0.182) (tarball)",
    "tlc" : "__thread",
    "sigsgev" : "normal",
    "notifications" : "epoll",
    "architecture" : "armel,vfp+hard",
    "disabled_features" : "none",
    "smallconfig" : "disabled",
    "bigarrays" : "disabled",
    "softdebug" : "enabled",
    "interpreter" : "enabled",
    "llvm_support" : "610",
    "suspend" : "preemptive"
  },
  "memory" : {
    "minor_gc_time" : "0",
    "major_gc_time" : "0",
    "minor_gc_count" : "0",
    "major_gc_count" : "0",
    "major_gc_time_concurrent" : "0"
 },
  "threads" : [
 {
    "is_managed" : true,
    "offset_free_hash" : "0x15b1c48ca",
    "offset_rich_hash" : "0x15b1c4952",
    "crashed" : true,
    "native_thread_id" : "0xffffffffb6f60ac0",
    "thread_info_addr" : "0x15864e0",
    "thread_name" : "mono",
    "ctx" : {
      "IP" : "0xb4513360",
      "SP" : "0xbec75bd8",
      "BP" : "0xbec75bf8"
  },
    "managed_frames" : [
  {
      "is_managed" : "true",
      "guid" : "DE882A77-E7C1-4F8B-A5D2-98093DDE82B2",
      "token" : "0x00000",
      "native_offset" : "0x0",
      "filename" : "mscorlib.dll",
      "sizeofimage" : "0x472000",
      "timestamp" : "0xbc6b67d7",
      "il_offset" : "0x00027"
   }
,
  {
      "is_managed" : "false",
      "native_address" : "unregistered"
   }
,
  {
      "is_managed" : "true",
      "guid" : "DE882A77-E7C1-4F8B-A5D2-98093DDE82B2",
      "token" : "0x00000",
      "native_offset" : "0x0",
      "filename" : "mscorlib.dll",
      "sizeofimage" : "0x472000",
      "timestamp" : "0xbc6b67d7",
      "il_offset" : "0x00061"
   }

  ]
 }
 ]
}

[mcrossley]

It is definitely mono that is crashing then. The only times I have seen this happen is when it has not been compiled for the older processor types on the original pi zeros. But a complete reinstall on mono forces it to recompile portions on the install.

Once you have removed mono, try listing all packages starting with "mono-*" and see if there are any left before you reinstall.

During the install you should see some components compiling.

[HansR]

This one already helped me several time: https://www.howtoforge.com/how-to-insta ... debian-11/
Note that you need 6.12.0.182 to have CMX send email. The above procedure does do that.

[SamiS]

This one already helped me several time: https://www.howtoforge.com/how-to-insta ... debian-11/
Note that you need 6.12.0.182 to have CMX send email. The above procedure does do that.

One thing bothers me on this guide. When uninstalling, it tells you to remove mono-runtime, but on installation it specifies mono-complete (that is required with cmx). I have not tested, but this makes me suspect, that the removal could leave something behind.

[HansR]

One thing bothers me on this guide. When uninstalling, it tells you to remove mono-runtime, but on installation it specifies mono-complete (that is required with cmx). I have not tested, but this makes me suspect, that the removal could leave something behind.

I noticed that too, can't change the article, but while following the procedure so far it worked great and had no problems with fault generating residues. You might try remove mono-complete. And btw, I think CMX only requires the runtime which mono-complete does supply. But maybe Mark can comment on this.

[SamiS]

I’m about 70% sure that in the past I tried installing only the runtime and CMX failed to run. But anyway not sure about the current status, that was probably well over a year ago, maybe from mono 4.x or 5.x.

[mcrossley]

It needs mono-complete, there are some components missing from the runtime that CMX uses. Not much of a runtime really is it!

[jonmiles]

thank you all for your input.

I have tried running through the guide posted.

i now have a different error for the service - a change from

Main PID: 727 (code=killed, signal=ABRT)
to
Main PID: 437 (code=killed, signal=TRAP)

Code: Select all

● cumulusmx.service - CumulusMX service
     Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Sat 2023-01-21 21:12:02 GMT; 12min ago
       Docs: https://cumuluswiki.org/a/Main_Page
    Process: 435 ExecStart=/usr/bin/mono-service -d:/opt/CumulusMX CumulusMX.exe -service (code=exited, status=0/SUCCESS)
    Process: 440 ExecStopPost=/bin/rm -f /tmp/CumulusMX.exe.lock (code=exited, status=0/SUCCESS)
   Main PID: 437 (code=killed, signal=TRAP)
        CPU: 89ms

Jan 21 21:12:02 raspberrypi systemd[1]: Starting CumulusMX service...
Jan 21 21:12:02 raspberrypi systemd[1]: Started CumulusMX service.
Jan 21 21:12:02 raspberrypi systemd[1]: cumulusmx.service: Main process exited, code=killed, status=5/TRAP
Jan 21 21:12:02 raspberrypi systemd[1]: cumulusmx.service: Failed with result 'signal'.

[HansR]

Could you run CMX from the commandline and post the resulting output on the console (just cut and paste here enclosed by code tags)
Could you also attach the corresponding logfile. If you can switch on debug in the Cumulus.ini it would be appreciated. I don't assume CMX will be active long enough to switch on debug through the interface.

[jonmiles]

Thank you

I only get one line when running it from the command line:

Code: Select all

Trace/breakpoint trap

there is no Cumulus.ini file in the cumulusmx folder.

it has not run correctly once yet so not sure if that is created on first run

[jonmiles]

I have re-imaged the installation, removed and re-installled mono.

if I run

Code: Select all

cd /opt/CumulusMX
sudo mono CumulusMX.exe

i get the following output

Code: Select all

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

Waiting for dumping threads to resume

=================================================================
        External Debugger Dump:
=================================================================
[New LWP 527]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
0xb6bb4034 in __GI___wait4 (pid=529, stat_loc=0xbece7034, 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 0xb6f41ac0 (LWP 526) "mono"        0xb6bb4034 in __GI___wait4 (pid=529, stat_loc=0xbece7034, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
  2    Thread 0xb5fff400 (LWP 527) "SGen worker" futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/nptl/futex-internal.h:186

Thread 2 (Thread 0xb5fff400 (LWP 527) "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 0xb6f41ac0 (LWP 526) "mono"):
#0  0xb6bb4034 in __GI___wait4 (pid=529, stat_loc=0xbece7034, 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 526) 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

[HansR]

@jonmiles:

During the install you should see some components compiling.

You never confirmed you see some components compiling. Do they compile?

If you are really using an RPi 1 (i.s.o. e.g. an RPi 3B+) and you can't get CMX to run then your exercise may lead to the conclusion that CMX cannot run on that machine (or it may be broken?) and may need a newer one (e.g. an RPi 3B+) or simply do not use the image to install and try to install from scratch (OS + updates + mono + CMX).

As long as mono crashes you will not have a proper installation.
Redoing it indefinitely will not help.
A problem is that nobody else has this issue and the data to go on is minimal.

So if it appears impossible to get it all to run on your Pi, impossible to recompile mono, then maybe the Pi is impossible to use?

[jonmiles]

@jonmiles:

During the install you should see some components compiling.

You never confirmed you see some components compiling. Do they compile?

apologies - i did miss that.

tbh i dont know - all i see if i connect a monitor is what looks like the normal boot up information for the pi, what should i see?