meteohub.de

Meteohub Forum
https://forum.meteohub.de/

100% data store usage

https://forum.meteohub.de/viewtopic.php?t=15851

Page 1 of 1

100% data store usage

Posted: Mon Aug 02, 2021 6:15 pm
by Rennpferd
Hello experts,

I noticed that my website (Meteotemplate) shows implausible rain data. This can also be seen under "Live-Data".


Min Max Data 20210802-094204.png
Min Max Data 20210802-094204.png (189.44 KiB) Viewed 2078 times

Sensor Data 20210802-093847.png
Sensor Data 20210802-093847.png (140.79 KiB) Viewed 2078 times

System 20210801-211043.png
System 20210801-211043.png (127.96 KiB) Viewed 2078 times


In the logging page you can see messages that the "100% data store usage" is the reason and that other sensors cannot work properly either.


Log 20210802-094549.png
Log 20210802-094549.png (217 KiB) Viewed 2078 times


A template for a custom chart has also disappeared!

I am constantly sending health data to another IT system and there I see that one day the memory is suddenly from 13% to 100% full. Shortly before that, this was the case for a short time. What happened? I have set MB so that the latest version is always installed on a reboot.


health data 20210802-093654.png
health data 20210802-093654.png (219.62 KiB) Viewed 2078 times


I've restarted MB a few times in the last few days, maybe it was the 5.2 update? Switching back to version 5.1 didn't solve the problem.

It can't be the database with the weather data. Who has an idea who is using the memory?

Re: 100% data store usage

Posted: Mon Aug 02, 2021 9:41 pm
by Gyvate
How large is your database ?
log in via SSH (puTTY) into your MB Pro and check (user + password are the same as for the Web UI)
enter
# df -h
you should see something like below
root@MeteoBridge:~# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 9.1M 3.3M 5.8M 36% /
/dev/root 5.5M 5.5M 0 100% /rom
tmpfs 25.0M 15.2M 9.8M 61% /tmp
/dev/mtdblock5 9.1M 3.3M 5.8M 36% /overlay
overlayfs:/overlay 9.1M 3.3M 5.8M 36% /
tmpfs 512.0K 4.0K 508.0K 1% /dev
/dev/sdb 927.9M 808.9M 55.0M 94% /tmp/mnt

what's the size of your /dev/sdb ? how much used, how much available.
That's your internal flash memory storage of the MB Pro where the database resides
then
# cd /tmp/mnt
# ls -l
root@MeteoBridge:/tmp/mnt# ls -l
-rwxr--r-- 1 root root 257 Oct 4 2020 0-don't touch dbase and dbase.ram nor data dir.txt
drwxr-xr-x 2 root root 4096 Apr 3 16:28 USB
drwxr-xr-x 10 root root 4096 Jun 29 14:34 data
-rwxr-xr-x 1 root root 695577600 Aug 2 21:26 dbase
-rw-r--r-- 1 root root 818176 Jun 29 14:57 dbase.old
-rw-r--r-- 1 root root 7707648 Aug 2 20:05 dbase.ram
-rw-r--r-- 1 root root 24 Aug 2 02:00 growth
-rw-r--r-- 1 root root 5727623 Jul 20 22:18 image.tgz
drwxr-xr-x 2 root root 4096 Dec 17 2015 lost+found
-rw-r--r-- 1 root root 1167 Aug 2 21:00 nonzerotime.tgz
-rw-r--r-- 1 root root 8388608 Feb 13 08:53 swap
-rw-r--r-- 1 root root 0 Aug 2 21:15 wrtest

here you see what all uses the internal storage (mounted into /tmp/mnt)
there should be a few files starting with dbase
what's their size altogether ?
the whole number you should get by du -sh in the /tmp/mnt directory:
root@MeteoBridge:/tmp/mnt# du -sh
807.8M .

in the example case there are only 55 MB free - not very much.

