My log.txt states "database disk image is malformed"

If your log.txt/server log window states the below error, the fastest way to get the system up and running again is to revert to a backup of the database from a time from before the message day/time.

Further analyzing the log.txt it maybe that it can give a clue on what has happened.

35235: 20240529:1243:   DB Save Completed
20240529:1243: [DEBUG Starting connected:check_for_inactivity_loop]
20240529:1243: [DEBUG Done connected:check_for_inactivity_loop]
20240529:1244: [DEBUG Starting connected:check_for_inactivity_loop]
20240529:1244: [DEBUG Done connected:check_for_inactivity_loop]
20240529:1245: [DEBUG Starting connected:check_for_inactivity_loop]
20240529:1245: [DEBUG Done connected:check_for_inactivity_loop]
20240529:1246: [DEBUG Starting connected:check_for_inactivity_loop]
20240529:1246: [DEBUG Done connected:check_for_inactivity_loop]
20240529:1247: [DEBUG Starting connected:check_for_inactivity_loop]
20240529:1247: [DEBUG Done connected:check_for_inactivity_loop]

INIT
385: 20240529:1250:   Running: farmerswife Server 7.0 Service Pack 4 (Build: 7.0.1004-0-g64e20d99c) (Intel FW Version)
385: 20240529:1250:   Running on: Darwin 18.7.0 (x86_64 64 bits)
385: 20240529:1250:   Process ID (PID): 385
385: 20240529:1250:   Loading Graphics
385: 20240529:1250:   Checking License
385: 20240529:1250:   IP: 192.168.0.239
385: 20240529:1250:   Init SQLite Library
385: 20240529:1250:   Loading Tree
385: 20240529:1250:   Loading Database
385: 20240529:1250:   Checking If SQLite Database Is Correct...
385: 20240529:1250:   SQLite Database Is OK
385: 20240529:1250:   Checking If SQLite Database Is Up-To-Date...
385: 20240529:1250:   SQLite Database Is Up-To-Date
385: 20240529:1250:   Optimizing/Analyzing SQL Database
385: 20240529:1250:   Done Optimizing/Analyzing SQL Database
385: 20240529:1250:   CRASH id202405291250260000000001

... it looks like there was a power-cut on the host machine yesterday at 12:47.

Solution:

This power-cut seems to have corrupted one or more SQLite "helper databases" of the farmerswife system.

It crashes on this step: "Checking If Histories SQLite Database Is Correct...".

To resolve:

Copy from here: Full Backup Folder: e.g. /Users/fwserver/Documents/FW Files/Full Backup

... the latest usable "histories.db3" file.

Ensure your fw Server app ist not running.

On your farmerswife Server app here "/Applications/farmerswife64 Server 7.0 SP4" use "Show Package Contents" then go into the "system" folder.

Here rename "histories.db3" to "corrupt-histories.db3".

Paste the "latest usable "histories.db3" file from "Full Backups".

Launch the fw Server app.

IMPORTANT:

More than one file might be affected.

Due to the roll-back to the latest usable histories.db3 you will lose "Booking actions history" for the time range of the date of that file until you start using it. All info will be there, except for this period.

Related Articles