"vantage: no <ACK> received..." with Davis Pro2 IP logger crashes weewx

989 views
Skip to first unread message

William Phelps

unread,
Jun 20, 2015, 3:20:29 PM6/20/15
to weewx...@googlegroups.com
One of my weewx installs has a Davis Pro2 with an IP logger.  With the upgrade to 3.1.0, I've noticed several "crashes" that I wasn't getting before the upgrade.

Relevant portion of syslog:

Jun 15 18:05:22 bone1 weewx[2226]: restx: CWOP: Published record 2015-06-15 18:05:00 PDT (1434416700)
Jun 15 18:05:28 bone1 weewx[2226]: vantage: No <ACK> received from console
Jun 15 18:05:28 bone1 weewx[2226]: engine: Shutting down StdReport thread
Jun 15 18:05:28 bone1 weewx[2226]: cheetahgenerator: Generated 16 files for report StandardReport in 6.37 seconds
Jun 15 18:05:36 bone1 weewx[2226]: genimages: Generated 30 images for StandardReport in 7.18 seconds
Jun 15 18:05:36 bone1 weewx[2226]: imageStackedWindRose: Generated 1 images for StackedWindRose in 0.21 seconds
Jun 15 18:05:39 bone1 weewx[2226]: ftpupload: Attempt #1. Failed uploading /public_html/weather/daywindbig.png to andromeda.lunarpages.com. Reason: 503 Entering Passive Mode (67,210,126,45,163,210)
Jun 15 18:05:41 bone1 weewx[2226]: ftpupload: Attempt #1. Failed uploading /public_html/weather/daycpupercent.png to andromeda.lunarpages.com. Reason: 503 Entering Passive Mode (67,210,126,45,161,203)
Jun 15 18:05:46 bone1 weewx[2226]: reportengine: ftp'd 47 files in 10.41 seconds
Jun 15 18:05:46 bone1 weewx[2226]: wxdata: shutdown
Jun 15 18:05:46 bone1 weewx[2226]: wxdata: server shutdown
Jun 15 18:05:51 bone1 weewx[2226]: engine: Caught WeeWxIOError: No <ACK> received from Vantage console
Jun 15 18:05:51 bone1 weewx[2226]:     ****  Waiting 60 seconds then retrying...
Jun 15 18:06:51 bone1 weewx[2226]: engine: retrying...
Jun 15 18:06:51 bone1 weewx[2226]: engine: Using configuration file /home/weewx/weewx.conf
Jun 15 18:06:51 bone1 weewx[2226]: engine: Loading station type Vantage (weewx.drivers.vantage)
Jun 15 18:06:58 bone1 weewx[2226]: vantage: No <ACK> received from console
Jun 15 18:06:58 bone1 weewx[2226]: engine: Unable to load driver: No <ACK> received from Vantage console
Jun 15 18:06:58 bone1 weewx[2226]:     ****  Exiting...


It looks like when we have a brief network outage, when weewx "retries" and gets the same faliure again, it just quits.  The problem is that this is an unattended RPI running in a remote location. I need it to keep trying - the network outages only last a few minutes at most.

I have just added the "--loop-on-init" option to DAEMON_ARGS in /etc/init.d/weewx - that will take care of this?

William

Thomas Keffer

unread,
Jun 20, 2015, 3:53:38 PM6/20/15
to weewx-user
It should.

Weewx keeps trying indefinitely except on initial startup. The thinking is that the problem is likely to be a configuration problem.

Option --loop-on-init overrides this. It will keep trying, even on startup.

-tk


--
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.
For more options, visit https://groups.google.com/d/optout.

William Phelps

unread,
Jun 20, 2015, 4:14:11 PM6/20/15
to weewx...@googlegroups.com
Note that in this case the exit happened on a retry.  I would not call that "initial startup", so I'm wondering if it's working as intended.

Thomas Keffer

unread,
Jun 20, 2015, 4:20:45 PM6/20/15
to weewx-user
Sorry, I wasn't clear. Retries are "taken from the top." They essentially restart the weewx engine from the beginning of the program. So, in that sense, it is an initial startup.

Option loop-on-init will keep retrying even though this is a restart.

-tk

Mike

unread,
Jul 5, 2017, 11:18:51 AM7/5/17
to weewx-user
Hi guys,

