meteohub.de

I have just fired up a recently acquired VP2 (model 6334au, an ISS with solar sensor and daytime fan aspiration) and a MB Pro Red - all without a console. On the system tab I am getting a continuous cycle of database error messages. Note the station does not have a UV sensor installed, just the solar sensor but their is a signal for the UV sensor. The live data tab is reporting signals for:

Rain 7s -85db
Solar 1m -86db
UV 34s -83db
Outdoor 10s -82db
Wind 5s -82db

A few of the error messages (about 18s per 'cycle'):

database (30.07.2017 17:39:06): cannot commit RAM (after 100 tries in 9028ms): c
database (30.07.2017 17:39:15): cannot insert into uv0index_day RAM (after 100 tries in 9133ms): database is locked
database (30.07.2017 17:39:15): rollback on insert forced (2) (hour): uv0index
database (30.07.2017 17:39:25): cannot commit RAM (after 100 tries in 9026ms): database is locked
database (30.07.2017 17:39:34): cannot insert into uv0index_day RAM (after 100 tries in 9140ms): database is locked
database (30.07.2017 17:39:34): rollback on insert forced (2) (hour): uv0index
database (30.07.2017 17:39:43): cannot commit RAM (after 100 tries in 9021ms): database is locked
database (30.07.2017 17:39:52): cannot insert into uv0index_day RAM (after 100 tries in 9161ms): database is locked
database (30.07.2017 17:39:52): rollback on insert forced (2) (hour): uv0index
database (30.07.2017 17:40:01): cannot commit RAM (after 100 tries in 9038ms): database is locked

Should I just ignore these or are they indicating a problem that I need to resolve?

After a bit more time, I got this sequence:

database (30.07.2017 17:51:32): process stopped.
test5m (30.07.2017 07:55:05): database daemon stalled, will be restarted now.
database (30.07.2017 17:55:05): process started.

In context:

database (30.07.2017 17:51:13): rollback on insert forced (2) (hour): uv0index
database (30.07.2017 17:51:22): cannot commit RAM (after 100 tries in 9057ms): database is locked
database (30.07.2017 17:51:32): cannot insert into uv0index_day RAM (after 100 tries in 9149ms): database is locked
database (30.07.2017 17:51:32): rollback on insert forced (2) (hour): uv0index
database (30.07.2017 17:51:32): process stopped.
test5m (30.07.2017 07:55:05): database daemon stalled, will be restarted now.
database (30.07.2017 17:55:05): process started.
database (30.07.2017 17:55:14): cannot insert into data10num_hour RAM (after 100 tries in 9119ms): database is locked
database (30.07.2017 17:55:14): rollback on sync forced (min): data10num
database (30.07.2017 17:55:24): cannot commit RAM (after 100 tries in 9028ms): database is locked
database (30.07.2017 17:55:33): cannot insert into rain0rate_day RAM (after 100 tries in 9129ms): database is locked
database (30.07.2017 17:55:33): rollback on insert forced (2) (hour): rain0rate
database (30.07.2017 17:55:42): cannot commit RAM (after 100 tries in 9063ms): database is locked
database (30.07.2017 17:55:52): cannot insert into rain0rate_day RAM (after 100 tries in 9143ms): database is locked
database (30.07.2017 17:55:52): rollback on insert forced (2) (hour): rain0rate
database (30.07.2017 17:56:01): cannot commit RAM (after 100 tries in 9031ms): database is locked
database (30.07.2017 17:56:10): cannot insert into rain0rate_day RAM (after 100 tries in 9167ms): database is locked
database (30.07.2017 17:56:10): rollback on insert forced (2) (hour): rain0rate

I think I have solved this (self-created) problem. I had turned SMB guest off. Resetting that appears to have resolved the database locked error.

A reboot does always fix it. These errors are happening isolated here and there, but unfortunately I cannot reproduce.