Weewx errno 32 pipe error

[Sean Jahnig]

Hi,

I have a RPi 4 with Acurite 010361  which has been online and reporting well for the last 3 months.

All of a sudden, it is giving the below error:

Nov 23 07:50:27 raspberrypi weewx[606]: restx: CWOP: Posting not enabled.

Nov 23 07:50:27 raspberrypi weewx[606]: restx: WOW: Posting not enabled.

Nov 23 07:50:27 raspberrypi weewx[606]: restx: AWEKAS: Posting not enabled.

Nov 23 07:50:27 raspberrypi weewx[606]: restx: WindGuru: service version is 0.1

Nov 23 07:50:27 raspberrypi weewx[606]: restx: WindGuru: Data will be uploaded for 10001

Nov 23 07:50:27 raspberrypi weewx[606]: engine: Starting up weewx version 3.9.2

Nov 23 07:50:27 raspberrypi weewx[606]: engine: Starting main packet loop.

Nov 23 07:50:27 raspberrypi weewx[606]: acurite: Failed attempt 1 of 10 to get LOOP data: [Errno 32] Pipe error

Nov 23 07:50:57 raspberrypi weewx[606]: acurite: Failed attempt 2 of 10 to get LOOP data: [Errno 32] Pipe error

Nov 23 07:51:27 raspberrypi weewx[606]: acurite: Failed attempt 3 of 10 to get LOOP data: [Errno 32] Pipe error

I have tried to soft reboot and hard reboot the RPi and i have checked all the cables - all seems to be in order.

This station is about 300km away from me so i've been trying to fix it via the phone with assistance from a person on site and using ssh.

Important to not that the station is half working. You can still view the apache webs server here: http://86.98.158.68:1051/ As you can see the camera is still taking pics and is online.

If you try access the weewx page (http://86.98.158.68:1051/weewx/) you can see it isn't receiving data.

The acurite display is connected to the weather sensor - so it is receiving the info. It is just not getting to the RPi. I have confirmed it is in USB MODE 4.

Any suggestions for how i can repair this locally or do i need to drive there?

When i run lsusb - i believe i am seeing the USB hub which the RPi is connected to:

pi@raspberrypi:~ $ lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 010: ID 24c0:0003  

Bus 001 Device 009: ID 05e3:0608 Genesys Logic, Inc. Hub

Bus 001 Device 008: ID 05e3:0608 Genesys Logic, Inc. Hub

Bus 001 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub

Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Would appreciate any suggestions.

Thanks

[Sean Jahnig]

As an additional note,

when i run $ usb-devices, one of the items that shows up is the acurite display:

T:  Bus=01 Lev=04 Prnt=08 Port=03 Cnt=02 Dev#= 10 Spd=1.5 MxCh= 0

D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1

P:  Vendor=24c0 ProdID=0003 Rev=00.20

S:  Product=Chaney Instrument

C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA

I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=(none)

[vince]

Running 'dmesg' usually helps provide good information that helps diagnose some issues.

[Sean Jahnig]

Thanks for the suggestion, does this mean anything to anyone?

[    2.770063] usb 1-1.2.4.4: New USB device found, idVendor=24c0, idProduct=0003, bcdDevice= 0.20

[    2.770081] usb 1-1.2.4.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[    2.770094] usb 1-1.2.4.4: Product: Chaney Instrument

[    2.780625] input: Chaney Instrument as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.4/1-1.2.4.4:1.0/0003:24C0:0003.0001/input/input0

[    2.780828] hid-generic 0003:24C0:0003.0001: input,hidraw0: USB HID v1.11 Device [Chaney Instrument] on usb-0000:01:00.0-1.2.4.4/input0 

to me it looks like the device is connected - yet it is still giving a pipe error?

[mwall]

i used to see this behavior from time to time when i was developing the acurite driver.  sometimes the usb would get into a state where the station showed up on the usb, but no communication was possible.  i had to power cycle the acurite console to recover.  sometimes that was not enough - i'd have to turn of power to the console, unplug the usb, then replug and power on.

i found that i could often induce the state by messing with the usb voltage or by messing with the console power supply

 

[Sean Jahnig]

Thanks for the suggestions. Last time i had an issue that i couldn't resolve remotely i drove down and power cycled everything including the display and that eventually fixed the problem.

I got someone on site to power cycle the display and it didn't fix it. So I was brainstorming this for a few hours and i was surprised to see that sudo apt-get update wasn't working. So i vnc'd into the pi and tried to browse a website and that didn't work either. Strange that even tho i was connected to it remotely via ssh, it was having DNS issues. I edited sudo nano /etc/resolv.conf and added nameserver 8.8.8.8 and viola it worked! Not sure how that setting got lost because i am the only one with access.

Thanks for all the support.

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/o1UrJlt2-nQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/08ab4d1c-c9a6-4aa5-9445-734fe7b0b024%40googlegroups.com.