It seems I am facing the same issue every 24 - 36 hours. I am pretty sure my local network is fine, even the port forwarding
to my PWS.  I don´t like to open a new post. I am using weewx V 3.71

Where do I have to add the "loop-on-it ?

IBelow the important part from the log

Thanks in advance

Jul  5 19:05:40 sd-69780 weewx[32468]: restx: Meteotemplate: Published record 2017-07-05 19:05:00 ICT (1499256300)
Jul  5 19:10:15 sd-69780 weewx[32468]: vantage: Getting archive packets since 2017-07-05 19:05:00 ICT (1499256300)
Jul  5 19:10:17 sd-69780 weewx[32468]: vantage: gentle wake up of console successful
Jul  5 19:10:21 sd-69780 weewx[32468]: vantage: Retrieving 1 page(s); starting index= 2
Jul  5 19:10:23 sd-69780 weewx[32468]: manager: Added record 2017-07-05 19:10:00 ICT (1499256600) to database 'weewx'
Jul  5 19:10:23 sd-69780 weewx[32468]: manager: Added record 2017-07-05 19:10:00 ICT (1499256600) to daily summary in 'weewx'
Jul  5 19:10:23 sd-69780 weewx[32468]: vantage: empty record page 0; index 3
Jul  5 19:10:23 sd-69780 weewx[32468]: reportengine: Running reports for latest time in the database.
Jul  5 19:10:23 sd-69780 weewx[32468]: vantage: Requesting 200 LOOP packets.
Jul  5 19:10:23 sd-69780 weewx[32468]: reportengine: Running report SteelSeries
Jul  5 19:10:23 sd-69780 weewx[32468]: reportengine: Found configuration file /etc/weewx/skins/ss/skin.conf for report SteelSeries
Jul  5 19:10:23 sd-69780 weewx[32468]: copygenerator: copied 0 files to /var/www/html/bang-saray/weewx/ss
Jul  5 19:10:23 sd-69780 weewx[32468]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Jul  5 19:10:23 sd-69780 weewx[32468]: manager: Daily summary version is 2.0
Jul  5 19:10:23 sd-69780 weewx[32468]: cheetahgenerator: Generated 2 files for report SteelSeries in 0.10 seconds
Jul  5 19:10:23 sd-69780 weewx[32468]: manager: Daily summary version is 2.0
Jul  5 19:10:24 sd-69780 weewx[32468]: imagegenerator: Generated 11 images for SteelSeries in 0.43 seconds
Jul  5 19:10:24 sd-69780 weewx[32468]: reportengine: Running report StandardReport
Jul  5 19:10:24 sd-69780 weewx[32468]: reportengine: Found configuration file /etc/weewx/skins/Sofaskin/skin.conf for report StandardReport
Jul  5 19:10:24 sd-69780 weewx[32468]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Jul  5 19:10:24 sd-69780 weewx[32468]: manager: Daily summary version is 2.0
Jul  5 19:10:24 sd-69780 weewx[32468]: restx: Wunderground-PWS: Published record 2017-07-05 19:10:00 ICT (1499256600)
Jul  5 19:10:25 sd-69780 weewx[32468]: cheetahgenerator: Generated 7 files for report StandardReport in 1.25 seconds
Jul  5 19:10:25 sd-69780 weewx[32468]: manager: Daily summary version is 2.0
Jul  5 19:10:25 sd-69780 weewx[32468]: vantage: gentle wake up of console successful
Jul  5 19:10:25 sd-69780 weewx[32468]: imagegenerator: aggregate interval required for aggregate type max
Jul  5 19:10:25 sd-69780 weewx[32468]: imagegenerator: line type rainRate skipped
Jul  5 19:10:26 sd-69780 weewx[32468]: imagegenerator: Generated 13 images for StandardReport in 0.74 seconds
Jul  5 19:10:26 sd-69780 weewx[32468]: copygenerator: copied 0 files to /var/www/html/bang-saray/weewx
Jul  5 19:10:26 sd-69780 weewx[32468]: reportengine: Running report FTP
Jul  5 19:10:26 sd-69780 weewx[32468]: reportengine: Found configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
Jul  5 19:10:26 sd-69780 weewx[32468]: ftpgenerator: FTP upload not requested. Skipped.
Jul  5 19:10:26 sd-69780 weewx[32468]: reportengine: Running report RSYNC
Jul  5 19:10:26 sd-69780 weewx[32468]: reportengine: Found configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Jul  5 19:10:26 sd-69780 weewx[32468]: rsyncgenerator: rsync upload not requested. Skipped.
Jul  5 19:10:41 sd-69780 weewx[32468]: restx: Meteotemplate: Published record 2017-07-05 19:10:00 ICT (1499256600)
Jul  5 19:12:29 sd-69780 weewx[32468]: vantage: ip-read error: timed out
Jul  5 19:12:29 sd-69780 weewx[32468]: vantage: LOOP try #1; error: timed out
Jul  5 19:12:29 sd-69780 weewx[32468]: vantage: Requesting 200 LOOP packets.
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-read error: [Errno 104] Connection reset by peer
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: LOOP try #2; error: Unable to wake up Vantage console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Requesting 200 LOOP packets.
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: LOOP try #3; error: Unable to wake up Vantage console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Requesting 200 LOOP packets.
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: LOOP try #4; error: Unable to wake up Vantage console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Requesting 200 LOOP packets.
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: LOOP try #5; error: Unable to wake up Vantage console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Requesting 200 LOOP packets.
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: LOOP try #6; error: Unable to wake up Vantage console
Jul  5 19:12:31 sd-69780 weewx[32468]: vantage: LOOP max tries (6) exceeded.
Jul  5 19:12:31 sd-69780 weewx[32468]: engine: Main loop exiting. Shutting engine down.
Jul  5 19:12:31 sd-69780 weewx[32468]: engine: Shutting down StdReport thread
Jul  5 19:12:31 sd-69780 weewx[32468]: engine: StdReport thread has been terminated
Jul  5 19:12:31 sd-69780 weewx[32468]: restx: Shut down Wunderground-PWS thread.
Jul  5 19:12:31 sd-69780 weewx[32468]: juergen...@freenet.de
Jul  5 19:12:31 sd-69780 weewx[32468]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data.
Jul  5 19:12:31 sd-69780 weewx[32468]:     ****  Waiting 60 seconds then retrying...
Jul  5 19:13:31 sd-69780 weewx[32468]: engine: retrying...
Jul  5 19:13:31 sd-69780 weewx[32468]: engine: Using configuration file /etc/weewx/weewx.conf
Jul  5 19:13:31 sd-69780 weewx[32468]: engine: debug is 1
Jul  5 19:13:31 sd-69780 weewx[32468]: engine: Initializing engine
Jul  5 19:13:31 sd-69780 weewx[32468]: engine: Loading station type Vantage (weewx.drivers.vantage)
Jul  5 19:13:31 sd-69780 weewx[32468]: vantage: driver version is 3.0.10
Jul  5 19:13:31 sd-69780 weewx[32468]: vantage: Opened up ethernet host xxxxxxx.duckdns.org on port 22222. timeout=120.0, tcp_send_delay=2.0
Jul  5 19:15:33 sd-69780 weewx[32468]: vantage: ip-read error: timed out
Jul  5 19:15:33 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:15:35 sd-69780 weewx[32468]: vantage: gentle wake up of console successful
Jul  5 19:15:37 sd-69780 weewx[32468]: vantage: _setup; hardware type is 16
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-read error: [Errno 104] Connection reset by peer
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #0 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #1 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #2 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #3 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #4 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: ip-write error: [Errno 32] Broken pipe
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: retry  #5 failed
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: Unable to wake up console
Jul  5 19:15:47 sd-69780 weewx[32468]: vantage: Max retries exceeded while getting EEPROM data at address 0xF
Jul  5 19:15:47 sd-69780 weewx[32468]: import of driver failed: While getting EEPROM data value at address 0xF (<class 'weewx.RetriesExceeded'>)
Jul  5 19:15:47 sd-69780 weewx[32468]: engine: Unable to load driver: While getting EEPROM data value at address 0xF
Jul  5 19:15:47 sd-69780 weewx[32468]:     ****  Exiting...

