Installing CMX v4

[HansR]

When using CMX4 with dotnet why do you need to start with

Code: Select all

sudo dotnet CumulusMX.[i]dll[/i]

rather than

Code: Select all

sudo mono CumulusMX.[i]exe[/i]

?

Because dotnet is a totally different environment than mono.
They are not interchangeable.

I have got CumulusMX running using as a service using

Code: Select all

systemctl enable cumulusmx 

but it only runs for a few seconds and then stops. What am I doing wrong?

Please post your logfile with debug on

[rogerthn]

...
I have got CumulusMX running using as a service using

Code: Select all

systemctl enable cumulusmx 

but it only runs for a few seconds and then stops. What am I doing wrong?

RogerH

Enable is to enable the service.
Have you tried

Code: Select all

systemctl start cumulusmx

[SamiS]

Enable is to enable the service.
Have you tried

Code: Select all

systemctl start cumulusmx

Good catch. To clarify for everyone, enable/disable determines that will the service start automatically on next reboot or not. Start/stop is used to start or stop the service immediately.

[RogerH]

Yes, I am starting it, both with the command and after a reboot. It runs for a couple of seconds and stops.
-------------------------------------------------------------------------------------------------------------------------------

After a reboot
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-04-15 20:29:39 BST; 5min ago
Docs: https://cumuluswiki.org/a/Main_Page
https://cumulus.hosiene.co.uk/
Process: 485 ExecStart=/opt/dotnet/dotnet CumulusMX.dll -service (code=exited, status=1/FAILURE)
Main PID: 485 (code=exited, status=1/FAILURE)
CPU: 3.819s

Apr 15 20:29:30 rpi3zw2 systemd[1]: Started CumulusMX service.
Apr 15 20:29:39 rpi3zw2 dotnet[485]: Cumulus stopped
Apr 15 20:29:39 rpi3zw2 systemd[1]: cumulusmx.service: Main process exited, code=exited, status=1/FAILURE
Apr 15 20:29:39 rpi3zw2 systemd[1]: cumulusmx.service: Failed with result 'exit-code'.
Apr 15 20:29:39 rpi3zw2 systemd[1]: cumulusmx.service: Consumed 3.819s CPU time.
~

using sudo systemctl start cumulusmx
rpi3zw2@rpi3zw2:~ $ sudo systemctl start cumulusmx
rpi3zw2@rpi3zw2:~ $ systemctl status cumulusmx
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-04-15 20:40:19 BST; 8s ago
Docs: https://cumuluswiki.org/a/Main_Page
https://cumulus.hosiene.co.uk/
Process: 2457 ExecStart=/opt/dotnet/dotnet CumulusMX.dll -service (code=exited, status=1/FAILURE)
Main PID: 2457 (code=exited, status=1/FAILURE)
CPU: 3.299s

Apr 15 20:40:12 rpi3zw2 systemd[1]: Started CumulusMX service.
Apr 15 20:40:19 rpi3zw2 dotnet[2457]: Cumulus stopped
Apr 15 20:40:19 rpi3zw2 systemd[1]: cumulusmx.service: Main process exited, code=exited, status=1/FAILURE
Apr 15 20:40:19 rpi3zw2 systemd[1]: cumulusmx.service: Failed with result 'exit-code'.
Apr 15 20:40:19 rpi3zw2 systemd[1]: cumulusmx.service: Consumed 3.299s CPU time.

[HansR]

Repeat: please post the logfile

[RogerH]

to Hans

RogerH wrote: ↑Mon 15 Apr 2024 4:41 pm
I have got CumulusMX running using as a service using

Code: Select all

systemctl enable cumulusmx

but it only runs for a few seconds and then stops. What am I doing wrong?

Please post your logfile with debug on

How do I do that?

Code: Select all

sudo dotnet CumulusMX.dll -install -user <username> -debug

?
Where or how do I find the output?

RogerH

[HansR]

You will find the logfiles in the directory MXdiags under the CumulusMX directory.
The filenames have the format <year><month><day>-<hhmmss>.txt e.g. 20240415-090654.txt.
Select the most recent logfile and post it here.

I don't know which version you try to run by assuming it is the last release v4 debug should already be on.
If not we'll see how to progress.

[RogerH]

Two logfiles attached.
The earlier log file was where Cumulus was run as a service, and failed.

