Author Topic: Database problems on Meteobridge Pro (Black)  (Read 720 times)

0 Members and 1 Guest are viewing this topic.

Offline wspronk

  • Member
  • *
  • Posts: 3
    • Weerstation Varsseveld
Database problems on Meteobridge Pro (Black)
« on: March 15, 2024, 05:49:46 AM »
Hello,
I do have troubles with my Meteobridge Pro and could do with any advise...
My system is set up on a Davis Vantage Pro 2 and I use the Meteobridge to collect the data from the weatherstation serially.
The Meteobridge is then making a database and then sending the actual data, graphics and other data to my weather page. (www.wspronk.nl)
Also the Meteobridge is providing data to various weather stations on the internet.

This all worked well for approx. 2 years but the last days the system sometimes stops and I get all kind of database errors.
This morning I did get the following errors in my logger:

database (15.03.2024 05:45:37): cannot insert into 'thb0temp_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 05:45:37): rollback on insert forced (1) (storemin): thb0temp
database (15.03.2024 05:45:37): cannot insert into 'thb0temp_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 05:45:37): rollback on insert forced (1) (storemin): thb0temp
database (15.03.2024 05:45:37): cannot insert into 'thb0temp_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 05:45:37): rollback on insert forced (1) (storemin): thb0temp
database (15.03.2024 05:45:37): cannot insert into 'thb0temp_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 05:45:37): rollback on insert forced (1) (storemin): thb0temp
database (15.03.2024 05:45:37): cannot insert into 'thb0temp_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 05:45:37): rollback on insert forced (1) (storemin): thb0temp
database (15.03.2024 05:45:38): cannot insert into 'thb0temp_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 05:45:38): rollback on insert forced (1) (storemin): thb0temp
system (15.03.2024 05:45:57): stop of logging process initiated.
logger (15.03.2024 05:45:57): parent process received termination signal (15).
logger (15.03.2024 05:45:57): child process received termination signal (15).
logger (15.03.2024 05:45:57): disconnect station 0 (Vantage): exit
logger (15.03.2024 05:45:58): disconnect station 9 (System Data): exit
database (15.03.2024 05:45:58): process terminated normally.
test5m (15.03.2024 04:46:00): USB storage remounted: /dev/sdb
database (15.03.2024 05:46:00): process started.
system (15.03.2024 05:46:00): start of logging process initiated.
logger (15.03.2024 05:46:01): databases connected. Update interval 3600 seconds.
logger (15.03.2024 05:46:01): data logger (version 5.4, build 14907) started.
logger (15.03.2024 05:46:02): connect station 0 (Vantage via USB serial).
logger (15.03.2024 05:46:02): connect station 9 (System Data via Plug-in).
logger (15.03.2024 05:46:02): station 0 (Vantage), wakeup sent.
logger (15.03.2024 05:46:05): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (15.03.2024 05:46:05): services paused.
logger (15.03.2024 05:46:06): station 0 (Vantage), no need to update console date/time.
logger (15.03.2024 05:46:06): station 0 (Vantage), setup script executed.
logger (15.03.2024 05:46:06): station 0 (Vantage), internal logger activated.
logger (15.03.2024 05:46:06): station 0 (Vantage), syncing.
logger (15.03.2024 05:46:16): station 0 (Vantage), gettime request sent.
logger (15.03.2024 05:46:16): station 0 (Vantage), no Vantage time offset.
logger (15.03.2024 05:46:16): station 0 (Vantage), eeprom request sent.
logger (15.03.2024 05:46:16): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (15.03.2024 05:46:16): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (15.03.2024 05:46:16): station 0 (Vantage), firmware version request sent.
logger (15.03.2024 05:46:16): station 0 (Vantage), firmware version 3.83 (supports LOOP2)
logger (15.03.2024 05:46:16): station 0 (Vantage), no reading of Vantage's internal logger.
logger (15.03.2024 05:46:21): sensors are now providing data.
logger (15.03.2024 05:46:21): services started.
database (15.03.2024 05:46:21): database sync done (43 tables, 137/971 writes).
export (15.03.2024 06:00:20): 15 lines of data written to file: NOAA-monthly-iso-202403-day.txt
export (15.03.2024 07:00:23): 15 lines of data written to file: NOAA-monthly-iso-202403-day.txt
export (15.03.2024 08:00:22): 15 lines of data written to file: NOAA-monthly-iso-202403-day.txt
export (15.03.2024 09:00:26): 15 lines of data written to file: NOAA-monthly-iso-202403-day.txt
logger (15.03.2024 09:22:54): DB cannot retrieve 'th0temp_day' (100 tries, 9035ms): database is locked (5)
logger (15.03.2024 09:23:03): DB cannot retrieve 'th0temp_day' (100 tries, 9012ms): database is locked (5)
logger (15.03.2024 09:23:12): DB cannot retrieve 'th0temp_day' (100 tries, 9028ms): database is locked (5)
database (15.03.2024 09:23:16): cannot insert into 'sol0evo_min'  (after 0 tries in 31119ms): disk I/O error (10)
database (15.03.2024 09:23:16): rollback on insert forced (1) (storemin): sol0evo
database (15.03.2024 09:23:17): cannot insert into 'sol0evo_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 09:23:17): rollback on insert forced (1) (storemin): sol0evo
database (15.03.2024 09:23:17): cannot insert into 'sol0evo_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 09:23:17): rollback on insert forced (1) (storemin): sol0evo
database (15.03.2024 09:23:17): cannot insert into 'sol0evo_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 09:23:17): rollback on insert forced (1) (storemin): sol0evo
database (15.03.2024 09:23:17): cannot insert into 'sol0evo_min'  (after 0 tries in 91ms): attempt to write a readonly database (8)
database (15.03.2024 09:23:17): rollback on insert forced (1) (storemin): sol0evo

