Linux update crash weewx... again!

[Jacques Desroches]

Hi!

Recently, I've encountered permission error after Bookworm update on rPi.

Ater trying other OS, Ubuntu worked... a few weeks, and now problem occur again.

Service status display :

fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.restx: CWOP: Posting not enabled.
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.restx: WOW: Posting not enabled.
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.restx: AWEKAS: Posting not enabled.
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.engine: 'pyephem' detected, extended almanac data is available
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO __main__: Starting up weewx version 5.2.0
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.manager: Starting backfill of daily summaries
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.manager: Daily summaries up to date
fév 20 17:26:22 New-Meteo weewxd[1334]: INFO weewx.engine: Starting main packet loop.fév 20 17:26:23 New-Meteo weewxd[1334]: ERROR weewx.drivers.acurite: Failed attempt 1 of 10 to get LOOP data: [Errno 110] Operation timed out

fév 20 17:38:29 New-Meteo weewxd[1334]: ERROR weewx.drivers.acurite: Failed attempt 1 of 10 to get LOOP data: [Errno 5] Input/Output Error
fév 20 17:38:59 New-Meteo weewxd[1334]: ERROR weewx.drivers.acurite: Failed attempt 2 of 10 to get LOOP data: [Errno 5] Input/Output Error

When using WeewxD, it display nothing, but with Ctrl-C, it display:

 Traceback (most recent call last):
  File "/usr/share/weewx/weewx/drivers/acurite.py", line 463, in genLoopPackets
    raw1 = station.read_R1()
           ^^^^^^^^^^^^^^^^^
  File "/usr/share/weewx/weewx/drivers/acurite.py", line 652, in read_R1
    return self.read(1, 10)
           ^^^^^^^^^^^^^^^^
  File "/usr/share/weewx/weewx/drivers/acurite.py", line 643, in read
    return self.handle.controlMsg(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/usb/legacy.py", line 207, in controlMsg
    return self.dev.ctrl_transfer(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/usb/core.py", line 1082, in ctrl_transfer
    ret = self._ctx.backend.ctrl_transfer(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 893, in ctrl_transfer
    ret = _check(self.lib.libusb_control_transfer(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 604, in _check
    raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno 5] Input/Output Error

Any suggestions?

Thanks,

Jacques

[Vince Skahan]

Go back to the previously working versions for whatever kernel and usb packages updated, verify it works again, and freeze them from future updates.  You should be able to figure out what changed from your dpkg.log file,

[p q]

Last week, I spent yet another day fighting this and gave up. I decided it was time to abandon my Acurite hardware. I had already replaced everything except the barometer, humidity, and wind with my own. I've bastardized the Acurite driver horribly to do so and I'm in the process of moving everything to the MQTT subscribe driver.

After investigating the USB issues, I concluded it wasn't the library but the kernel change that caused the problem. And, since after the kernel change I was able to still see the USB device but not read from it, I think it might be the Acurite not following the USB spec exactly right. But, who knows. I got tired of chasing it and found another solution.

FWIW, Claude.AI was helpful in trying to debug the issue and providing instructions for rolling back to an earlier version

Good luck.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/bf39e4d6-b3a3-49b4-9410-e050b08ca5f8n%40googlegroups.com.

--

Peter Quinn
(415)794-2264

[Vince Skahan]

Not understanding why you can't just rollback and freeze the kernel revision or even all updates to the computer.  If you're LAN-only with no incoming traffic you likely never really 'need' to do any updates.  But sure shopping elsewhere and not fighting Acurite vs. kernel definitely works.