Incorrect restore of only database + correct setting in MySQL settings generated by Virtualmin Pro ?

Nota bene: When restorign All features, the database is correctly deleted first. Which it's not here, and thus it's not recreated.

I've seen no errors before or after, otherwise would have pasted them here. :-)

Here the Wemin page contents from the activity log: (I love that activity log feature:

While at it, this is the trace from the activity log of same log entry: could maybe help you (replaced domain and user by example and IP address at end by 1.1.1.1):

Hope that helps. :-)

Doing... t is not x :-D

Here the output of the command:

(mysqltuner.pl was a file in the main folder of that server, not accessible from the web).

You probably don't want to have 9.7 Gigabytes in your inbox.... ;-)

I thought it was an easy to reproducee bug, but seems that it works on a correctly restored site... So:

I need to add one more thing that might help you find the issue: Maybe "1)" is related to "2)": In the sense that following the bug "2)", I tried restoring only database as "1)".

But "2)" didn't complete, as I found out after posting bug, as it stopped at database restoration step with error "ERROR 2006 (HY000) at line 3633: MySQL server has gone away", and didn't complete the steps after that.

Here the exact full restore (from folder containing all new-version backup files) that ran before the database-content-only-restoration that failed BEFORE the trial above: (note that the ns3 was not migrated yet, and was giving errors, that could be ignored fine in all other restores that worked):

BUT also note that after that database max_packet issue all next domains restoration failed communicating with the slaved DNSes too. But interestingly, after fixing the setting of mysql, deleting example.com and example.net and following virtual servers, and restoring them worked fine.

ALL NEXT ONES WITH SAME ERRORS "Error reading response length from fastrpc.cgi : " ON ALL 3 NS servers, but when deleted virtual servers (one by one....) and redone a restore was ok...strange....

I assume that on the restore form, you selected only the "Contents of server's MySQL databases" feature?

yes, only that checkmark.

i'm not 100% sure if mysqld crashed, or just mysql client returned that error, as I was away during that very long restore, and no site was active during that restore.

Is there a log somewhere if the monitor of Virtualmin catches a mysqld down and restarts it automatically ?

Maybe related, but doubt it....: Separate actually very very annoying new bug "3)":

I also noticed that during last few days, on the old server automatic backups, and it happened to me also in the first trial to manually backup, the example.com.tar.gz file had only 20 bytes instead of 9.7 GigaBytes !!!

I'm attaching such a file (added .txt at end to upload)

The worst part of that other bug is that the email was like the whole backup was successful, no error, no notices, nothing, same as if everything went well ! ... except that backup was empty....and choking on invalid tar.gz file at restore. Fortunately, it was a server migration, and not a crash recovery! :-)

e.g.: (note total size and backup times):

To be compared with a successful backup (really successful):

Backup is complete. Final size was 15.19 GB. Total backup time was 1 hours, 52:33 minutes.
 
Sent by Virtualmin at: https://example.com:10000
 
Running pre-backup command ..
.. done
 
 
Creating backup for virtual server joomlapolis.com ..
   Copying virtual server configuration ..
   .. done
 
   Backing up Cron jobs ..
   .. none defined.
 
   Copying records in DNS domain ..
   .. done
 
   Saving mail aliases ..
   .. done
 
   Saving mail and FTP users ..
   .. done
 
   Backing up mail and FTP user Cron jobs ..
   .. done
 
   Copying Apache virtual host configuration ..
   .. done
 
   Copying Webalizer configuration files ..
   .. done
 
   Copying SSL Apache virtual host configuration and certificate ..
   .. done
 
   Copying Logrotate configuration ..
   .. done
 
   Dumping MySQL database joomlapo_production ..
   .. done
 
   Copying Procmail and SpamAssassin configuration files ..
   .. done
 
   Backing up AWstats configuration file ..
   .. done
 
   Creating TAR file of home directory ..
   .. done
 
   Uploading archive to SSH server li98.cbpolis.com ..
   .. done
 
.. completed in 1 hours, 17:39 minutes
 
Creating backup for virtual server ......
 
......
 
20 servers backed up successfully, 0 had errors.
9 Virtualmin configuration settings backed up successfully.
Deleting backups from /mnt/data/backups/example-%Y-%m-%d on SSH server backups.example.com older than 21 days ..
   Deleting file /mnt/data/backups/example-2012-11-25 via SSH, which is 21 days old ..
   .. deleted 4 kB.
 
.. deleted 1 old backups
 