You could try using an external and bigger e.g. 4/8/16 GB USB stick for the database.
- In the administration tab at Database Media choose USB stick on front panel (can also be back panel)
- copy your last database backup on the USB stick and rename it from dbase-202108012021 (example) to just dbase
(if you don't have a backup :shock: , copy the existing database from /tmp/mnt onto the USB stick)
- plug in the USB stick into the port you have selected under Database Media
- reboot
MB should now use the database on the USB stick
the "old" database will remain in /mnt/tmp
check the logging if you still have an out-of-memory issue.

If that solves your issue and you need to continue using the external USB stick for a longer time, it's advisable to exchange the standard USB by a stick with industrial flash memory in order not to die early due to too many I/Os

Re: 100% data store usage

Posted: Mon Aug 02, 2021 11:01 pm
by Rennpferd
Thanks for the help, I get that displayed:

Code: Select all

BusyBox v1.22.1 (2015-04-26 23:49:31 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 BARRIER BREAKER (Barrier Breaker, r44550)
 -----------------------------------------------------
root@MeteoBridge:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                    9.1M      3.3M      5.8M  36% /
/dev/root                 5.5M      5.5M         0 100% /rom
tmpfs                    25.0M      8.2M     16.8M  33% /tmp
/dev/mtdblock5            9.1M      3.3M      5.8M  36% /overlay
overlayfs:/overlay        9.1M      3.3M      5.8M  36% /
tmpfs                   512.0K    512.0K         0 100% /dev
tmpfs                   512.0K    512.0K         0 100% /tmp/mnt
tmpfs                   512.0K    512.0K         0 100% /tmp/mnt
root@MeteoBridge:~# cd /tmp/mnt
root@MeteoBridge:/tmp/mnt# ls -l
drwxr-xr-x    3 root     root            60 Jan  1  1970 bus
crw-r--r--    1 root     root        5,   1 Jan  1  1970 console
crw-r--r--    1 root     root       10,  63 Jan  1  1970 cpu_dma_latency
drwxr-xr-x    8 root     root           160 Aug  2 14:01 data
prw-r--r--    1 root     root             0 Aug  2 22:41 database
-rw-r--r--    1 root     root             0 Aug  2 14:02 dbase
crw-rw-rw-    1 root     root        1,   7 Jan  1  1970 full
crw-r--r--    1 root     root       89,   0 Aug  2 13:59 i2c-0
-rw-r--r--    1 root     root        524288 Aug  2 14:00 image.tgz
crw-r--r--    1 root     root        1,  11 Jan  1  1970 kmsg
prw-r--r--    1 root     root             0 Aug  2 22:41 ledburst
srw-rw-rw-    1 root     root             0 Aug  2 14:00 log
crw-r--r--    1 root     root        1,   1 Jan  1  1970 mem
prw-r--r--    1 root     root             0 Aug  2 22:41 meteobridge
crw-r--r--    1 root     root       90,   0 Jan  1  1970 mtd0
crw-r--r--    1 root     root       90,   1 Jan  1  1970 mtd0ro
crw-r--r--    1 root     root       90,   2 Jan  1  1970 mtd1
crw-r--r--    1 root     root       90,   3 Jan  1  1970 mtd1ro
crw-r--r--    1 root     root       90,   4 Jan  1  1970 mtd2
crw-r--r--    1 root     root       90,   5 Jan  1  1970 mtd2ro
crw-r--r--    1 root     root       90,   6 Jan  1  1970 mtd3
crw-r--r--    1 root     root       90,   7 Jan  1  1970 mtd3ro
crw-r--r--    1 root     root       90,   8 Jan  1  1970 mtd4
crw-r--r--    1 root     root       90,   9 Jan  1  1970 mtd4ro
crw-r--r--    1 root     root       90,  10 Jan  1  1970 mtd5
crw-r--r--    1 root     root       90,  11 Jan  1  1970 mtd5ro
crw-r--r--    1 root     root       90,  12 Jan  1  1970 mtd6
crw-r--r--    1 root     root       90,  13 Jan  1  1970 mtd6ro
brw-r--r--    1 root     root       31,   0 Jan  1  1970 mtdblock0
brw-r--r--    1 root     root       31,   1 Jan  1  1970 mtdblock1
brw-r--r--    1 root     root       31,   2 Jan  1  1970 mtdblock2
brw-r--r--    1 root     root       31,   3 Jan  1  1970 mtdblock3
brw-r--r--    1 root     root       31,   4 Jan  1  1970 mtdblock4
brw-r--r--    1 root     root       31,   5 Jan  1  1970 mtdblock5
brw-r--r--    1 root     root       31,   6 Jan  1  1970 mtdblock6
crw-r--r--    1 root     root       10,  62 Jan  1  1970 network_latency
crw-r--r--    1 root     root       10,  61 Jan  1  1970 network_throughput
-rw-r--r--    1 root     root             0 Aug  2 22:32 nonzerotime.tgz
crw-rw-rw-    1 root     root        1,   3 Jan  1  1970 null
prw-r--r--    1 root     root             0 Aug  2 22:40 oled
crw-r--r--    1 root     root        1,   4 Jan  1  1970 port
crw-r--r--    1 root     root      108,   0 Aug  2 13:58 ppp
crw-rw-rw-    1 root     root        5,   2 Aug  2 22:41 ptmx
drwxr-xr-x    2 root     root            40 Jan  1  1970 pts
crw-r--r--    1 root     root        1,   8 Jan  1  1970 random
brw-r--r--    1 root     root        8,   0 Aug  2 13:59 sda
brw-r--r--    1 root     root        8,   1 Aug  2 13:59 sda1
crw-r--r--    1 root     root       21,   0 Aug  2 13:59 sg0
drwxr-xr-x    2 root     root            40 Jan  1  1970 shm
-rw-r--r--    1 root     root             0 Aug  2 14:06 stdout
-rw-r--r--    1 root     root             0 Aug  2 14:00 swap
crw-r--r--    1 root     root        5,   0 Jan  1  1970 tty
crw-r--r--    1 root     root      254,   0 Jan  1  1970 ttyATH0
lrwxrwxrwx    1 root     root            12 Aug  2 13:59 ttyMH -> /dev/ttyUSB0
lrwxrwxrwx    1 root     root            12 Aug  2 13:59 ttyMH113 -> /dev/ttyUSB0
crw-r--r--    1 root     root        4,  64 Jan  1  1970 ttyS0
crw-r--r--    1 root     root      188,   0 Aug  2 14:02 ttyUSB0
crw-r--r--    1 root     root        1,   9 Jan  1  1970 urandom
crw-r--r--    1 root     root       10, 130 Jan  1  1970 watchdog
-rw-r--r--    1 root     root             0 Aug  2 22:25 wrtest
crw-rw-rw-    1 root     root        1,   5 Jan  1  1970 zero
root@MeteoBridge:/tmp/mnt# du -sh
512.0K  .
root@MeteoBridge:/tmp/mnt#

Re: 100% data store usage

Posted: Tue Aug 03, 2021 12:48 am
by Gyvate
Looks rather strange ...
the df -h and ls -l of /tmp/mnt do not show any mounted internal storage
the System info should have a line which says
storage ATP: ................ that would be the internal flash memory
MB-Pro_system-info.JPG
MB-Pro_system-info.JPG (38.71 KiB) Viewed 2049 times
It doesn't show in your case -hence no internal storage mounted ...
and the database size is 0 (then the message in the system log is correct, DBsize 0 and no storage space

If after a power cycle (=shutdown, switch on again and start again with option "get newest on reboot" active in version control (system - administration - save and apply) (select before shutdown :wink: ), nothing changes in the system information view, I'd say the device is defective.
(or the system setup script doesn't work properly).

the ls -l indicates that there is a special device (sda) which has 2 partitions (sda and sda1) - that's usually a USB stick or a hard disk.
Do you have a USB stick plugged in ? If so, that would be it.
the internal storage usually shows as sdb (when an external USB is plugged in, that would be sda, sda1)
ls /dev/sd* -l would show all special devices (usually "disks", USB, HDD, SSD, ...) which start with a "sd"

in my case it is
root@MeteoBridge:/tmp/mnt# ls /dev/sd* -l
brw-r--r-- 1 root root 8, 0 Jul 20 22:17 /dev/sda
brw-r--r-- 1 root root 8, 1 Jul 20 22:17 /dev/sda1
brw-r--r-- 1 root root 8, 16 Jul 20 22:18 /dev/sdb
my external USB stick for backup (sda1) and the internal storage (sdb) - in your case the sdb is probably missing.

If the ls /dev/sd* -l shows for you also the sdb device, then probably the mounting of the internal storage failed - if it's not there at all, the internal storage wasn't recognized.
How old is your MB Pro (still warranty ?) ?

Re: 100% data store usage

Posted: Tue Aug 03, 2021 11:49 pm
by Rennpferd
My meteoBridge PRO red is from November 2019. I have a SanDisk 16GB USB stick in the front for data backups.

I did it as suggested. At first it was unsuccessful. Then I disconnected the power supply for 1h and restarted. The Storage ATP is now visible again.
20210803-111806.png
20210803-111806.png (113.11 KiB) Viewed 2027 times
Is it maybe a hardware error that has to do with the temperature in the case?

This is what it looks like in the file system:

Code: Select all

BusyBox v1.22.1 (2015-04-26 23:49:31 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
 
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 BARRIER BREAKER (Barrier Breaker, r44550)
 -----------------------------------------------------
root@MeteoBridge:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                    9.1M      3.4M      5.8M  37% /
/dev/root                 5.5M      5.5M         0 100% /rom
tmpfs                    25.0M     14.2M     10.8M  57% /tmp
/dev/mtdblock5            9.1M      3.4M      5.8M  37% /overlay
overlayfs:/overlay        9.1M      3.4M      5.8M  37% /
tmpfs                   512.0K      4.0K    508.0K   1% /dev
/dev/sda1                14.9G      3.6G     11.3G  24% /tmp/backup
/dev/sdc                927.9M    116.8M    747.2M  14% /tmp/mnt
root@MeteoBridge:~# cd /tmp/mnt
root@MeteoBridge:/tmp/mnt# ls -l
drwxr-xr-x    8 root     root          4096 Jan  2  2020 data
-rw-r--r--    1 root     root      75650048 Aug  3 11:22 dbase
-rw-r--r--    1 root     root             0 May  1 19:54 dbase.err
-rw-r--r--    1 root     root      18228224 May  1 19:18 dbase.old
-rw-r--r--    1 root     root       3588096 Aug  3 09:32 dbase.ram
-rw-r--r--    1 root     root       8357172 May  1 19:54 dbase.sql.gz
-rw-r--r--    1 root     root            24 Jul 30 02:00 growth
-rw-r--r--    1 root     root       5727652 Aug  3 09:00 image.tgz
drwx------    2 root     root         16384 Dec 17  2015 lost+found
-rw-r--r--    1 root     root           564 Aug  3 10:04 nonzerotime.tgz
-rw-r--r--    1 root     root       8388608 Dec 30  2020 swap
-rw-r--r--    1 root     root             0 Aug  3 11:01 wrtest
root@MeteoBridge:/tmp/mnt# du -sh
115.6M  .
root@MeteoBridge:/tmp/mnt#

Today I waited to see if everything worked again. In the meantime, during the analysis, it was not possible to write to the database, only read it. I've tried a few things, but it's still buggy.

After about 4 hours the Storage ATP has disappeared again. If I switch it off with “Power Off” and switch it on again, the Storage ATP appears again. But not after a “reboot”.

Is the database now defective and causing further errors? Since the MB has now run with the error for a few days, plausible entries are missing in the database. Is there a way to repair it automatically?

When I try to restore a backup (with option "Delete database before restore"), the memory disappears again and there is an error:

dbrestore (03.08.2021 23:26:51): file to restore: /tmp/backup/dbase-202108031842 (72.4M)
dbrestore (03.08.2021 23:26:54): not enough free space to restore database

Code: Select all

oled (03.08.2021 21:11:30): process started.
dbrepair (03.08.2021 23:17:16): database size is 72.5M.
dbrepair (03.08.2021 23:17:16): test integrity of database.
dbrepair (03.08.2021 23:17:17): RAM database integrity is fine, nothing to do.
dbrepair (03.08.2021 23:18:50): database integrity is fine, but rebuild is forced.
dbrepair (03.08.2021 23:18:51): database rebuild started.
dbrepair (03.08.2021 23:26:27): dumpfile generation failed.
database (03.08.2021 23:26:27): process started.
database (03.08.2021 23:26:27): Content of RAM database restored.
database (03.08.2021 23:26:27): database sync done (0 tables, 0/0 writes).
database (03.08.2021 23:26:29): process terminated normally.
wnetd  (03.08.2021 23:26:30): process started.
system (03.08.2021 23:26:30): start of logging process initiated.
wnetd  (03.08.2021 23:26:30): send data thread started (pid:4205 tid:4206)
database (03.08.2021 23:26:30): process started.
database (03.08.2021 23:26:30): database sync done (0 tables, 0/0 writes).
system (03.08.2021 23:26:30): stop of logging process initiated.
logger (03.08.2021 23:26:31): databases connected. Update interval 3600 seconds.
logger (03.08.2021 23:26:31): data logger (version 5.1e, build 14478) started.
logger (03.08.2021 23:26:32): connect station 0 (Meteostick Vantage via USB serial).
logger (03.08.2021 23:26:32): connect station 9 (System Data via Plug-in).
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), transmitter 1 registered as ISS
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), debug off
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), verbose off
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), filter on
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), rx threshold set to -85db
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), listening to transmitter 1
logger (03.08.2021 23:26:33): station 0 (Meteostick Vantage), bandwidth narrow
logger (03.08.2021 23:26:34): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (03.08.2021 23:26:34): station 0 (Meteostick Vantage), frequency band 868MHz (EU)
logger (03.08.2021 23:26:35): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (03.08.2021 23:26:35): services paused.
dbrestore (03.08.2021 23:26:51): file to restore: /tmp/backup/dbase-202108031842 (72.4M)
dbrestore (03.08.2021 23:26:54): not enough free space to restore database
logger (03.08.2021 23:27:35): sensors are now providing data.
logger (03.08.2021 23:27:35): services started.
system (03.08.2021 23:30:32): stop of logging process initiated.
logger (03.08.2021 23:30:32): parent process received termination signal (15).
logger (03.08.2021 23:30:32): child process received termination signal (15).
logger (03.08.2021 23:30:32): disconnect station 0 (Meteostick Vantage): exit
logger (03.08.2021 23:30:32): disconnect station 9 (System Data): exit
database (03.08.2021 23:30:33): process terminated normally.
system (03.08.2021 23:30:34): start of logging process initiated.
test5m (03.08.2021 23:30:34): USB storage remounted: /dev/sdc
database (03.08.2021 23:30:34): process started.
system (03.08.2021 23:30:35): start of logging process initiated.
logger (03.08.2021 23:30:35): databases connected. Update interval 3600 seconds.
logger (03.08.2021 23:30:35): data logger (version 5.1e, build 14478) started.
logger (03.08.2021 23:30:36): connect station 0 (Meteostick Vantage via USB serial).
logger (03.08.2021 23:30:36): connect station 9 (System Data via Plug-in).
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), transmitter 1 registered as ISS
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), debug off
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), verbose off
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), filter on
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), rx threshold set to -85db
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), listening to transmitter 1
logger (03.08.2021 23:30:38): station 0 (Meteostick Vantage), bandwidth narrow
logger (03.08.2021 23:30:39): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (03.08.2021 23:30:39): station 0 (Meteostick Vantage), frequency band 868MHz (EU)
logger (03.08.2021 23:30:40): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (03.08.2021 23:30:40): services paused.
database (03.08.2021 23:30:57): database sync done (46 tables, 180/230 writes).

