meteohub.de

Reverting to V5.5 seems to have solved the problem

The problem is still present with Ver 5.8, see last nights rainfall Screen Capture 007.jpg
Notice that 2.00am shows actual value from 1.00am (0mm), 3.00am shows value from 2.00am (0.2mm - happens to be correct), 4.00am shows value from 3.00am (0.2mm) the rest of the night looks ok because there is ...

Updated to 5.8 now, just have to wait for some more rain, shouldn't be too long.

Ever since the clocks went back on 31-march my rain0total-sumday value exported to my database has been incorrect, with the value on each hour showing the previous hours value, causing a sawtooth graph. Is anyone else having this problem?
(Meteobridge pro Version 5.6, Davis vantage vue)

email sent again

Problem is still happening ... Todays log
database (20.06.2018 08:00:07): cannot rollback (after 0 tries in 1ms): cannot rollback - no transaction is active
database (20.06.2018 08:00:07): cannot insert into data10num_hour (after 0 tries in 1ms): database or disk is full
database (20.06.2018 08:00 ...

email sent

another crash today
oled (03.06.2018 13:57:11): process started.
database (03.06.2018 14:59:21): process started.
wnetd (03.06.2018 14:59:24): process started.
system (03.06.2018 14:59:24): start of logging process initiated.
logger (03.06.2018 14:59:24): databases connected. Update interval 3600 ...

I've had the following crash a few times now, any idea what's up?

oled (03.05.2018 07:19:42): process started.
database (03.05.2018 23:31:01): process started.
wnetd (03.05.2018 23:31:03): process started.
system (03.05.2018 23:31:04): start of logging process initiated.
logger (03.05.2018 23:31 ...

and some more

database (03.01.2017 13:00:03): rollback on insert forced (min): data10num
database (03.01.2017 13:00:03): cannot rollback (after 0 tries in 1ms): cannot rollback - no transaction is active
database (03.01.2017 13:00:03): cannot insert into data10num_hour (after 0 tries in 1ms ...

It's failing several times per day now. a little feedback from the developer as to where the problem lies would be appreciated.

and again, dmesg attached
command: dmesg
-------------
[ 0.000000] Linux version 3.10.49 (boris@mars) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r44550) ) #685 Thu Dec 17 00:17:35 CET 2015
[ 0.000000] MyLoader: sysp=22a03bb2, boardp=aaaaaa22, parts=ab2abab2
[ 0.000000] bootconsole [early0 ...

and again...
logger (23.12.2016 16:40:03): databases connected. Update interval 3600 seconds.
logger (23.12.2016 16:40:03): Historical data loaded (0 records).
logger (23.12.2016 16:40:03): data logger (version 5.0t, build 10773) started.
logger (23.12.2016 16:40:03): error while doing bind (port ...

Yet another problem. I assume this is failed USB storage again.
logger (21.12.2016 19:40:05): databases connected. Update interval 3600 seconds.
logger (21.12.2016 19:40:05): Historical data loaded (0 records).
logger (21.12.2016 19:40:05): data logger (version 5.0t, build 10762) started.
logger ...

after running reliably for a period of a few months (apart from the odd zero value in the barometric pressure data) I had a total logging failure today
logger (08.12.2016 16:55:29): databases connected. Update interval 3600 seconds.
logger (08.12.2016 16:55:29): Historical data loaded (0 records ...