Page 1 of 1
Unexpected fail
Posted: Sun 23 Jun 2024 8:25 am
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
Re: Unexpected fail
Posted: Thu 11 Jul 2024 4:02 pm
by Nottub
After replacing my USB cable there is no drop out when I move the new cable
. 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
Re: Unexpected fail
Posted: Thu 11 Jul 2024 4:17 pm
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
Re: Unexpected fail
Posted: Thu 11 Jul 2024 4:21 pm
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
Re: Unexpected fail
Posted: Thu 11 Jul 2024 5:25 pm
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.
Re: Unexpected fail
Posted: Thu 11 Jul 2024 5:42 pm
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?
Re: Unexpected fail
Posted: Thu 11 Jul 2024 9:21 pm
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
Re: Unexpected fail
Posted: Fri 12 Jul 2024 2:12 pm
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.