Page 1 of 1
Logger message **solved**
Posted: Tue Jul 26, 2016 1:17 pm
by SPW55
I have started to receive these logging details I have tried the check and repair and reboot but still get this messages ----logger (26.07.2016 00:53:01): DB cannot retrieve th0temp_min (0 tries, 2ms): attempt to write a readonly database
logger (26.07.2016 02:31:35): DB cannot retrieve wind0wind_min (0 tries, 2ms): attempt to write a readonly database
Re: Logger message
Posted: Thu Jul 28, 2016 11:10 am
by admin
Please ignore, this is a false error message I am just working on to get removed.
Nothing that should make you worry, not an indication of bad database.
As you see from the text a request for data is answered by a "read-only database error message", which is not logical as Meteobridge did try to read data. Looks like there is no data avail for the requested time range and this fires somehow the wrong exception. As said, nothing serious.
Re: Logger message **solved**
Posted: Thu Jul 28, 2016 11:20 am
by SPW55
Thank you for getting back to me I did check against history data and could see no problems with that, I was just unsure why this message appeared but now you have explained I have no problem thank you
Re: Logger message **solved**
Posted: Sat Jul 30, 2016 10:13 pm
by easyas12mb
I'm also receiving similar error messages.
logger (28.07.2016 02:50:03): DB cannot retrieve wind2dir_min (0 tries, 2ms): attempt to write a readonly database
logger (28.07.2016 10:30:00): DB cannot retrieve wind2dir_min (0 tries, 2ms): attempt to write a readonly database
logger (29.07.2016 01:54:01): DB cannot retrieve rain0total_min (0 tries, 2ms): attempt to write a readonly database
logger (29.07.2016 02:54:01): DB cannot retrieve rain0total_min (0 tries, 2ms): attempt to write a readonly database
logger (29.07.2016 17:00:01): DB cannot retrieve rain0total_min (0 tries, 2ms): attempt to write a readonly database
logger (30.07.2016 12:22:00): DB cannot retrieve wind2wind_min (0 tries, 2ms): attempt to write a readonly database
Re: Logger message **solved**
Posted: Sat Jul 30, 2016 11:58 pm
by admin
Please update to todays version that should have this fixed.
This is not caused by bad storage or something severe..