The later log file was where Cumulus was run directly.

Is the problem with permissions? I was asked to enter my password when I ran the self-installer,

Code: Select all

sudo dotnet CumulusMX.dll -install -user <username>

[HansR]

@RogerH:

CMX can't create it's backup so most likely the ownership of the CMX directory structure is different from the owner under which you run CMX.

Questions:

1. under which owner do you run CMX (or did you install as a service)
2. who is the owner of the CMX directory structure (main and subdirectories please in case they differ in ownership)

Note: the owners must be the same and the advise is NOT to use root.

[HansR]

@RogerH:
NOTE: the required password when installing the service with sudo is something of sudo which wants to check you have the right to use sudo. To change that - i.e. have sudo always permitted with your standard user - requires configuring sudo. That is something you may do on some lazy sunday afternoon, it is not related to running CMX.

[RogerH]

I don't know who or what had ownership of the various parts. How do I find out and change them to work?

What hierarchy of permissions does Rpi have.

RogerH

[HansR]

I don't know who or what had ownership of the various parts. How do I find out and change them to work?

What hierarchy of permissions does Rpi have.

This is going to be somewhat difficult than. I can't give a course on Unix / Linux - File Permission / Access Modes but there are good courses online (like the one linked). I suggest you do the elementary basics yourself and then when you have questions on CumuluxMX you come back.

Using Unix/Linux without any knowledge about that OS is not advised.

[RogerH]

To change that - i.e. have sudo always permitted with your standard user - requires configuring sudo. That is something you may do on some lazy sunday afternoon, it is not related to running CMX.

It may be the reason for the failure I am seeing in CMX. The file

Comparison of MXdiags log files, etc.docx

shows a comparison of a failing start (via systemd) and working properly (using sudo dotnet CumulusMX.dll).

I looked at the <cumulusmx.service> file. In version 3283 the user and group were set to <root>. In version 4019 they are set to my <user>, but the permissions for the file itself are <root>. I cannot edit the file to test the hypothesis that this is the problem. However if I had configured my account so that sudo was permitted for a standard user it would probably work, but still NOT for a normal standard user.
My <cumulusmx.service> file.

Code: Select all

[Unit]
Description=CumulusMX service
Documentation=https://cumuluswiki.org/a/Main_Page https://cumulus.hosiene.co.uk/
Wants=network-online.target time-sync.target
After=network-online.target time-sync.target

[Service]
User=rpi3zw2
Group=rpi3zw2
WorkingDirectory=/home/rpi3zw2/CumulusMX
ExecStart="/opt/dotnet/dotnet" CumulusMX.dll -service
Type=simple

[Install]
WantedBy=multi-user.target

RogerH

[HansR]

To change that - i.e. have sudo always permitted with your standard user - requires configuring sudo. That is something you may do on some lazy sunday afternoon, it is not related to running CMX.

It may be the reason for the failure I am seeing in CMX. The file

Comparison of MXdiags log files, etc.docx

shows a comparison of a failing start (via systemd) and working properly (using sudo dotnet CumulusMX.dll).

I looked at the <cumulusmx.service> file. In version 3283 the user and group were set to <root>. In version 4019 they are set to my <user>, but the permissions for the file itself are <root>. I cannot edit the file to test the hypothesis that this is the problem. However if I had configured my account so that sudo was permitted for a standard user it would probably work, but still NOT for a normal standard user.
[...]

I think you have to modify the group and ownsership of the CMX service process set to rpi3zw2 (that's good: it is not root). But this means you have to modify the user and group of the files in the CMX directory structure.

To do so, use the chgrp and chown commands:

1. cd /home/rpi3zw2/CumulusMX
2. chgrp -R rpi3zw2 *
3. chown -R rpi3zw2 *

That should probably do the trick.

[ConligWX]

When using CMX4 with dotnet why do you need to start with

Code: Select all

sudo dotnet CumulusMX.[i]dll[/i]

rather than

Code: Select all

sudo mono CumulusMX.[i]exe[/i]

?
RogerH

Because cmx V4 uses donet and not mono. Did you read the change log?

A new version of Cumulus MX is now in beta testing. Version 4 moves away from the old Microsoft .Net Framework and on to the new fully supported .NET 8.0 platform

viewtopic.php?p=179828#p179828