Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4017) - 17 March 2024

Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

System info

Discussion of the Cumulusutils tool and website generator.

Moderator: HansR

sutne
Posts: 372
Joined: Sun 14 Oct 2012 4:23 pm
Weather Station: HP2553 (WS80) and HP2564 (WS90)
Operating System: Raspbian Bullseye and Bookworm
Location: Rjoanddalen and Kronstad, Norway
Contact:

System info

Post by sutne »

Code: Select all

 Linux/Unix

System uptime: 4 weeks, 3 hours, 58 minutes

System/Processor: Unknown (exception) - Thread was being aborted.
Please install lshw (apt-get install lshw)
I have lshw installed. This used to work.

Is this because I am starting CumulusMX as a service?


http://www.rjoandveret.no/utils/
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: System info

Post by HansR »

sutne wrote: Fri 04 Sep 2020 5:57 pm Is this because I am starting CumulusMX as a service?
Definitely not. I am running CMX as a service and it works.

Could you answer the following:
  1. The error you see is a direct return from a system call trying to run "lshw -quiet -class system" in a try/catch block.
    If you give that command from the commandline does it work?
  2. If not, please reinstall lshw and try again (from the commandline)
  3. Did you update your system recently?
  4. Could you check in the CMX directory if there is a file named similar to mono_crash.0.0.json?
  5. Which linux/Mono versions are running?
  6. I see you system is running already 4 weeks, 3 hours, 58 minutes. That is not a record, but it is quite long. I don't think it should be the cause, but I would try a reboot.
    When you did that, did it help?
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
sutne
Posts: 372
Joined: Sun 14 Oct 2012 4:23 pm
Weather Station: HP2553 (WS80) and HP2564 (WS90)
Operating System: Raspbian Bullseye and Bookworm
Location: Rjoanddalen and Kronstad, Norway
Contact:

Re: System info

Post by sutne »

1.

Code: Select all

 $ sudo lshw -quiet -class system
raspberrypi
    description: ARMv7 Processor rev 4 (v7l)
    product: Raspberry Pi 3 Model B Rev 1.2
    serial: 000000003159ee13
    width: 32 bits
    capabilities: smp
pi@raspberrypi:~ $ 
2. See above
3. Not recently, probably 4 weeks ago
4. Cannot find any mono crash file
5.

Code: Select all

 $ uname -r
5.4.51-v7+
$ mono -V
Mono JIT compiler version 5.18.0.240 (Debian 5.18.0.240+dfsg-3 Sat Apr 20 05:16:08 UTC 2019)
6. I rather not want to do a reboot when I am not there. Probably next week-end.
4 weeks it not much. Sometimes it has been running for several month.
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: System info

Post by HansR »

I see you run sudo to execute lshw.
How do you execute cutils?

I see you did update linux but mono is still 5.18 I don't think that matters so I think that is all ok.

To be honest I don't have an explanation and I prefer to wait now until the reboot if that is OK wih you.
Maybe some linux guru around here has some great ideas to try
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: System info

Post by HansR »

Btw i checked your site and i see it did run last night to completion with result in systeminfo.
I don't know what you did but it now works...

I do see another issue btw and that is the nr of days running for CumulusMX: -49 days.
Surpising that you have that same number as I get when I leave my system running for more than three weeks.

I thought it had to do with an instability in linux but I am beginning to assume it is an issue of CMX. I had the same number both using my method before using the API as with the API. Xo aftef roughly 20+ days CMX comes back with -49. I'll ask @mcrossley and come back on fhis.

This btw is the reason why i have an automated reboot with cmx restart every 15 days.
I could do without and would love to run the RPi really 24/7 with only restart on updates.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
sutne
Posts: 372
Joined: Sun 14 Oct 2012 4:23 pm
Weather Station: HP2553 (WS80) and HP2564 (WS90)
Operating System: Raspbian Bullseye and Bookworm
Location: Rjoanddalen and Kronstad, Norway
Contact:

Re: System info

Post by sutne »

I have done nothing to the system except executing the lshw command and checking versions.
Each hour I run ‘sysinfo’, after midnight I run ‘Thrifty website’.
Can that be a difference?

When I upgraded to Raspian Buster I did a complete new installation and then added mono.
By default the system gave me version 5.18 of mono. I saw no reason to change that to a newer version.
Let the system decide what is the best version.

I start CumulusUtils as External Programs from CumulusMX. I know this is deprecated, but it has been working for me.
I will soon change things. Start CumulusMX from systemd. And then I will change startup of CumulusUtils to a cronjob.

I do not like the philosophy of running regular reboots. If there are problems one should find it and fix it.
Regular reboots is just clearing symptoms.
But can of course be used as temporarly workarounds.

My experience with Rasberry is that it can run «forever».
User avatar
rogerthn
Posts: 489
Joined: Thu 11 Apr 2013 6:31 pm
Weather Station: Ecowitt GW1000/GW1003
Operating System: Raspberry Pi OS bullseye aarch64
Location: Trollhättan Sweden
Contact:

Re: System info

Post by rogerthn »

sutne wrote: Sat 05 Sep 2020 6:20 am ...
I start CumulusUtils as External Programs from CumulusMX. I know this is deprecated, but it has been working for me.
I will soon change things. Start CumulusMX from systemd. And then I will change startup of CumulusUtils to a cronjob.
...
I do run a script as Daily program, see viewtopic.php?p=145390#p145390 for details
System Info is updated from crontab

Code: Select all

