meteohub.de

Hi,

I have a Meteobridge Pro with 2 weather stations connected. Connected are a Davis device with 3 ISS running and a Fine offset/Froggit/Ecowitt GW1000 with several sensors. So a lot of data comes in but all went smooth for almost the whole 2022 up to now. After 9 months there is 198 MB storage space left. As said this configuration worked fine since January. A few days ago I rebooted the system after running for more than 3 months. Further maybe to mention, although living in The Netherlands, I use UTC as time stamp because I want to measure 0-24 UTC.

Why the reboot? Well on the evening of September 8th suddenly my data wasn't stored anymore. The sensors were read, all uploads to Weather networks weren't stopped. But the data storage stopped at 18 UTC on that day. That I found out the next morning. After rebooting the Meteobridge Pro started to store the data again.

Now only 3 days later, yesterday evening, again at 18 UTC, the same problem. Again I found out next morning. After rebooting it started working again.

As said, according the system there is quite some data stored, but there is a calculated space for another 92 days. Further remarkable that the logging stopped at exact the same time. What might be the problem and what to do?

Best,

Ton

Yesterday evening it happened for the 4th time. It's now every day happening. Not always on the same time I see.

Two day ago, before the last failure I changed some settings to: store only mapped data and automated deletion after 180 days. This did not really release space on the storage but only the now remaining 192 MB is now sufficient for more days. And it didn't help as it crashed one day later again.

Is there is a problem with writing on that last left MB's? How can I free more space?

Some screen shots.

I don't think you don't have enough space for the database - 192 MB free storage on the internal storage is enough for quite some time.

TonvG wrote: ↑Mon Sep 12, 2022 7:16 pm The sensors were read, all uploads to Weather networks weren't stopped. But the data storage stopped at 18 UTC on that day.

From what/where do you tell that archiving data (writing into the database) has stopped ?
What are the related log messages ?
Can we see them ?

A screenshot of the latest log messages, but it hasn't crashed since last night. Except the usual warning for a humdity sensor that is not existing noting special as far as I can see. I don't know if it is possible to retrieve the log messages from before the reboot, but as I recall there was nothing special in it. If there is another crash, I will send the latest log message too.


Further the export file which I make every day misses data as another screenshot shows.


And the graphs from the last days are not ok. That's where I noticed first because I check them every day several times.