Here i try a rebuild:


.
.
.
dbrepair (03.08.2021 23:59:14): dumpfile generation failed.
.
.
.
logger (04.08.2021 00:08:15): DB cannot retrieve 'rain0total_day' (100 tries, 9089ms): database is locked (5)
logger (04.08.2021 00:08:26): DB cannot retrieve 'rain0total_day' (100 tries, 9107ms): database is locked (5)
database (04.08.2021 00:08:33): cannot insert into 'data20num_min' (after 0 tries in 30523ms): disk I/O error (10)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
.
.
.

Code: Select all


oled (03.08.2021 21:49:42): process started.
dbrepair (03.08.2021 23:51:44): database size is 72.5M.
dbrepair (03.08.2021 23:51:44): test integrity of database.
dbrepair (03.08.2021 23:51:45): RAM database integrity is fine, nothing to do.
dbrepair (03.08.2021 23:53:14): database integrity is fine, but rebuild is forced.
dbrepair (03.08.2021 23:53:14): database rebuild started.
dbrepair (03.08.2021 23:59:14): dumpfile generation failed.
database (03.08.2021 23:59:17): process started.
database (03.08.2021 23:59:17): Content of RAM database restored.
database (03.08.2021 23:59:17): database sync done (0 tables, 0/0 writes).
wnetd  (03.08.2021 23:59:19): process started.
system (03.08.2021 23:59:19): start of logging process initiated.
wnetd  (03.08.2021 23:59:19): send data thread started (pid:4019 tid:4020)
logger (03.08.2021 23:59:20): databases connected. Update interval 3600 seconds.
logger (03.08.2021 23:59:20): data logger (version 5.1e, build 14478) started.
logger (03.08.2021 23:59:21): connect station 0 (Meteostick Vantage via USB serial).
logger (03.08.2021 23:59:21): connect station 9 (System Data via Plug-in).
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), transmitter 1 registered as ISS
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), debug off
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), verbose off
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), filter on
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), rx threshold set to -85db
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), listening to transmitter 1
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), bandwidth narrow
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (03.08.2021 23:59:23): station 0 (Meteostick Vantage), frequency band 868MHz (EU)
logger (03.08.2021 23:59:24): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (03.08.2021 23:59:24): services paused.
logger (04.08.2021 00:00:24): sensors are now providing data.
logger (04.08.2021 00:00:24): services started.
system (03.08.2021 22:01:28): stop of logging process initiated.
logger (04.08.2021 00:01:28): parent process received termination signal (15).
logger (04.08.2021 00:01:28): child process received termination signal (15).
logger (04.08.2021 00:01:28): disconnect station 0 (Meteostick Vantage): exit
logger (04.08.2021 00:01:28): disconnect station 9 (System Data): exit
database (04.08.2021 00:01:29): process terminated normally.
test5m (03.08.2021 22:01:30): USB storage remounted: /dev/sdc
system (03.08.2021 22:01:31): start of logging process initiated.
database (04.08.2021 00:01:31): process started.
logger (04.08.2021 00:01:31): databases connected. Update interval 3600 seconds.
logger (04.08.2021 00:01:31): data logger (version 5.1e, build 14478) started.
logger (04.08.2021 00:01:33): connect station 0 (Meteostick Vantage via USB serial).
logger (04.08.2021 00:01:33): connect station 9 (System Data via Plug-in).
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), transmitter 1 registered as ISS
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), debug off
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), verbose off
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), filter on
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), rx threshold set to -85db
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), listening to transmitter 1
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), bandwidth narrow
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (04.08.2021 00:01:35): station 0 (Meteostick Vantage), frequency band 868MHz (EU)
logger (04.08.2021 00:01:36): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (04.08.2021 00:01:36): services paused.
database (04.08.2021 00:01:48): database sync done (46 tables, 224/264 writes).
logger (04.08.2021 00:02:36): sensors are now providing data.
logger (04.08.2021 00:02:36): services started.
logger (04.08.2021 00:08:15): DB cannot retrieve 'rain0total_day' (100 tries, 9089ms): database is locked (5)
logger (04.08.2021 00:08:26): DB cannot retrieve 'rain0total_day' (100 tries, 9107ms): database is locked (5)
database (04.08.2021 00:08:33): cannot insert into 'data20num_min'  (after 0 tries in 30523ms): disk I/O error (10)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:33): cannot insert into 'data20num_min'  (after 0 tries in 22ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:33): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:33): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:33): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:33): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:33): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:33): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 22ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:34): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:34): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:35): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:35): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 11ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:36): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:36): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:37): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:37): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:38): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:38): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:39): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:39): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:39): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:39): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:39): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:39): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:39): cannot insert into 'data20num_min'  (after 0 tries in 31ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:39): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:39): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:39): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:39): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:39): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:40): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:40): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:40): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:40): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:40): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:40): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:40): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:40): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:40): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:40): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:41): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:41): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:41): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:41): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:41): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:41): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:41): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:41): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:41): cannot insert into 'data20num_min'  (after 0 tries in 21ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:41): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:41): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:41): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:42): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:42): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:42): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:42): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:42): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:42): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:42): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:42): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:42): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:42): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:43): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:43): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:43): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:43): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:43): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:43): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:43): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:43): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:43): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:43): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:43): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:43): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:44): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:44): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:44): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:44): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:44): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:44): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:44): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:44): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:44): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:44): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:44): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:44): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:45): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:45): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:45): cannot insert into 'data20num_min'  (after 0 tries in 21ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:45): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:45): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:45): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:45): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:45): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:45): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:45): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:46): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:46): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:08:46): cannot insert into 'data20num_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:08:46): rollback on insert forced (1) (storemin): data20num
database (04.08.2021 00:09:00): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:00): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:00): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:00): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:00): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:00): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:00): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:00): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:01): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:01): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:02): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:02): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:02): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:02): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:02): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:02): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:02): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:02): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:02): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:02): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:02): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:02): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:02): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:02): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:03): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:03): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:04): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:04): rollback on insert forced (1) (storemin): rain0rate
database (04.08.2021 00:09:05): cannot insert into 'rain0rate_min'  (after 0 tries in 1ms): attempt to write a readonly database (8)
database (04.08.2021 00:09:05): rollback on insert forced (1) (storemin): rain0rate