Mike

unread,
Jul 5, 2017, 11:29:09 AM7/5/17
to weewx-user
Sorry I forgot to tell, I am using the a Davis Pro 2 with an IP logger


Am Sonntag, 21. Juni 2015 02:20:29 UTC+7 schrieb William Phelps:

gjr80

unread,
Jul 5, 2017, 4:05:47 PM7/5/17
to weewx-user
Hi,

To use loop_on_init edit weewx.conf and put the line:

loop_on_init = True

on a line at the top or root level (ie not in any [] stanzas). You could put it just under debug = 0. You will need to stop then start weeWX for the new setting to take effect.

Gary

Mike

unread,
Jul 6, 2017, 7:56:02 AM7/6/17
to weewx-user
Hi Gary,

I did some more tests today. I think it is working now and I found out the reason. At the moment I don´t know what the entry

loop_on_init = True

is doing. My guess it is shooting down the driver and reload it.

For days ago my google search was: weewx vantage: ip-read error: timed out

I saw a lot of Germans are facing this issue. In Germany we are getting up to 99% a dynamic IP adress from our Internet Service Provider (ISP). I know in England are most ISP´s
providing a static IP, such as BT, Virgin or Sky. I am pretty sure weewx users with a static IP from the ISP are not facing this issue.

Weewx users with a dynamic WAN IP need to use a dynIP like from www.noip.com - This are no new news. For example, my Dyndns client is checking every 5
minutes for the current IP.

