V2.3a - Rapid Fire is not working ** solved **

[cbhiii]

Is there a way to check if the Weather Underground rapid fire packets are being sent to Weather Underground? A log file maybe?

First problem:
Since I upgraded to v2.3a I've noticed that Weather Underground is not receiving my rapid fire data every few seconds because my station is no longer listed as 'Rapid Fire' on their site.

Second problem:
Regular packets are taking 10 minutes to be sent to Weather Underground even though my setting is for 5 minutes.

You can see the times of my packets here and sometimes there are sent at 5 minutes and sometimes 10 minutes.

http://www.wunderground.com/weatherstat ... =KMIROCKF4


Can you confirm this?

[bsparks]

Good call. I did not notice that, but I apparently am no longer in rapid fire as well. I have the same equipment setup that you do--a Davis Vantage Pro2 with Meteohub.

My wind speed has always been weird, just like yours... in those strange .9s and 2mph increments.

I have also gotten a slew of connect errors from regular Wunderground (not rapid fire)

I'm going to see what I can find out.

Boris posted this in another thread:
when you login via ssh you can initiate a weather network update in debug mode with \"/home/meteohub/meteonet -d\". It will take some seconds until data gets printed

[admin]

wu rapid fire is realized by running the weather network part of Meteohub as a daemon. This daemon is named \"meteonet\". If you are familiar with SSH you could login and check by \"ps | grep meteonet\" if such a process is running. It is started on every reboot. So rebooting might help or saying \"rcmeteonetd start\" in an SSH session will make this running.

Question remains... why has this daemon being halted on your system? I don't expect doing the update will inhibit this daemon being started.

[bsparks]

I ran the ps | grep meteonet command, and I'm showing that the meteonet process is running.

Running rcmeteonetd start and then ps | grep again shows two instances running. Restarting the NSLU2 seemed to fix the problem, as we are sending in Rapid Fire updates. I'll see if that also fixes the 50+ connection errors I was receiving each day from Meteohub.

[cbhiii]

A reboot also seemed to fix my problem. It had been running since the upgrade. Not sure if this problem will come back in the future or not.

[bsparks]

The problem did come back. RapidFire quit working. A reboot fixed it again, but it doesn't appear to be stable.

[cbhiii]

I can confirm this as well. Rapid Fire is no longer working. My status is listed as normal.

This is not good. When will a fix be available?

[cbhiii]

Ok. And now all of a sudden it's working again and I did not do anything to Meteohub. It just started working.

This is an intermittent problem it appears.

[admin]

Are there any log file entries that might shed some light on this?

rapid file is realized by a daemon, so if this daemon quits, no more rapd fire.

reguluar update every 5 minutes or so is dane by cron (as the other weather network puch services) so this should run regardless what has happend to the daemon.

Meteohub needs the data logger running to feed the weather networks with fresh data. If the data logger process is down, weather network update functions will be suspended as well.

[cbhiii]

I'll be watching it under v2.3c now and see what happens.

[admin]

Solved from 2.3d on