9-59/10 * * * * cd /home/pi/CumulusMX && ./cumulusutils.exe SysInfo >> /tmp/SysInfo.log 2>&1
sutne wrote: Sat 05 Sep 2020 6:20 am My experience with Rasberry is that it can run «forever».
+1
Image
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: System info

Post by HansR »

sutne wrote: Sat 05 Sep 2020 6:20 am I have done nothing to the system except executing the lshw command and checking versions.
Each hour I run ‘sysinfo’, after midnight I run ‘Thrifty website’.
Can that be a difference?
No, thrifty is not applied to 'sysinfo'.
Anyway, unexplained as it it may be... it is working again :D
sutne wrote: Sat 05 Sep 2020 6:20 am When I upgraded to Raspian Buster I did a complete new installation and then added mono.
By default the system gave me version 5.18 of mono. I saw no reason to change that to a newer version.
Let the system decide what is the best version.
No problem
sutne wrote: Sat 05 Sep 2020 6:20 am I start CumulusUtils as External Programs from CumulusMX. I know this is deprecated, but it has been working for me.
I will soon change things. Start CumulusMX from systemd. And then I will change startup of CumulusUtils to a cronjob.
That's great, thats what I am using and I think it is the method to go for on the RPi 8-)
Systemd gives easy start/stop possibilities from any script and whenever.
sutne wrote: Sat 05 Sep 2020 6:20 am I do not like the philosophy of running regular reboots. If there are problems one should find it and fix it.
Regular reboots is just clearing symptoms.
But can of course be used as temporarly workarounds.

My experience with Rasberry is that it can run «forever».
Neither do I, and I agree it should not be done. But it is my workaround for the CumulusMX uptime error which comes after 3 weeks or so.
I may come back on this one if I know where the uptime error comes from.

Apart from that... the RPi may be able to run forever, but maybe applications are not :|
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
rogerthn
Posts: 489
Joined: Thu 11 Apr 2013 6:31 pm
Weather Station: Ecowitt GW1000/GW1003
Operating System: Raspberry Pi OS bullseye aarch64
Location: Trollhättan Sweden
Contact:

Re: System info

Post by rogerthn »

HansR wrote: Sat 05 Sep 2020 6:58 am Apart from that... the RPi may be able to run forever, but maybe applications are not :|
With systemd a restart of CumulusMX from crontab is very doable ;)
Image
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: System info

Post by HansR »

@rogerthn:
Yes it is, but a restart of CMX most likely won't fix this issue, you may need a system restart.
And @sutne until now does have complete systemd use if I understand it well and is not present at the RPi so he is reluctant to reboot.

Anyway, there are additional issues which I received off line with this and they seem to revolve around the running of the system longer than 3 weeks (giving erroneous info to the uptime info for CMX and no info for other queries to the API.

So it is apparently running some times per day (when a full run is made) but when used only with a call to sysinfo it starts failing.
Weird.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
rogerthn
Posts: 489
Joined: Thu 11 Apr 2013 6:31 pm
Weather Station: Ecowitt GW1000/GW1003
Operating System: Raspberry Pi OS bullseye aarch64
Location: Trollhättan Sweden
Contact:

Re: System info

Post by rogerthn »

HansR wrote: Sat 05 Sep 2020 7:24 am @rogerthn:
Yes it is, but a restart of CMX most likely won't fix this issue, you may need a system restart.
And @sutne until now does have complete systemd use if I understand it well and is not present at the RPi so he is reluctant to reboot.

Anyway, there are additional issues which I received off line with this and they seem to revolve around the running of the system longer than 3 weeks (giving erroneous info to the uptime info for CMX and no info for other queries to the API.

So it is apparently running some times per day (when a full run is made) but when used only with a call to sysinfo it starts failing.
Weird.
The issue seems to be resolved?
Image
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: System info

Post by HansR »

Yes it seemed, but it isn't :(
The info on site is from midnight and the hourly runs to update sysinfo fail. I received info by PM.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
rogerthn
Posts: 489
Joined: Thu 11 Apr 2013 6:31 pm
Weather Station: Ecowitt GW1000/GW1003
Operating System: Raspberry Pi OS bullseye aarch64
Location: Trollhättan Sweden
Contact:

Re: System info

Post by rogerthn »

HansR wrote: Sat 05 Sep 2020 7:49 am Yes it seemed, but it isn't :(
The info on site is from midnight and the hourly runs to update sysinfo fail. I received info by PM.
OK :(
Image
sutne
Posts: 372
Joined: Sun 14 Oct 2012 4:23 pm
Weather Station: HP2553 (WS80) and HP2564 (WS90)
Operating System: Raspbian Bullseye and Bookworm
Location: Rjoanddalen and Kronstad, Norway
Contact:

Re: System info

Post by sutne »

With systemd a restart of CumulusMX from crontab is very doable
I can easy do a reboot. I have full remote control of my RPi via VNC, but I am reluctant to do it unless I am present at the site or soon going up there.

Before my RPi which probably will come back after every reboot, I had an old windows laptop running Cumulus 1. This laptop was a struggle to connect to the wi-fi, so after power failure etc it never came back up by itself.
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: System info

Post by HansR »

OK. I just informed Mark in a separate post.
Wait with a reboot until he had a chance to say something.
As the reboot most likely (I think) solves the problem for now, it may be deeper. So as it is only sysinfo now, I suggest to wait a bit.
If you detect more anomalies, I would advice to reboot before the system becomes unusable (which happened to me some times).
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
Post Reply