Re: 100% data store usage

Posted: Wed Aug 04, 2021 1:54 am
by Gyvate
what you can do is:
instead of using the "delete before repair" option we will do this manually
see that the internal storage appears again. (shut down, wait, whatever is necessary)
then start MB and connect via SSH and go to /tmp/mnt and delete the database:
# cd /tmp/mnt
/tmp/mnt # rm dbase*
insert the USB stick
create a mount point
/tmp/mnt # mkdir /tmp/mnt/data/USB (this only needs to be done once, it will remain)
now mount the USB stick with the backup on it
/tmp/mnt # mount /dev/sda1 /tmp/mnt/data/USB
copy the backup into internal memory
/tmp/mnt # cp /tmp/mnt/data/USB/dbase-202108031843 /tmp/mnt/
rename the backup to dbase
/tmp/mnt # mv dbase-202108031843 dbase

I have taken the backup name from your earlier post - please verify the name of the database backup which you have on the USB stick and which you want to restore.

then reboot the MB from the WebUI
MB should recognize the database and build a new RAM database - and should work normally again
maybe place the MB box on some metal object for the heat to dissipate better -
possibly overheating was the reason for "forgetting" its internal storage
my MB Pro(s) are also getting pretty warm, even hot, but I have placed them on the metal box of an external hard disk;
that keeps the heat from getting too strong.