OK - the message log info (which disappears after a reboot as the log file with the same name is created at boot) would have been useful.
Next time it happens (fingers crossed that it won't ), take a copy of the log before you reboot the system.
It may give a hint why the logger stopped archiving ...
It also (rather rarely) occurs with my MB Pro and then it usually cannot write to a database table probably because it is locked and leaves a "--" in the minute recordings (History, minute data).
Also the station 9 data would be useful from the Min/May History - a system overload could be responsible for such a behaviour (wherever this overload may come from).
Looks that in your case it's not named station 9 but station 0 - the last 11 values in your min/max list

It happened again last night and now I cant make graphs either.

Long list of bad news:

The only good thing is that it keeps on uploading.
Raw data. The CPU overload is maybe caused by that I tried to retrieve data for the graphs. Usually it is far below 100 %.

The graph shows loss of signal each night. This looks very much like a battery problem, where in the absence of light the buffer battery does not provide enough juice.

"Database locked" errors can happen if you request data in short intervals like crazy. I have seen setups where users are going to upload every 10 seconds template strings with hundreds of variables. Especially the GW1000 with tons of cheap sensors supported in parallel are candidates for overstretching in that regard. As I don't know your setup I can't say if this is the case with your MB as well. But you might review your event definitions this in mind.

Regarding the th2 dew point issue. Is that a sensor that does not provide humidity or a humidity of zero?
If you give me a remote login I could inspect this interesting situation, I have not had so far.

I suppose that the cut text in the screenshot says "database is locked".
This usually occurs when another process works on the database and locks it.
Wondering what that would be ...
Do you have some regular imports running which may conflict with the data logger ?
Any other regular processes ("events") like backups ?
Also, your CPU load is quite high - when the CPU gets overloaded too much and too long, the system starts doing all types of weird things.
(but again this overload might come from the 100s/1000s of unsuccessful trials to write to or read from the locked database)

I must say that I had such "phenomena" (messages) too - but very rarely and a reboot would fix it. Maybe some bug which only shows in some special constellation...

That you cannot create/display graphs when the database is locked in just consequential. That's a collateral effect.

It would be good to know what other activities you are doing on the systems beyond the data logger archiving data and posting data to weather networks to see if it's a potential overload issue.

It looks as if some process had locked the database and didn't unlock it again. But which one and why ....
The reboot would remove this lock (until the missing unlock occurs again).

Maybe Boris can have a look into your system when you provide him the credentials for access ...

regarding your min/max history: (which may just be a 2nd-ary result of the locked database)
What is this th2(2) sensor of yours ? it seems to be calculated from your outdoor temperature/humidity sensor (or comes directly from your console - no idea how MB is connected to your Davis), and produces senseless values:
1% of RH outdoors and a dewpoint of -41.4°C .... - they don't look like correct values ...
what are your console values ? Do they match ?
Again, might just be some "dirt effect" caused by the locked database.

A sort of "dirty" workaround which comes to my mind would be running a schript each day at 18:00 which reboots the MB Pro.
Create a script e.g. reboot.sh with only one line in it: "reboot" without "", copy it into \\METEOBRIDGE\data\scripts and start it with an event from inside MB daily at 18:00 - and see what it gives ...

Hi,

This configuration has been running since January without any failure. Now every day it stops.

Every 10 minutes there is an upload to 2 weather nets.
One weather net (VWK) is programmed as an event with a quite long script.
Every minute there is an event for the display.
Every midnight two export files are produced from the running month, daily and hourly values.
And every new month a backup file is produced.

The weird humidity reading os from a Davis metal temperature sensor, without a humidity sensor.
Also on all ISS stations are not all sensors in use. ISS1 has the metal sensor and a rain gauge. ISS 3 has a a newer temp/hum sensor and second rain gauge. And ISS2 has only the wind sensor, at 10 meters height.
However in the system several sensors are seen that aren't there: wind stations at ISS1 and ISS3. A rain gauge at ISS2.

The GW1000 setup has 2 temp/hum sensors. A third sensor is only temp. There a 0 % humidity is created by the system. And a lightning detector.


Question: how to contact admin directly to give access?

TonvG wrote: ↑Thu Sep 15, 2022 7:41 pm Question: how to contact admin directly to give access?

send an email to info@meteobridge.com

but you can still try the workaround until your issue has been solved

To give some status ono this. The th2 bad data issue was worked around by a code change in the meantime. "database locked" might be a result of trying to access the database while a database backup is done, which is scheduled every hour in this case.

Sensor outage during night is still an open topic with an idea (no power during night) but not finally sorted out.

TonvG wrote: ↑Thu Sep 15, 2022 7:41 pmThe weird humidity reading os from a Davis metal temperature sensor, without a humidity sensor.
Also on all ISS stations are not all sensors in use. ISS1 has the metal sensor and a rain gauge. ISS 3 has a a newer temp/hum sensor and second rain gauge. And ISS2 has only the wind sensor, at 10 meters height.
However in the system several sensors are seen that aren't there: wind stations at ISS1 and ISS3. A rain gauge at ISS2.

ISS with not the standard sensors applied is not what Meteobridge expects or is made for. When connections are left open any data might be reported. Did you try to use a better fitting category like "extra temp/hum station" when just having a temp/hum probe installed to the pseudo ISS?

TonvG wrote: ↑Thu Sep 15, 2022 7:41 pm The GW1000 setup has 2 temp/hum sensors. A third sensor is only temp. There a 0 % humidity is created by the system. And a lightning detector.

This is solved with latest update

The Meteobridge seems to run fine again. There were no problems anymore in the last few days and the endless messages about bad sensors are gone.

ISS with not the standard sensors applied is not what Meteobridge expects or is made for. When connections are left open any data might be reported. Did you try to use a better fitting category like "extra temp/hum station" when just having a temp/hum probe installed to the pseudo ISS?

About the setup for reading out a Davis station. At the field sensor configuration you have to choose between an ISS station or a transmitter with only one sensor. In my configuration I have 3 transmitters, all having more than one sensor. So I can choose only ISS as possibility. It would be nice if you could define a transmitter with more than one sensor, so you can give in the exact configuration.

However thanks already for solving the problems so far!