When Meteobridge does not get fresh data for a couple of minutes, then it restarts the logging
process to give it a frsh try. But when you have good RF reception, this shouldn't happen at at all.
Can you change position of Meteobridge, USB cabe and WMR console a bit? May be it gets tons of
RF ...
Search found 6 matches
- Sat Jan 17, 2015 7:42 pm
- Forum: Meteobridge Discussion
- Topic: Upgrade meteobridge version 2.2 to 2.4 problems **solved**
- Replies: 22
- Views: 11107
- Sat Jan 17, 2015 7:15 pm
- Forum: Meteobridge Discussion
- Topic: Upgrade meteobridge version 2.2 to 2.4 problems **solved**
- Replies: 22
- Views: 11107
Re: Upgrade meteobridge version 2.2 to 2.4 problems **solved
That's what I thought. Does the timeout error message have any particular significance? I'm curious why the logger would just periodically quit. The automatic reboot script mentioned in the other thread is one option to deal with it I guess.admin wrote:no. looks good.
- Sat Jan 17, 2015 6:57 pm
- Forum: Meteobridge Discussion
- Topic: Upgrade meteobridge version 2.2 to 2.4 problems **solved**
- Replies: 22
- Views: 11107
Re: Upgrade meteobridge version 2.2 to 2.4 problems **solved
Any further thoughts on that?sar104 wrote:505L. 59% used.
- Fri Jan 16, 2015 11:28 pm
- Forum: Meteobridge Discussion
- Topic: Upgrade meteobridge version 2.2 to 2.4 problems **solved**
- Replies: 22
- Views: 11107
Re: Upgrade meteobridge version 2.2 to 2.4 problems **solved
505L. 59% used.
- Fri Jan 16, 2015 8:37 pm
- Forum: Meteobridge Discussion
- Topic: Upgrade meteobridge version 2.2 to 2.4 problems **solved**
- Replies: 22
- Views: 11107
Re: Upgrade meteobridge version 2.2 to 2.4 problems **solved
No. Acurite bridge.
- Fri Jan 16, 2015 4:06 am
- Forum: Meteobridge Discussion
- Topic: Upgrade meteobridge version 2.2 to 2.4 problems **solved**
- Replies: 22
- Views: 11107
Re: Upgrade meteobridge version 2.2 to 2.4 problems **solved
I'm seeing the same periodic data logger failure with 2.4. Restarting the logger or rebooting the device fixes it, until the next time it happens.
In the system messages I see: "logger (14.01.2015 03:47:08): child process received timeout signal (14)."
In the system messages I see: "logger (14.01.2015 03:47:08): child process received timeout signal (14)."