some side info:
the mounting will remain until the next scheduled backup - and will then be removed by the backup script
as long as the mounting persists, you can see it under Windows at \\METEOBRIDGE\data\USB
as long as the ../data/USB directory is open in WIndows Explorer the backup script will not be able to remove the mount

Re: 100% data store usage

Posted: Thu Aug 05, 2021 11:19 am
by Rennpferd
Thanks for the detailed guide to help. Now I understand a little more how the device is organized. Now I'm on vacation for a few days. I can do some things remotely, but I can only pull out the USB stick when I'm back at the weather station.

I think it wouldn't be easier to reset the MB to factory settings. If I have a backup of the weather database and a backup of the configuration settings should that go really quickly?

Would that be the instructions to delete everything and to format the internal memory (Storage ATP)?

https://www.meteobridge.com/wiki/index. ... t_Sequence

Another consideration would be to use a USB stick permanently for the database. Do you know a professional product that works for a long time? A USB stick outside the housing would stay colder and could also be used for maintenance.

Re: 100% data store usage

Posted: Thu Aug 05, 2021 12:56 pm
by Gyvate
If your USB stick is already plugged in and contains your backup database, you don't need to insert it anymore. 8)

You can reset to factory settings, but you would lose all your configuration (if you have saved it to a PC in the System/administration tab, coming back to the old configuration will be easier). But there's no gain as far as the database is concerned. It will remain - and that's the issue for playing back the backup right now.

