setup (25.08.2024 12:09:28): use UTC stamp 2024-08-25 10:09:28 (1 tries)
dbrepair (25.08.2024 12:09:32): database size is 9.8G.
dbrepair (25.08.2024 12:09:32): test integrity of database.
dbrepair (25.08.2024 12:09:32): RAM database integrity is fine, nothing to do.
dbrepair (25.08.2024 12:09:33): not enough free space to repair database.
dbase (25.08.2024 12:09:34): process started.
/tmp/mnt/data/backup$ df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 125.5G 23.2G 95.8G 20% /
tmpfs 116.5M 53.8M 62.7M 46% /tmp
tmpfs 512.0K 4.0K 508.0K 1% /dev
how is this possible ?
MB won't start the rebuild/repair process - option was: forced rebuild on reboot
A complete shutdown and restart of the VM didn't make any change ...
MB VM not enough space to repair database
Moderator: Mattk
MB VM not enough space to repair database
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
Re: MB VM not enough space to repair database
That should be fixable. Can you please provide me remote access?
Re: MB VM not enough space to repair database
I have meanwhile removed a 10 GB backup file from the RPi which it didn't seem to like.
Then after a full restart of the VM, not only a reboot, it's behaving properly again.
So for that probably a remote login won't give any insights
What is strange is now that during backup it brings error/warning messages of the type
backup (30.08.2024 10:12:00): backup completed: dbase-202408301000.gz (1.2G)
backup (30.08.2024 12:00:00): backup media size is 125.5G (63.4G free).
backup (30.08.2024 12:00:15): WAL file cannot be resolved, backup might be incomplete.
logger (30.08.2024 12:03:30): transfer of sensor data to database timed out: th2!9temp
logger (30.08.2024 12:03:35): transfer of sensor data to database timed out: th2!9hum
logger (30.08.2024 12:03:40): transfer of sensor data to database timed out: th2!9dew
logger (30.08.2024 12:03:45): transfer of sensor data to database timed out: th2!9heatindex
logger (30.08.2024 12:03:50): transfer of sensor data to database timed out: th2!9wetbulb
logger (30.08.2024 12:03:55): transfer of sensor data to database timed out: th3!1temp
logger (30.08.2024 12:04:00): transfer of sensor data to database timed out: th3!1hum
logger (30.08.2024 12:04:05): transfer of sensor data to database timed out: th3!1dew
logger (30.08.2024 12:04:10): transfer of sensor data to database timed out: th3!1heatindex
logger (30.08.2024 12:04:15): transfer of sensor data to database timed out: th3!1wetbulb
logger (30.08.2024 12:04:20): transfer of sensor data to database timed out: th3!3temp
logger (30.08.2024 12:04:25): transfer of sensor data to database timed out: th3!3hum
logger (30.08.2024 12:04:30): transfer of sensor data to database timed out: th3!3dew
logger (30.08.2024 12:04:36): transfer of sensor data to database timed out: th3!3heatindex
logger (30.08.2024 12:04:41): transfer of sensor data to database timed out: th3!3wetbulb
logger (30.08.2024 12:04:46): transfer of sensor data to database timed out: th3!7temp
logger (30.08.2024 12:04:51): transfer of sensor data to database timed out: th3!7hum
logger (30.08.2024 12:04:56): transfer of sensor data to database timed out: th3!7dew
logger (30.08.2024 12:05:01): transfer of sensor data to database timed out: th3!7heatindex
logger (30.08.2024 12:05:06): transfer of sensor data to database timed out: th3!7wetbulb
logger (30.08.2024 12:05:11): transfer of sensor data to database timed out: th3!25hum
logger (30.08.2024 12:05:29): transfer of sensor data to database timed out: th3!7wetbulb
logger (30.08.2024 12:05:39): transfer of sensor data to database timed out: thb0press
logger (30.08.2024 12:05:46): transfer of sensor data to database timed out: thb1!0temp
backup (30.08.2024 12:15:27): backup completed: dbase-202408301200.gz (1.2G)
if you still want to login - let me know
Then after a full restart of the VM, not only a reboot, it's behaving properly again.
So for that probably a remote login won't give any insights
What is strange is now that during backup it brings error/warning messages of the type
backup (30.08.2024 10:12:00): backup completed: dbase-202408301000.gz (1.2G)
backup (30.08.2024 12:00:00): backup media size is 125.5G (63.4G free).
backup (30.08.2024 12:00:15): WAL file cannot be resolved, backup might be incomplete.
logger (30.08.2024 12:03:30): transfer of sensor data to database timed out: th2!9temp
logger (30.08.2024 12:03:35): transfer of sensor data to database timed out: th2!9hum
logger (30.08.2024 12:03:40): transfer of sensor data to database timed out: th2!9dew
logger (30.08.2024 12:03:45): transfer of sensor data to database timed out: th2!9heatindex
logger (30.08.2024 12:03:50): transfer of sensor data to database timed out: th2!9wetbulb
logger (30.08.2024 12:03:55): transfer of sensor data to database timed out: th3!1temp
logger (30.08.2024 12:04:00): transfer of sensor data to database timed out: th3!1hum
logger (30.08.2024 12:04:05): transfer of sensor data to database timed out: th3!1dew
logger (30.08.2024 12:04:10): transfer of sensor data to database timed out: th3!1heatindex
logger (30.08.2024 12:04:15): transfer of sensor data to database timed out: th3!1wetbulb
logger (30.08.2024 12:04:20): transfer of sensor data to database timed out: th3!3temp
logger (30.08.2024 12:04:25): transfer of sensor data to database timed out: th3!3hum
logger (30.08.2024 12:04:30): transfer of sensor data to database timed out: th3!3dew
logger (30.08.2024 12:04:36): transfer of sensor data to database timed out: th3!3heatindex
logger (30.08.2024 12:04:41): transfer of sensor data to database timed out: th3!3wetbulb
logger (30.08.2024 12:04:46): transfer of sensor data to database timed out: th3!7temp
logger (30.08.2024 12:04:51): transfer of sensor data to database timed out: th3!7hum
logger (30.08.2024 12:04:56): transfer of sensor data to database timed out: th3!7dew
logger (30.08.2024 12:05:01): transfer of sensor data to database timed out: th3!7heatindex
logger (30.08.2024 12:05:06): transfer of sensor data to database timed out: th3!7wetbulb
logger (30.08.2024 12:05:11): transfer of sensor data to database timed out: th3!25hum
logger (30.08.2024 12:05:29): transfer of sensor data to database timed out: th3!7wetbulb
logger (30.08.2024 12:05:39): transfer of sensor data to database timed out: thb0press
logger (30.08.2024 12:05:46): transfer of sensor data to database timed out: thb1!0temp
backup (30.08.2024 12:15:27): backup completed: dbase-202408301200.gz (1.2G)
if you still want to login - let me know
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
Re: MB VM not enough space to repair database
My offer was focussed at the "not enough space" error which does not seem to be correct as you have plenty of free space.
Re: MB VM not enough space to repair database
These errors just tell that logger cannot reach database for storing new data while backup is running.Gyvate wrote: ↑Fri Aug 30, 2024 12:49 pm logger (30.08.2024 12:03:30): transfer of sensor data to database timed out: th2!9temp
logger (30.08.2024 12:03:35): transfer of sensor data to database timed out: th2!9hum
logger (30.08.2024 12:03:40): transfer of sensor data to database timed out: th2!9dew
logger (30.08.2024 12:03:45): transfer of sensor data to database timed out: th2!9heatindex
logger (30.08.2024 12:03:50): transfer of sensor data to database timed out: th2!9wetbulb
logger (30.08.2024 12:03:55): transfer of sensor data to database timed out: th3!1temp
logger (30.08.2024 12:04:00): transfer of sensor data to database timed out: th3!1hum
logger (30.08.2024 12:04:05): transfer of sensor data to database timed out: th3!1dew
logger (30.08.2024 12:04:10): transfer of sensor data to database timed out: th3!1heatindex
logger (30.08.2024 12:04:15): transfer of sensor data to database timed out: th3!1wetbulb
logger (30.08.2024 12:04:20): transfer of sensor data to database timed out: th3!3temp
logger (30.08.2024 12:04:25): transfer of sensor data to database timed out: th3!3hum
logger (30.08.2024 12:04:30): transfer of sensor data to database timed out: th3!3dew
logger (30.08.2024 12:04:36): transfer of sensor data to database timed out: th3!3heatindex
logger (30.08.2024 12:04:41): transfer of sensor data to database timed out: th3!3wetbulb
logger (30.08.2024 12:04:46): transfer of sensor data to database timed out: th3!7temp
logger (30.08.2024 12:04:51): transfer of sensor data to database timed out: th3!7hum
logger (30.08.2024 12:04:56): transfer of sensor data to database timed out: th3!7dew
logger (30.08.2024 12:05:01): transfer of sensor data to database timed out: th3!7heatindex
logger (30.08.2024 12:05:06): transfer of sensor data to database timed out: th3!7wetbulb
logger (30.08.2024 12:05:11): transfer of sensor data to database timed out: th3!25hum
logger (30.08.2024 12:05:29): transfer of sensor data to database timed out: th3!7wetbulb
logger (30.08.2024 12:05:39): transfer of sensor data to database timed out: thb0press
logger (30.08.2024 12:05:46): transfer of sensor data to database timed out: thb1!0temp
Re: MB VM not enough space to repair database
I know - and the error is no longer showing

WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
Re: MB VM not enough space to repair database
I would expect the data to be transferred to the WAL (write ahead log) file during backup and retroactively posted by the database once the backup is completed ...
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
Re: MB VM not enough space to repair database
Tell the sqlite developersGyvate wrote: ↑Fri Aug 30, 2024 2:31 pmI would expect the data to be transferred to the WAL (write ahead log) file during backup and retroactively posted by the database once the backup is completed ...