First my idea was to solve the problem, changed the weewx.conf

timeout = 120

and

max_tries = 6

Weewx will try 12 minutes to reconnect to the new WAN IP address. It did not work without a

loop_on_init = True

I did a TCP dump on port 22222

tcpdump -ni em1 port 22222

Weewx was not able to send the requests to the "new WAN IP" without 
loop_on_init = True Thats why Weewx or the driver gave up and ends up with an Exit in the log file.

I try to help to improve Weewx because I like the project.

@@ tk

During the Weewx setup, enter "station name"........choose your "PWS" I would add in the next Weewx version, something like: "Does your ISP provide a static or dynamic IP?" If dynamic add

loop_on_init = True

into the conf file.

If you guys like I can write a how to in English and German.

Thanks again
Michael

Andrew Milner

unread,
Jul 6, 2017, 8:23:54 AM7/6/17
to weewx-user
@Tom - I think the main problem is that the documentation does not appear to say anything, anywhere, about loop_on_init = True - neither the user guide nor the hardware guide - or if it is somewhere it is not easy to find!!

.

gjr80

unread,
Jul 7, 2017, 7:21:36 AM7/7/17
to weewx-user
I'm certainly no expert on the IP logger but I wouldn't have thought a dynamic WAN IP would be affecting the logger when used with weeWX. I thought the typical use case of the logger with weeWX was to connect both the IP logger and the weeWX device to a local router or switch and the IP logger communicates solely with the weeWX device with no knowledge of the WAN. If however, the IP logger was being used to talk to WeatherLink.com I could see a dynamic WAN IP maybe causing an issue. But as far as I know it's either weeWX or WeatherLink.com but not both. Will be interesting to hear Tom's view.

Um, your IP logger is not somehow still trying to connect to WeatherLink.com is it?

When set to True loop_on_init simply catches any console/station initialisation failures (ie failure to load the station driver) and forces a retry (ie reload the driver) after 60 seconds. This will happen forever rather than just causing weeWX to exit. Looking at the history it seems loop_on_init was added as an option to weewx.conf in v3.5.0 (March 2016) to mimic the weewxd command line --loop-on-init option (which was previously the --retry option). This might explain why the documentation slipped through the cracks. Am sure Tom will shed some more light in this.

Gary

Luc Heijst

unread,
Jul 8, 2017, 6:16:43 PM7/8/17
to weewx-user
Hi Mike,

I debugged the vantage driver for the ip-datalogger in March 2016 and came across the same errors you have now.
I discovered the ip-datalogger needed other timings than the serial and usb dataloggers.

This is what I found in my old notes:

    # Serial delays (when using serial or USB):
    command_delay = 0.2

    # TCP delays (when using the WeatherLinkIP):
    command_delay = 1.0
    tcp_send_delay = 0.2

The default values of the current driver are:
    command_delay = 0.5
    tcp_send_delay = 0.5

Maybe the command_delay time is too short for the ip-datalogger.
Default it is 0.5 s and it should be 1.0 s (according to my notes one year ago)
You can try to increase the command_delay time by putting in the [Vantage] section of weewx.conf:
    command_delay = 1.0

Maybe it helps.

Luc


Thomas Keffer