Regarding moving the database to an external USB device:
I would suggest to connect an external SATA-6 SSD with an USB3 connector (even though the MB doesn't support USB3, but it's downward compatible).
It should not need too much power and could be fed with a USB2 port.

Another less bulky option could be to use a microSD USB3 adapter with a let's say 64 GB San Disk MAX ENDURANCE microSD - they should hold for a while. :wink: - I use them for my hourly backups. (Even though a 256 GB version - that's for hourly backup, not for MB running the database).

Meanwhile you could order a 16 GB WD/SanDisk SLC microSD card [Western Digital/SanDisk SDSDQED-016G-XI, +/- 28 EUR] (24 weeks waiting time !!) with mouser.de or arrow.de and later on switch the cards (and copy the database). Your backup USB could still be in the other USB port.
If you plan at some point in time to move to the MB on RPi, you could use the SLC microSD.

Re: 100% data store usage

Posted: Tue Aug 17, 2021 1:47 pm
by Rennpferd
It took me a few days, now I can report what I did.

The analysis has shown that the built-in USB stick (an ATP Nano Dura SLC 1GB USB stick) repeatedly fails sporadically. Sometimes it works and then fails and works again, it breaks the operating system and the database.

That made it so difficult to solve, a total failure would have been easier :-)

I wanted to replace it, which in principle also worked. But I noticed how warm the memory in the device gets and decided to only use the external USB ports.