As you can see there is an error in the database and for this reason the system restarts and after working then for approx. 4 hours another error is happening and a restart again happens.
This is already happening for the last few months.
But now also this week the system sometimes stops and no data is the sent out anymore and the database is also nu updated.
Then after a reboot the system is working again for a short while but the errors are still happening every few hours.

In a discussion with the supplier he suggested to replace the internal memory stick as this could be the cause of the problems.
He claimed that maybe the current memory stick was still of an older type and this caused problems in the past.
This was done and i did find that the original memory stick was identical to the new one and from an industrial type. My Meteobridge is only 3 years old.
The result was that there was no difference in behavior and the errors did still occur.

On this forum I did fine a topic "MB data logger stuck - attempt to write a readonly database **solved**" and they gave : Got it working again with "Rebuild on reboot".
Therefor I also did this and the database rebuild on reboot took approx. 3 hours and the system started again but still the same behavior.
Also went to an older software version (Now I use version 5.5) because also this was an topic on this forum but with no differences.

Any help in this matter would be highly appreciated.
I do not want to lose my weather site and I cannot believe that this problem is caused by the memory stick anymore.
Please help.......

Willy Spronk.
www.wspronk.nl


Offline Mattk

  • Forecaster
  • *****
  • Posts: 2177
Re: Database problems on Meteobridge Pro (Black)
« Reply #1 on: March 15, 2024, 06:22:23 AM »
What are the System box details on the System>Information tab?

Offline wspronk

  • Member
  • *
  • Posts: 3
    • Weerstation Varsseveld
Re: Database problems on Meteobridge Pro (Black)
« Reply #2 on: March 15, 2024, 06:34:37 AM »
Hello Mattk,

The System Box is giving me:

Platform:   Meteobridge PRO * 
RAM:   61500 kB total, 20048 kB free (67% used)
Storage ATP:   Internal 903 MB total, 56 MB free (94% used)
SW Version:   Meteobridge 5.5 (Mar 4 2023, build 14907), FW 1.4
Uptime:   1 days, 0 hours, 56 minutes    Buffer: 1 items (0%)
Power Data:   5.57V 500mA 2.79W  (Box Climate: 44.5C 18%)

The uptime is very low because I have worked on the system for a couple of day's already.

Hope this info helps.

Willy Spronk.

Offline wspronk

  • Member
  • *
  • Posts: 3
    • Weerstation Varsseveld
Re: Database problems on Meteobridge Pro (Black)
« Reply #3 on: March 15, 2024, 06:42:30 AM »
Hello,

At 11.00.53 I had another restart of the system and I like to share the error log for this.

