Welcome to the Cumulus Support forum.

Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025

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

Legacy Cumulus 1 release 1.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

If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080

Unexpected fail

From Cumulus MX version 3 build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since, and has recently released Cumulus MX version 4. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

Post Reply
Nottub
Posts: 227
Joined: Fri 04 Dec 2020 4:35 pm
Weather Station: Davis VP2 (Cabled)
Operating System: RPi 4 (Bookworm)
Contact:

Unexpected fail

Post by Nottub »

Yesterday CMX unexpectedly stopped just before 4pm.

The Diagnostic log just stopped as shown below (zipped diagnostic attached for completeness).

Code: Select all

Write complete
2024-06-22 15:56:53.359 RealtimePHP[164]: Uploading extra web file /home/pi2/Pictures/scene.jpeg to images/webcam.jpg
2024-06-22 15:56:53.360 RealtimePHP[164]: Uploading to images/webcam.jpg
2024-06-22 15:56:53.386 RealtimePHP[164]: Sending via POST
2024-06-22 15:56:53.556 RealtimePHP[164]: Upload to images/webcam.jpg: Response code = 200: OK
2024-06-22 15:56:53.556 RealtimePHP[164]: Upload to images/webcam.jpg: Response text follows:
Unzipping data
Opening binary file images/webcam.jpg for replacement
Writing binary file images/webcam.jpg
Write complete
2024-06-22 15:56:53.557 RealtimePHP[164]: Real time files complete, 3 files uploaded
2024-06-22 15:56:53.557 RealtimePHP[164]: Real time files process end
2024-06-22 15:56:53.557 Realtime[164]: End cycle
2024-06-22 15:56:54.494 LOOP: Data - 20: 4C-4F-4F-14-00-54-03-CA-74-FE-02-2C-E2-02-01-02-0C-01-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-2B-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-00-00-C9-00-AA-08-00-00-00-00-00-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2A-03-06-2D-B7-01-56-08-0A-0D-12-51
2024-06-22 15:56:54.495 LOOP: 20 - Data packet is good
2024-06-22 15:56:54.495 DoWind: latest=1.0, speed=2.0 - Current: gust=8.5, speed=2.5
2024-06-22 15:56:54.496 DoWind: New: gust=8.5, speed=2.5, latest:1.2
And that was the very last line.

A shutdown of CMX and reboot of RPi, and all was well.

BTW trimmed down the Logging options to just 'Debug Logging'.

Just puzzled rather than concerned at this stage.

Martyn
You do not have the required permissions to view the files attached to this post.
Image
Nottub
Posts: 227
Joined: Fri 04 Dec 2020 4:35 pm
Weather Station: Davis VP2 (Cabled)
Operating System: RPi 4 (Bookworm)
Contact:

Re: Unexpected fail

Post by Nottub »

After replacing my USB cable there is no drop out when I move the new cable :D . So the connection bit is sorted.

However CMX unexpectedly stopped again today with no particular signs of any issues in the Diagnostic file.
The entries just stopped at 15:04:41.879.

Is there a reason why the DoWind: is read so frequently?

Code: Select all

2024-07-11 15:04:29.879 LOOP: 35 - Data packet is good
2024-07-11 15:04:29.880 DoWind: latest=2.0, speed=2.0 - Current: gust=4.9, speed=2.3
2024-07-11 15:04:29.881 DoWind: New: gust=4.9, speed=2.3, latest:2.4
2024-07-11 15:04:31.880 LOOP: 36 - Data packet is good
2024-07-11 15:04:31.880 DoWind: latest=3.0, speed=2.0 - Current: gust=4.9, speed=2.3
2024-07-11 15:04:31.881 DoWind: New: gust=4.9, speed=2.3, latest:3.7
2024-07-11 15:04:33.880 LOOP: 37 - Data packet is good
2024-07-11 15:04:33.880 DoWind: latest=2.0, speed=2.0 - Current: gust=4.9, speed=2.3
2024-07-11 15:04:33.881 DoWind: New: gust=4.9, speed=2.3, latest:2.4
2024-07-11 15:04:35.877 LOOP: 38 - Data packet is good
2024-07-11 15:04:35.878 DoWind: latest=2.0, speed=2.0 - Current: gust=4.9, speed=2.3
2024-07-11 15:04:35.878 DoWind: New: gust=4.9, speed=2.3, latest:2.4
2024-07-11 15:04:37.875 LOOP: 39 - Data packet is good
2024-07-11 15:04:37.876 DoWind: latest=1.0, speed=2.0 - Current: gust=4.9, speed=2.3
2024-07-11 15:04:37.876 DoWind: New: gust=4.9, speed=2.3, latest:1.2
2024-07-11 15:04:39.884 LOOP: 40 - Data packet is good
2024-07-11 15:04:39.884 DoWind: latest=1.0, speed=2.0 - Current: gust=4.9, speed=2.3
2024-07-11 15:04:39.885 DoWind: New: gust=4.9, speed=2.3, latest:1.2
2024-07-11 15:04:41.878 LOOP: 41 - Data packet is good
2024-07-11 15:04:41.879 DoWind: latest=2.0, speed=2.0 - Current: gust=4.9, speed=2.3
2024-07-11 15:04:41.879 DoWind: New: gust=4.9, speed=2.3, latest:2.4
Any ideas gratefully received.

