Community discussions

MikroTik App
 
Gombeen666
Member Candidate
Member Candidate
Topic Author
Posts: 224
Joined: Tue Jun 25, 2019 5:33 pm

dude,critical db failure: database disk image is malformed

Mon Aug 02, 2021 4:59 pm

I just created a CHR VM on Proxmox - (credit to smileymattj https://www.youtube.com/watch?v=wI98U1WBFFI )

There is 10G free space and the issue I have is that on dude database FTP upload stops around 100M on any of my backup's - (note my backup's are from
Dude 4.0beta3 which I am now migrating to 6.48.3 )

Is this a limitation on the free licence and while I have no problem in purchasing a licence, I don't to discover that this a limitation on the CHR !
Last edited by Gombeen666 on Tue Aug 03, 2021 3:21 pm, edited 1 time in total.
 
Gombeen666
Member Candidate
Member Candidate
Topic Author
Posts: 224
Joined: Tue Jun 25, 2019 5:33 pm

Re: CHR on Proxmox - Dude dB FTP upload issue

Tue Aug 03, 2021 3:14 pm

Ok solved the incomplete ftp file transfer !

Now I have "echo: dude,critical db failure: database disk image is malformed"

Any suggestions as the dB is working OK on Dude 4.0beta3
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: dude,critical db failure: database disk image is malformed

Tue Aug 03, 2021 3:59 pm

The database is incompatible with new versions.

I try on the past to convert from 4 to 6, but after some time the "converted" database do everytime problem.

Starting from scratch on 6.x and no problem till now.
 
Gombeen666
Member Candidate
Member Candidate
Topic Author
Posts: 224
Joined: Tue Jun 25, 2019 5:33 pm

Re: dude,critical db failure: database disk image is malformed

Wed Aug 04, 2021 12:56 am

Got the issue fixed by
(1) first importing and applying my oldest backup 2019 which worked - I copied the dude.db
(2) then imported a 2020 backup ( dude prompted about vacuuming ...) worked OK - once again copied dude.db
(3) then I imported a backup created 3 days ago and this gave the malformed disk image !
(4) I deleted dude.db and brought back a working dude.db from earlier and it worked OK
(5) I created another backup from V4 and imported - this now working OK

Who is online

Users browsing this forum: No registered users and 36 guests