database (15.03.2024 11:00:53): rollback on insert forced (1) (storemin): wind0wind
database (15.03.2024 11:00:53): cannot insert into 'wind0wind_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 11:00:53): rollback on insert forced (1) (storemin): wind0wind
database (15.03.2024 11:00:53): cannot insert into 'wind0wind_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (15.03.2024 11:00:53): rollback on insert forced (1) (storemin): wind0wind
export (15.03.2024 11:00:54): cannot open template file: /tmp/mnt/data/templates/NOAA-monthly-iso.exp
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:01): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:01): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
system (15.03.2024 11:01:02): stop of logging process initiated.
logger (15.03.2024 11:01:02): parent process received termination signal (15).
logger (15.03.2024 11:01:02): child process received termination signal (15).
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
logger (15.03.2024 11:01:02): disconnect station 0 (Vantage): exit
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:02): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:02): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
logger (15.03.2024 11:01:03): disconnect station 9 (System Data): exit
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): failed with step exist record on 'data10num_min' (after 0 retries in 1ms): disk I/O error (10)
database (15.03.2024 11:01:03): rollback on insert forced (1) (storemin): data10num
database (15.03.2024 11:01:03): process terminated normally.
test5m (15.03.2024 10:01:05): USB storage remounted: /dev/sdb
database (15.03.2024 11:01:05): process started.
system (15.03.2024 11:01:05): start of logging process initiated.
logger (15.03.2024 11:01:06): databases connected. Update interval 3600 seconds.
logger (15.03.2024 11:01:06): data logger (version 5.4, build 14907) started.
logger (15.03.2024 11:01:07): connect station 0 (Vantage via USB serial).
logger (15.03.2024 11:01:07): connect station 9 (System Data via Plug-in).
logger (15.03.2024 11:01:07): station 0 (Vantage), wakeup sent.
logger (15.03.2024 11:01:10): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (15.03.2024 11:01:10): services paused.
logger (15.03.2024 11:01:11): station 0 (Vantage), no need to update console date/time.
logger (15.03.2024 11:01:11): station 0 (Vantage), setup script executed.
logger (15.03.2024 11:01:11): station 0 (Vantage), internal logger activated.
logger (15.03.2024 11:01:11): station 0 (Vantage), syncing.
logger (15.03.2024 11:01:21): station 0 (Vantage), gettime request sent.
logger (15.03.2024 11:01:21): station 0 (Vantage), no Vantage time offset.
logger (15.03.2024 11:01:21): station 0 (Vantage), eeprom request sent.
logger (15.03.2024 11:01:21): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (15.03.2024 11:01:21): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (15.03.2024 11:01:21): station 0 (Vantage), firmware version request sent.
logger (15.03.2024 11:01:21): station 0 (Vantage), firmware version 3.83 (supports LOOP2)
logger (15.03.2024 11:01:21): station 0 (Vantage), no reading of Vantage's internal logger.
database (15.03.2024 11:01:25): database sync done (43 tables, 91/1181 writes).
logger (15.03.2024 11:01:25): sensors are now providing data.
logger (15.03.2024 11:01:25): services started.

And again the system restarted due to database problems.

Willy Spronk.

Offline ConligWX

  • Forecaster
  • *****
  • Posts: 856
  • #conligwx
    • conligwx.org
Re: Database problems on Meteobridge Pro (Black)
« Reply #4 on: March 15, 2024, 06:54:22 AM »
Probably best to contact Boris directly.  info(at)smartbedded.com

though disk i/o errors could be a sdcard failing perhaps?
Regards Simon
Davis Vantage Pro2 Plus (6162UK) Daytime FARS WeatherLink Live AirLink PurpleAir PA-II-SD CumulusMX


Offline wsNoordbergum

  • Contributor
  • ***
  • Posts: 139
    • wsNoordbergum
Re: Database problems on Meteobridge Pro (Black)
« Reply #5 on: April 25, 2024, 05:53:47 PM »
I had the same problem and after a reconstruct of the database my minute data was gone
I was planning on migrating from a Nano SD to a Pro 2 black
Boris has solved the issue for me remotely and it was fine
I had trouble importing the database to my Pro 2 black
But in the end I have returned the unit because it can not transfer data through port 22222 as the nano can because it is a stand alone unit and not connected to a console like a regular meteobridge or a nano SD is
I use the Nano SD also in combination with CumulusMX on a raspberry Pi so I need the 22222 pass through to feed my CumulusMX program
CumulusMX is my main upload source to my website but I do also use the meteobridge graphs generating capabilities

To be short, after importing the database the first time I did not see the min data of the day in the min/max tab, just --

SD card was fine

And yes the rebuilt process took several hours to complete as it has data in it dating back to 2018
It took quite some time to get it right but thanks to Boris it was working

So contact Boris via the meteobridge forum, it could be a bug since I had the same problem
« Last Edit: April 25, 2024, 06:01:10 PM by wsNoordbergum »
Davis Vantage Pro 2 UV/Solar
Meteobridge nano SD
Ecowitt WS90 WH40 WH31 WH57 GW2000 HP2550_c
CumulusMX/raspberry Pi 4b

Offline Mattk

  • Forecaster
  • *****
  • Posts: 2177
Re: Database problems on Meteobridge Pro (Black)
« Reply #6 on: April 25, 2024, 06:40:50 PM »
Would be looking at the storage capacity? On March 15 there was 94% used, only 56mb free, that's not good.   

Offline wsNoordbergum

  • Contributor
  • ***
  • Posts: 139
    • wsNoordbergum
Re: Database problems on Meteobridge Pro (Black)
« Reply #7 on: April 25, 2024, 06:45:06 PM »
I did not have low storage as far as I can remember
But it is sure not a good thing to be that low on storage
I can recall massive processor load .....

I'm sure Boris can help
Davis Vantage Pro 2 UV/Solar
Meteobridge nano SD
Ecowitt WS90 WH40 WH31 WH57 GW2000 HP2550_c
CumulusMX/raspberry Pi 4b

Offline Mattk

  • Forecaster
  • *****
  • Posts: 2177
Re: Database problems on Meteobridge Pro (Black)
« Reply #8 on: April 25, 2024, 08:13:01 PM »
I did not have low storage as far as I can remember
But it is sure not a good thing to be that low on storage
I can recall massive processor load .....

I'm sure Boris can help

Sorry was responding to the original poster and the March 15 post

 

anything