Error - Caught WeeWxIOError: [Errno 110] Operation timed out

[Łukasz Nowak]

Hi!

I'm using the station TE923 and weewx version 3.5. And I have problem with error that occurs from time to time - basically it works fine for couple of days and stop with the error like below:

Aug 22 11:59:48 htpc weewx[2535]: engine: Caught WeeWxIOError: [Errno 110] Operation timed out

Aug 22 11:59:48 htpc weewx[2535]:     ****  Waiting 60 seconds then retrying...

Aug 22 12:00:30 htpc systemd[1]: Started CUPS Scheduler.

Aug 22 12:00:30 htpc colord[2565]: (colord:2565): Cd-WARNING **: failed to get session [pid 1826]: Nie ma takiego urzÄ…dzenia ani adresu

Aug 22 12:00:48 htpc weewx[2535]: engine: retrying...

Aug 22 12:00:48 htpc weewx[2535]: engine: Using configuration file /etc/weewx/weewx.conf

Aug 22 12:00:48 htpc weewx[2535]: engine: Loading station type TE923 (weewx.drivers.te923)

Aug 22 12:00:48 htpc weewx[2535]: te923: driver version is 0.18

Aug 22 12:00:48 htpc weewx[2535]: te923: polling interval is 10

Aug 22 12:00:48 htpc weewx[2535]: te923: observation map is {'bat_1': 'outBatteryStatus', 'bat_3': 'extraBatteryStatus2', 'bat_2': 'extraBatteryStatus1', 'bat_5': 'extraBatteryStatus4', 'bat_4': 'extraBatteryStatus3', 'bat_wind': 'windBatteryStatus', 't_in': 'inTemp', 'link_rain': 'rainLinkStatus', 't_5': 'extraTemp4', 'h_in': 'inHumidity', 'h_4': 'extraHumid3', 'h_5': 'extraHumid4', 'h_2': 'extraHumid1', 'h_3': 'extraHumid3', 'h_1': 'outHumidity', 't_2': 'extraTemp1', 'link_2': 'extraLinkStatus1', 'link_uv': 'uvLinkStatus', 'link_wind': 'windLinkStatus', 'uv': 'UV', 'bat_uv': 'uvBatteryStatus', 'link_5': 'extraLinkStatus4', 'bat_rain': 'rainBatteryStatus', 'link_3': 'extraLinkStatus2', 't_3': 'extraTemp2', 'link_1': 'outLinkStatus', 't_1': 'outTemp', 't_4': 'extraTemp3', 'link_4': 'extraLinkStatus3'}

Aug 22 12:00:48 htpc weewx[2535]: te923: Found device on USB bus= device=

Aug 22 12:00:48 htpc kernel: [84338.588479] usb 1-1.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes

Aug 22 12:00:48 htpc kernel: [84338.868006] usb 1-1.1: reset low-speed USB device number 4 using xhci_hcd

Aug 22 12:00:48 htpc kernel: [84339.166646] usb 1-1.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes

Aug 22 12:00:49 htpc weewx[2535]: te923: Failed attempt 1 of 5 to read data: Bad header byte: ff != 5a

Aug 22 12:00:53 htpc weewx[2535]: te923: Failed attempt 2 of 5 to read data: Bad header byte: 00 != 5a

Aug 22 12:00:56 htpc weewx[2535]: te923: Failed attempt 3 of 5 to read data: Bad header byte: 59 != 5a

Aug 22 12:00:59 htpc weewx[2535]: te923: Failed attempt 4 of 5 to read data: Bad header byte: aa != 5a

Aug 22 12:01:03 htpc weewx[2535]: te923: Failed attempt 5 of 5 to read data: Bad header byte: ff != 5a

Aug 22 12:01:06 htpc weewx[2535]: engine: Unable to load driver: Read failed after 5 tries

Aug 22 12:01:06 htpc weewx[2535]:     ****  Exiting...

When I restart ubuntu (16.04) then it works well again.

Can I ask you for any advise?

Thanks!!!!!!!

[mwall]

is this x86, x64, arm, or something else?

what caused the WeeWxIOError at the beginning of your post?

was this during system startup or when you started weewx manually?

what happens when you start weewx without restarting the os?  does weewx communicate with the station, or do you have to do a system reboot to get weewx to communicate?

it is odd that there is a message about 'Found device on USB bus= device=' but no bus or device is reported.

as a brute force fix you could use the loop-on-init option to weewxd.  that will make weewx attempt to restart in the situation you posted.  then monitor your logs (using logwatch) to see how often it happens.

something changed from debian 7 to debian 8 that is causing grief for the te923 driver.  i don't know if it is systemd or the kernel usb drivers or something else.

m

[Łukasz Nowak]

Hi!

x64 Debian 16.04, kernel  4.4.0-34

what caused the WeeWxIOError at the beginning of your post?

No idea,I see now I missed very first entry directly on this:

Aug 22 11:59:48 htpc weewx[2535]: engine: Shutting down StdReport thread

It happens after system OS, however not directly, it works fine usually for days or two. I cannot restart manually, need to restart OS

I'll try your work-around with loop-on-init, thanks!!!!

[Łukasz Nowak]

Can I ask you for little help? I'm quite new in linux and have a problem with implementation of this:

as a brute force fix you could use the loop-on-init option to weewxd.  that will make weewx attempt to restart in the situation you posted

I'm running weewx as daemon, should I edit /etc/init.d/weewx somehow to add this loop-on-init parameter? I couldn't find anything about it in docs

Thanks in advance!

[mwall]

On Tuesday, August 23, 2016 at 8:41:04 AM UTC-4, Łukasz Nowak wrote:

Can I ask you for little help? I'm quite new in linux and have a problem with implementation of this:

as a brute force fix you could use the loop-on-init option to weewxd.  that will make weewx attempt to restart in the situation you posted

I'm running weewx as daemon, should I edit /etc/init.d/weewx somehow to add this loop-on-init parameter? I couldn't find anything about it in docs

you can put it in the weewx.conf file at the root level:

debug = 0
loop_on_init = True
WEEWX_ROOT = ...
socket_timeout = 20
version = 3.5.0
...

m

[Andrew Milner]

Tom/Matthew - FYI how/when/where to use loop-on-init appears to be missing from all the documentation both in the .conf and also for the command line.  Are there any other undocumented command line/.conf options??