Thanks

Martyn
Image
broadstairs
Posts: 1184
Joined: Thu 14 Aug 2008 7:17 am
Weather Station: Ecowitt GW2000/GW3000
Operating System: Linux openSUSE LEAP
Location: Broadstairs, Kent, UK
Contact:

Re: Unexpected fail

Post by broadstairs »

From memory when I had a VP1 the wind updates were about every 2 seconds!

As for why it stopped I can only guess perhaps memory or disk space exceeded?

Stuart
Currently running CMX V4.4.2 4085 on Linux openSUSE Leap
Nottub
Posts: 227
Joined: Fri 04 Dec 2020 4:35 pm
Weather Station: Davis VP2 (Cabled)
Operating System: RPi 4 (Bookworm)
Contact:

Re: Unexpected fail

Post by Nottub »

Looking through recent posts there was a suggestion to check the RPi Journal. So i ran:

Code: Select all

sudo journalctl --since="2024-07-11 15:00:00"
This may be of help:(note the 15:04:48 entries (appears in RED in the Journal).

Code: Select all

Jul 11 15:02:01 blackberrypi CRON[682518]: pam_unix(cron:session): session opened for user pi2(uid=1000) by (uid=0)
Jul 11 15:02:01 blackberrypi CRON[682519]: (pi2) CMD (/home/pi2/snapshot)
Jul 11 15:02:04 blackberrypi CRON[682518]: (CRON) info (No MTA installed, discarding output)
Jul 11 15:02:04 blackberrypi CRON[682518]: pam_unix(cron:session): session closed for user pi2
Jul 11 15:04:01 blackberrypi CRON[682701]: pam_unix(cron:session): session opened for user pi2(uid=1000) by (uid=0)
Jul 11 15:04:01 blackberrypi CRON[682702]: (pi2) CMD (/home/pi2/snapshot)
Jul 11 15:04:04 blackberrypi CRON[682701]: (CRON) info (No MTA installed, discarding output)
Jul 11 15:04:04 blackberrypi CRON[682701]: pam_unix(cron:session): session closed for user pi2
Jul 11 15:04:48 blackberrypi kernel: xhci_hcd 0000:01:00.0: ERROR Transfer event for unknown stream ring slot 2 ep 7
Jul 11 15:04:48 blackberrypi kernel: xhci_hcd 0000:01:00.0: @000000040e002050 00000000 00000000 05000000 02088000
Jul 11 15:05:19 blackberrypi kernel: sd 0:0:0:0: [sda] tag#22 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT 
Jul 11 15:05:19 blackberrypi kernel: sd 0:0:0:0: [sda] tag#22 CDB: opcode=0x2a 2a 00 01 bf 46 78 00 00 10 00
Jul 11 15:05:19 blackberrypi kernel: sd 0:0:0:0: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT 
Jul 11 15:05:19 blackberrypi kernel: sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 00 00 16 28 00 00 08 00
Thanks

Martyn
Image
SamiS
Posts: 510
Joined: Sun 27 Feb 2011 5:13 pm
Weather Station: Ecowitt HP2551 & GW1100
Operating System: Raspberry Pi OS
Location: Kangasala, Finland

Re: Unexpected fail

Post by SamiS »

I’m not too familiar with linux kernel error messages, but to me it seems that your sda disk experiences some problems. If you run from sd card, this might be a card issue, but googling also found references to external usb drive problems.
User avatar
rogerthn
Posts: 547
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: Unexpected fail

Post by rogerthn »

Nottub wrote: Thu 11 Jul 2024 4:02 pm ....
Any ideas gratefully received.

Thanks

Martyn
I've had some issues with power supplies, have you checked voltage level?
Image
broadstairs
Posts: 1184
Joined: Thu 14 Aug 2008 7:17 am
Weather Station: Ecowitt GW2000/GW3000
Operating System: Linux openSUSE LEAP
Location: Broadstairs, Kent, UK
Contact:

Re: Unexpected fail

Post by broadstairs »

Those two xhci_hcd messages do indicate to me a disk issue, but might be a PSU issue especially if its an external disk.

Stuart
Currently running CMX V4.4.2 4085 on Linux openSUSE Leap
BigOkie
Posts: 283
Joined: Tue 28 May 2013 1:06 am
Weather Station: Davis VP2 Plus
Operating System: Raspian Bookworm (RPi 3b)
Location: Tulsa, OK

Re: Unexpected fail

Post by BigOkie »

broadstairs wrote: Thu 11 Jul 2024 4:17 pm From memory when I had a VP1 the wind updates were about every 2 seconds!

As for why it stopped I can only guess perhaps memory or disk space exceeded?

Stuart
All the VPs I believe have a small interval on wind (on the Vp2, depending on what the ISS freq is set to, it's between 2.5 and 3.5 seconds.
Post Reply