unread,
Jul 9, 2017, 6:47:09 PM7/9/17
to weewx-user
Michael,

loop_on_init only affects how an error in the driver is handled on startup.

Normally, if an error is encountering when weewx is starting up ("initializing"), the program exits. The assumption is that the user has a configuration problem, so there is no point in trying the same thing over-and-over again.

However, if loop_on_init is set to true, then weewx will restart from the top and keep trying.

In either case, once a successful startup is achieved, if an error occurs, weewx will restart from the top.

On to your WLIP problems. The Davis serial protocol is very "chatty," with lots of state transitions. This makes it very difficult to run it over a WAN. It should work just fine with either static or dynamic IP assignments. However, it will be very sensitive to firewall settings.

I do not own an IP logger, so it's very hard for me to debug them remotely. 

-tk

--
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+unsubscribe@googlegroups.com.

Mike

unread,
Jul 12, 2017, 2:02:11 AM7/12/17
to weewx-user
Thanks for the informations.

@@ Luc

Are you getting a dynamic ot static IP from your ISP?
Do you use loop_on_init = True in your conf file?

Thanks again
Michael
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

Luc Heijst

unread,
Jul 12, 2017, 8:11:03 AM7/12/17
to weewx-user
Hi Michael,

I don't have an IP-logger myself.

Last year I was remote testing a Raspberry PI model B with a Davis IP-logger in Germany (from Suriname) .
Don't know if the IP was static or dynamic. I don't think I had loop_on_init = True in the config file.

I was playing with the various timings and also changed the wake-up and other logic.

I checked my old logs. The remote system got broken pipe errors with version 3.0.6 and the errors were gone with version 3.0.5.
Unfortunately I don't have copies anymore of those versions to check the differences.

Luc

Luc Heijst

unread,
Jul 12, 2017, 8:42:33 AM7/12/17
to weewx-user
Hi Michael,

I checked my old logs again. As weewx was started automatically after a fatal error, I must have set loop_on_init = True.
See log example below:
Mar  3 15:04:25 raspberrypi weewx[23145]: vantage: Opened up ethernet host 192.168.0.120 on port 22222
Mar  3 15:04:25 raspberrypi weewx[23145]: vantage: Getting archive packets since 2016-03-03 14:50:00 CET (1457013000)
Mar  3 15:04:31 raspberrypi weewx[23145]: vantage: raise WeeWxIOError-8 read chars 2 received 0
Mar  3 15:04:31 raspberrypi weewx[23145]: vantage: remaining: 4096, raise WeeWxIOError-7 socket error-3 |[Errno 11] Die Ressource ist zur Zeit nicht verfügbar|
Mar  3 15:04:32 raspberrypi weewx[23145]: vantage: remaining: 2, raise WeeWxIOError-7 socket error-3 |[Errno 104] Die Verbindung wurde vom Kommunikationspartner zurückgesetzt|
Mar  3 15:04:32 raspberrypi weewx[23145]: engine: Main loop exiting. Shutting engine down.
Mar  3 15:04:32 raspberrypi weewx[23145]: vantage: raise WeeWxIOError-9 write socket error [Errno 32] Datenübergabe unterbrochen (broken pipe)
Mar  3 15:04:32 raspberrypi weewx[23145]: vantage: input buffer flushed; read: 0 chars
Mar  3 15:04:32 raspberrypi weewx[23145]: vantage: raise WeeWxIOError-9 write socket error [Errno 32] Datenübergabe unterbrochen (broken pipe)
Mar  3 15:07:07 raspberrypi weewx[23494]: engine: Initializing engine
Mar  3 15:07:07 raspberrypi weewx[23494]: driver version is 3.0.2

Mike

unread,
Jul 14, 2017, 1:02:03 AM7/14/17
to weewx-user
Hi Luc,

it seems the issue is really coming from the IP Logger. If I read the Log well the PWS and the Rasp. are/were running in a local
network. Mar  3 15:04:25 raspberrypi weewx[23145]: vantage: Opened up ethernet host 192.168.0.120 on port 22222

In this case it doesn´t matter if you get a static or dynamic IP from the ISP.

After I have changed the conf file with: loop_on_init = True weewx is running well. Had yesterday a power failure for 6 hours, my local network
was down - weewx reconnected after my local router was up again.

Thaanks again.
Michael
Reply all
Reply to author
Forward
0 new messages