At the front I use the connection for the database and at the back for the automatic backups.

Since I didn't get an SLC USB stick so quickly, I now use two SanDisk MobileMates with a SanDisk MAX ENDURANCE microSD card. Thanks for the tip, I didn't know this type of SandDisk yet.

MB Pro USB Intern.jpg
MB Pro USB Intern.jpg (293.63 KiB) Viewed 1864 times

This combination even fits into the housing. But I noticed how hot it gets in operation and have now only installed everything on the outside. The slot inside now remains free and the CPU in the case may be colder. If there are problems I can change the memory so quickly. Currently the memory is sufficient for 58 years :-)

20210815-134835.png
20210815-134835.png (36.23 KiB) Viewed 1864 times

The tips should make it easy to restore the old backup. But it didn't work as easily as described. I always had the problem that the old data was not imported, I didn't know why?

Working and copying through the SSH terminal was also a solution, but the database kept producing errors and not working properly.

I set everything up again 100% without old data and probably got the old data back in with a trick.

I would like to see a few new functions for these cases.

It would have helped me to be able to check an external backup file and to be able to rebuild it in the event of an error. This is currently only possible with the internal database.

The error messages didn't help me, adding more details to the log file would be good in such a case.

I also had the old data as a CSV file, but I was not aware of any format how I could properly import it again. The correct filling via the import was too unsure for me because I did not understand the import formats perfectly.

