MB Pro - Database is Locked

[Mattk]

What might be going on here?

logger (16.02.2016 15:40:14): DB cannot retrieve thb0hum_day (20 tries, 5504ms): database is locked
logger (16.02.2016 15:40:31): DB cannot retrieve thb0seapress_all (20 tries, 5504ms): database is locked
logger (16.02.2016 15:40:52): DB cannot retrieve wind0avgwind_month (20 tries, 5504ms): database is locked
logger (16.02.2016 15:41:08): DB cannot retrieve sol0rad_day (20 tries, 5512ms): database is locked
logger (16.02.2016 15:41:17): DB cannot retrieve thb9temp_day (20 tries, 5504ms): database is locked

[dr.diesel]

I'm seeing similar messages:

logger (15.02.2016 19:46:13): DB cannot retrieve thb0hum_day (20 tries, 5517ms): database is locked
logger (15.02.2016 19:46:36): DB cannot retrieve thb9press_all (20 tries, 5546ms): database is locked

Are you also having your WU and other networks services constantly crash and fail to update until rebooted?

[Mattk]

I haven't got to that stage with the Pro but do appear to have issues with data? When exporting data using the standard imp or iso templates so far am not getting any data, header, date, time, the rest blanks. Also getting a lot of "This page can not be displayed" dropouts which isn't occurring with the standard MB's.

I appear to be reading data, can push/output template data for a single point in time but still this morning showing 0% data storage usage? I would have thought this may have moved by now if I was logging data?

Indoor 9s 28.6% 41.6°C 29% 1006.1hPa (997.3hPa) 106.9°F 29% 29.71inHg (29.45inHg)
Rain 7s -60db rate 0.0mm/h rate 0.00in/h
Outdoor 1s -63db 21.0°C 94% (dew 20.0°C, heat 21.0°C) 69.8°F 94% (dew 68.0°F, heat 69.8°F)
Wind 1s -63db 0.0m/s (avg 0.0m/s) 304° NW 0.0mph (avg 0.0mph) 304° NW
Data #10 10 sec 12% system load 12% system load
Data #11 10 sec 12.6h uptime 12.6h uptime
Data #12 10 sec 0% data store usage 0% data store usage
Data #13 10 sec 57% RAM usage 57% RAM usage
Data #15 10 sec 51 processes 51 processes
Data #16 10 sec 1sec since last data 1sec since last data
Data #14 10 sec 2.17W power 2.17W power
Data #17 10 sec 5.34V voltage 5.34V voltage
Data #18 10 sec 0.41A current 0.41A current
Data #19 10 sec 4091.13kb tx data 4091.13kb tx data
Data #20 10 sec 2005422.49kb rx data 2005422.49kb rx data
System #9 10 sec 49.4°C 20% 1006.8hPa (998.0hPa) 120.9°F 20% 29.73inHg (29.47inHg)

[miraculon]

I am also seeing this message.

I also saw out of memory messages. Was 93%, dropped to 72% after reboot/update.

I rebooted to catch the latest FW, I'll monitor it for a while.

Greg

[dr.diesel]

Greg,

Have your weather net uploads quit working? Or was the out of memory causing a problem that you noticed?

Mine runs for about 1.5 days and all weather nets and services die, has happened how about 10 times.

[miraculon]

There was an error on the WD-Live Data Feed (clientraw) tab. I then looked at the "System" tab and could see the 93% RAM consumption. I am now down to 64% after the update/reboot. I also disabled the FTP-WD Live since I wasn't really using it for anything.
I didn't notice the other uploads and services, but my site was OK. Sorry, but I didn't check all of them.

Greg

[dr.diesel]

I was utilizing FTP upload as well, but trimmed items down to try and help prevent the crashing, so far no luck.

I'm down to Weather Underground, APRS and Triggered Display, but still very unreliable.

[plex]

Greg,

Have your weather net uploads quit working? Or was the out of memory causing a problem that you noticed?

Mine runs for about 1.5 days and all weather nets and services die, has happened how about 10 times.

I see same behavior here, but my weather nets dies after 1 hour or so

Started after upgrading to newest version, from old one dated 10th of feb.

[admin]

There has been a bug in the services stack. A new release is online.
Please reboot and things should go normal again.

If a database locked messages appears, that can be because of another
process also having access. If this occurs just here an there, no worry.
If it filly up the messages window, please chime in again.

[dr.diesel]

There has been a bug in the services stack. A new release is online.
Please reboot and things should go normal again.

The crash is still happening as of build 9199.

[plex]

There has been a bug in the services stack. A new release is online.
Please reboot and things should go normal again.

The crash is still happening as of build 9199.

Mine has been running for 1 day and 8 hours so far - no crash.

But I still see a few database errors

[dr.diesel]

If I look back through the graphs on WU, mine appears to crash about every ~34 hours.

[admin]

But I still see a few database errors

These time outs can happen as I decided to give up on retrieving a certain data after some time (5 secs) when DB is locked because another process is writing to it. To try endlessly will make fatal cyclic locks possible and will stop other important operations from going on. If 5 secs is right or it should be up to 10, I can't say. This might need some more experimentation.

When you fire clientraw updates, which have tons of variables to be taken out from the db, at short intervals probability of occasional timeouts will rise.

@dr.diesel: when you still have system stalls/crashes, which surprises me, please drop a mail to "info(at)meteobridge.com". I would be interested to login to your rig to understand what causes the problem. Systems here do run perfectly stable again.

[dr.diesel]

@dr.diesel: when you still have system stalls/crashes, which surprises me, please drop a mail to "info(at)meteobridge.com". I would be interested to login to your rig to understand what causes the problem. Systems here do run perfectly stable again.

I sent an email this morning to that address.

Thanks

[dr.diesel]

My apologies, I sent an email to info(at)smartbedded.com