Intermittant Fault sending to CWOP

[mattjdalton]

Hi All,

I get an intermittent fault in sending data to CWOP. (You can check the data at CW9477). I have meteohub set for 5 minute updates to both CWOP and WeatherUnderground.

The alert message I get is as follows:

error write socket: Connection reset by peer

Any ideas? Has been working fine, but seems to be deteriorating since 1.8.

Thanks


Matt

[trouserless]

same issue here. Boris has been looking into this and hopefully will have something for us soon.

[admin]

My system was also impacted by the CWOP issue. Working on the next update I did change a bit of the timing, that might help to get a connection even when the servers are quite busy. However the errors did mostly disappear again.

See my log on weather networks. It starts with some problems with CWOP, but looks fine now. My experience with weather networks is, that they do have server problems from time to time, so it is not unusual to see connection problems come and go without knowing why:

2008.01.26 23:32:07 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 00:07:38 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 00:26:56 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 00:37:00 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 00:45:24 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 01:01:45 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 01:12:41 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 01:17:54 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 01:26:31 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 01:30:48 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 01:42:57 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 01:55:53 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 02:02:35 meteohub: weathernet: cwop: error write socket: Connection reset by peer
2008.01.27 03:11:10 meteohub: weathernet: wetterarchiv: upload to wetterarchiv failed: [SQL-ERROR:CONNECT][SQL-ERROR: SELECT][SQL-ERROR:QUERY]status=ERROR&errorstring=Ihre Wettermeldung konnte nicht gespeichert werden. Folgende Fehler traten auf: Benutzerdaten falsch
2008.01.27 04:01:03 meteohub: weathernet: weather underground: no response from weather underground
2008.01.27 04:01:04 meteohub: weathernet: cwop: error server connect: Success
2008.01.27 04:03:48 meteohub: weathernet: weatherbug: no response from weather bug
2008.01.28 03:10:58 meteohub: weathernet: wetterarchiv: upload to wetterarchiv failed: [SQL-ERROR:CONNECT][SQL-ERROR: SELECT][SQL-ERROR:QUERY]status=ERROR&errorstring=Ihre Wettermeldung konnte nicht gespeichert werden. Folgende Fehler traten auf: Benutzerdaten falsch
2008.01.28 04:00:12 meteohub: weathernet: weather underground rapid fire: no response from weather underground
2008.01.28 04:00:23 meteohub: weathernet: weather underground rapid fire: no response from weather underground
2008.01.28 04:00:52 meteohub: weathernet: weather underground: no response from weather underground
2008.01.28 04:01:06 meteohub: weathernet: cwop: error server connect: Success
2008.01.28 04:02:01 meteohub: weathernet: weatherbug: no response from weather bug
2008.01.28 04:03:22 meteohub: weathernet: weather underground rapid fire: no response from weather underground
2008.01.28 19:57:41 meteohub: weathernet: cwop: error write socketi (2): Connection reset by peer

Are you still impacted by these problems with cwop? Or does it work again without popping that many errors?

[trouserless]

Here's the culprit...a /. posting a few days ago...hoping it clears up soon. You are correct once again Boris :-)


http://www.wxqa.com/news.html


\"Jan 21, 2008 - Yesterday, there was a slashdot posting about Personal Weather Stations that mentioned CWOP. Because of this, the CWOP web site traffic for yesterday was about eight times normal.\"

[mattjdalton]

Hi Boris,

I was reading the FAQ of SWOP, and this text is interesting, and it may be something that you could include in an update:

1. How often should I send data? Any packet rate that you are comfortable with is fine with us as long as it is not faster than one data packet every 9 or 10 minutes. Right now data are sent from findu.com to NOAA every 15 minutes, so one packet every 10 minutes is adequate. We recommend that you set your software so that the first packet of the hour is sent in the minute that matches the last number in your CW ID or ham callsign. The purpose of this is to even out the data flow received by the APRS-IS servers to reduce the number of connects at multiples of 5 minutes after top of the hour. If your application does not let you set the start time or if your last number is 0 or 5, select a time interval of 9 or 11 minutes.

Thanks

Matt

[admin]

CWOP is really a problem at the moment.

Status: Frequency of sending data is not our issue. Physical socket connection isn't the issue either.

Must be something on higher protocol level... stay tuned.