meteohub.de

Posted: **Thu Mar 10, 2011 9:18 pm**

Immer wieder kommt es zu folgenden Problemen:

logger (10.03.2011 16:29:58): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:30:05): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:30:15): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:30:25): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:30:27): child process received timeout signal (14).
logger (10.03.2011 16:30:27): disconnect station 0 (Vantage).
logger (10.03.2011 16:30:27): disconnect station 1 (System Data).
logger (10.03.2011 16:30:28): data logger stopped.
logger (10.03.2011 16:30:29): data logger (version 4.7d, build 360) started.
logger (10.03.2011 16:30:30): connect station 0 (Vantage via TCP/IP).
logger (10.03.2011 16:30:30): connect station 1 (System Data via Plug-in).
logger (10.03.2011 16:30:31): station 0 (Vantage), wakeup sent.
logger (10.03.2011 16:30:31): station 0 (Vantage), syncing.
logger (10.03.2011 16:30:31): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:30:41): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:30:51): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:31:00): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:31:10): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:31:20): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:31:28): station 0 (Vantage), wakeup sent.
logger (10.03.2011 16:31:28): station 0 (Vantage), syncing.
logger (10.03.2011 16:31:28): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:31:38): station 0 (Vantage), gettime request sent.

Irgendwann klappt es dann doch:

logger (10.03.2011 16:35:58): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:36:00): child process received timeout signal (14).
logger (10.03.2011 16:36:00): disconnect station 0 (Vantage).
logger (10.03.2011 16:36:00): disconnect station 1 (System Data).
logger (10.03.2011 16:36:01): data logger stopped.
logger (10.03.2011 16:36:02): data logger (version 4.7d, build 360) started.
logger (10.03.2011 16:36:02): connect station 0 (Vantage via TCP/IP).
logger (10.03.2011 16:36:02): connect station 1 (System Data via Plug-in).
logger (10.03.2011 16:36:03): station 0 (Vantage), wakeup sent.
logger (10.03.2011 16:36:04): station 0 (Vantage), syncing.
logger (10.03.2011 16:36:04): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:36:09): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:36:19): station 0 (Vantage), gettime request sent.
logger (10.03.2011 16:36:19): station 0 (Vantage), time offset of Vantage: -1 minutes
logger (10.03.2011 16:36:19): station 0 (Vantage), eeprom request sent.
logger (10.03.2011 16:36:20): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (10.03.2011 16:36:20): station 0 (Vantage), transmitter 1 active as station type (#0) "ISS".
logger (10.03.2011 16:36:20): station 0 (Vantage), transmitter 2 active as station type (#4) "Wireless Anemometer".
logger (10.03.2011 16:36:20): station 0 (Vantage), transmitter 3 active as station type (#8) "SensorLink".
logger (10.03.2011 16:36:20): station 0 (Vantage), transmitter 4 active as station type (#1) "Temperature Only" mapped to "t1".
logger (10.03.2011 16:36:25): station 0 (Vantage), data gap of 111 minutes, start reading Vantage's internal logger after 2011-03-10 16:36 (Vantage's local time).
logger (10.03.2011 16:36:26): station 0 (Vantage), internal logger provides 5 pages of data.
logger (10.03.2011 16:36:28): station 0 (Vantage), finished reading internal logger, 23 records inserted.

Es kann mehrere Stunden dauern bis es endlich wieder Daten gelesen werden. Wenn ich von Hand eingreife und für 2-3 Minuten die Datenerfassung anhalte funktioniert es danach SOFORT wieder.

Zur Zeit ist 4.7d (Build 354) aktiv

Posted: **Sun Mar 13, 2011 10:01 am**

Heute wieder.
Nach 2 Stunden ohne Verbindung kurz (2 Min) von Hand gestoppt, danach war alles wieder ok.

Posted: **Sun Mar 20, 2011 9:43 am**

Nachdem ich die Meldungen an Weatherlink.com deaktiviert habe läuft alles stabil.

Posted: **Sun Mar 20, 2011 12:42 pm**

Hi,

This is what I've seen as well, it seems that the uploads to Weatherlink are affecting meteohub. This is more likely to happen if you look at the Weahelink page of you station. Not sure why this happens, I think that a better retry mechanism in MH should be able to work around this.

Ysbrand

Posted: **Sun Mar 20, 2011 5:54 pm**

Rabit, I have had a similar problem as well on 4.6t. The Meteohub prevents the uploads to weatherlink.com from occurring. If I manually stop the data logging for several minutes, the weatherlink.com is updated.

I think when this occurs the Meteohub LOOPing and the the weatherlink.com upload are in contention. The WLIP effectively locks up as far as weatherlink.com uploads. The Meteohub system load also climbs to unreasonably high levels.

As a solution to fix the problem, I have tried increasing the "Hold time for live data" to 10 minutes. This seemed to eliminate the worst of the problem as I haven't had to manually stop logging to allow a weatherlink.com update for a while.

Posted: **Fri Mar 25, 2011 2:39 pm**

Still working fine for me now, but i will check the 10min setting.

I think the weatherlink-ip device is to weak to handle all the requests. It would be a good feature to adjust the uploads to weatherlink.com. An intervall vor the archive data, and a second one for the live data.

Posted: **Fri Jun 03, 2011 11:52 pm**

Hi there,

my weatherstation runs since about one month. Up to now meteohub collected data from weatherlink perfectly. But since a few days meteohub stops collecting data from weatherlink after a few hours of working.
I restart meteohub every day at 5am automatically. Other data collecting works fine, just weatherlink seems to struggle...any idea?

Link to my systemdata + weatherdata see http://untersiggenthal.meteo.selfip.inf ... ?show=data

meteohub.de

timeout / disconnect ..

timeout / disconnect ..

Re: timeout / disconnect ..

Re: timeout / disconnect ..

Re: timeout / disconnect ..

Re: timeout / disconnect ..

Re: timeout / disconnect ..

Re: timeout / disconnect ..