Running post-backup command ..
.. done
<code>
 
 
(note that it says ".. deleted 4 kB." (which is the meta-data size of the folder, and not the content of it).
 
Unfortunately, automated backups seem not to be logged (with great precision) in the activity log like e.g. manual restores. So didn't find any deeper trace.
 
But this is a sign for us that we will have to put a second different and independent backup method in place...as we can't rely on this one only.

I also emailed you the 3 files (.dom and .info) if that can help.

No, we monitor disk space closely using Zabbix, and have alarm emails firing within seconds when the used space is above 80%, and that didn't happen on neither system.

Also there are concurrent backups by ssh to the backup server from other systems, but we try to have them not at same time. And that backED-up server is a dedicated server, so no other site owner can do backups at same time. There is only one daily scheduled backup. And it's the one with that (biggest virtual server with big database tables and lots of files) that failed.

I will sure keep an eye on backup sizes from now onwards and write in here when I have something.

In the mean time 2 other Backup restoration bugs:

4) When restoring a domain which was sharing an SSL key with another domain with same IP, the SSL key is not backed up with that domain, making the separate restoration of that domain on a different server not possible with the SSL feature: It gives an error that SSL can't be restored, because /home/otherdomain/ssl.key doesn't exist.

5) But when then trying to enable the SSL feature in "edit domain", it it STILL impossible to activate SSL, this is the result of the action: (btw, weird, it tries to change IP address, while it stays same, as it's only domain on that server, and using the shared address)

So I created the folder and copied over the ssl certificates. Then the feature got added ok.

So next bug:

6) But then when I go to edit the SSL certs, it says:

clicking on the link to edit doesn't go anywhere since the corresponding virtual server doesn't exist:

so yet another bug:

7) Even more wierd, DISABLING SSL certificate still doesn't get rid of the pointer to the other domain, because re-enabling it doesn't re-create a self-signed clean blank certificate.

Ok, two more bug when trying to separate websites to different servers one at backup time and one at restore time:

8) (backup):

+

9) (restore):

When deselecting to backup the users Email/FTP accounts, and deselecting to restore them, the huge folders homes/usernames and homes/usernames/Maildir (we use IMAP so they are huge) still get backed up AND still get restored. Even if backed up, if that feature is unselected at restore time, it should NOT be restored.

For me, main big bug in here is still "3)", and as said I will keep an eye on it...Btw, if destination folder is full, SSH sees that the transfer failed, and the backup is marked and emailed as Failed correctly. So it's certainly not that.

For this SSL issue, did you restore all the domains that shared an SSL cert at the same time?

No, only 1 of them that I wanted to put on a separate server (and not the one that Virtualmin decided was the "holder" of the SSL certificate, which was probably the first one that was added SSL on the old servers.

Ok, no worries, bug "4)" in here I can live with it. Would be nice if you had a work-around for bug "7)" which disallows to get out of bug "4)" situation. Any hint how to bring Virtualmin to forget about the SSL cert which was in the other now inexistent domain when disabling and then re-enabling the SSL feature ?

Still keeping an eye on the most serious of these bugs, the "3)" (20-bytes empty tar file instead of 10 gigs). I have seen backups on other old servers doing that too from time to time. Keeping an eye to new backups sizes.

How do I get rid of error: number 6) above in my comment #14 https://www.virtualmin.com/comment/590756#comment-590756 ?

StartSSL has been distrusted, so I'm moving to Let's-Encrypt, but can't because of that error, and I don't find where to unlink manually. Disabling SSL from domain then re-enabling it doesn't unlink from the unexistant domain.

Solving that issue is becoming urgent here.

Nevermind, found it: in file /etc/webmin/virtual-server/domains/XXXXXXXXXX remove line ssl_same="YYYYYYYY" fixed it for me.

You are welcome.

btw. I also had to change in that server file XXXXXXXXXXX the ssl private, public and cert file path. But that was obvious once the certs couldn't be written.

Note: The bugs reported in here are all still open.

Thanks, no rush, problem is solved on my end. Now all my certs use Let's encrypt. It took a full day to replace around 25 certs on around 12 servers because of all these linkages and a few surprises.

I found following way to break it manually on a server where they were linked properly: Replace the wildcard cert to which all domains were smart-linked by a self-signed one generated in virtualmin.

For the server where the migration of domains without the linked-to domain (splitting sites), I had to edit the virtualmin config files.

Linkages disappeared and the linked sites automatically got a self-signed certificate (according to the Virtualmin SSL page, didn't check if that was real, as I then just requested through virtualmin a Let's Encrpty Cert for each of those servers for subdomains of the main domain that had a wildcard cert separately with configured auto-renewals all 2 months in virtualmin). I luckily just didn't hit the 20 subdomains per week limit of Let's Encrypt!!!

btw, I have probably hit another bug in Virtualmin's Postfix's IP ports auto-config when I did delete a server and added it back as a subserver, it mixed up the IP addresses for Postfix, and as a result a server with dedicated IP address didn't get mails anymore (secondary server got them and forwarded them once the issue was fixed). But that could have been an old config that wasn't "right", as it was listening for smtp on all * IP addresses, and working fine. The new auto-config in Virtualmin replaced the * with main server IP address, but didn't add back an untouched domain with a private IP address that wasn't in there before, as not needed. Not enough clear thing to open a bug ticket for it.

Nice! Thanks Jamie! You rock as usual :-) Happy New Year!

(keeping open because of the other bugs)