A standard “Meteobridge RAW CSV Format” for export and import would be great. In such a case, that could be analyzed and, if necessary, repaired with Excel before importing.

Now it's working again. I hope it stays like this.

Re: 100% data store usage

Posted: Tue Aug 17, 2021 2:11 pm
by Gyvate
Rennpferd wrote: ↑Tue Aug 17, 2021 1:47 pm It took me a few days, now I can report what I did.

The analysis has shown that the built-in USB stick (an ATP Nano Dura SLC 1GB USB stick) repeatedly fails sporadically. Sometimes it works and then fails and works again, it breaks the operating system and the database.

That made it so difficult to solve, a total failure would have been easier :-)

I wanted to replace it, which in principle also worked. But I noticed how warm the memory in the device gets and decided to only use the external USB ports.
a) Did you try to contact Smartbedded on that ? They might replace the internal USB - even the whole maiboard:
info@smartbedded.com
b) the MB Pro can get pretty warm not to say hot - mine gets up to 50°C - I put the case on an old 3.5" HDD which serves as a heat conductor - that reduces the temperature quite well.
At the front I use the connection for the database and at the back for the automatic backups.

Since I didn't get an SLC USB stick so quickly, I now use two SanDisk MobileMates with a SanDisk MAX ENDURANCE microSD card. Thanks for the tip, I didn't know this type of SandDisk yet.

This combination even fits into the housing. But I noticed how hot it gets in operation and have now only installed everything on the outside. The slot inside now remains free and the CPU in the case may be colder. If there are problems I can change the memory so quickly. Currently the memory is sufficient for 58 years :-)
I wouldn't care too much about heat with a proper passive cooling equipment in place(like my "re-purposed" old HDD)
The tips should make it easy to restore the old backup. But it didn't work as easily as described. I always had the problem that the old data was not imported, I didn't know why?

Working and copying through the SSH terminal was also a solution, but the database kept producing errors and not working properly.

I set everything up again 100% without old data and probably got the old data back in with a trick.

I would like to see a few new functions for these cases.

It would have helped me to be able to check an external backup file and to be able to rebuild it in the event of an error. This is currently only possible with the internal database.
you could do this even on a Windows PC with SQlite - the database used by MB is a SQLite database.
The error messages didn't help me, adding more details to the log file would be good in such a case.

I also had the old data as a CSV file, but I was not aware of any format how I could properly import it again. The correct filling via the import was too unsure for me because I did not understand the import formats perfectly.

A standard “Meteobridge RAW CSV Format” for export and import would be great. In such a case, that could be analyzed and, if necessary, repaired with Excel before importing.
Regarding import - did you read the WiKi importing data ?
https://www.meteobridge.com/wiki/index. ... ata_Import
All times are UTC+02:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited