Restore failed : setquota: user vhost_owner does not exist

Submitted by LonDoh on Wed, 11/21/2012 - 09:54

this error is occurring restoring a virtualmin vhost backup from an old box to a new install

virtualmin version is current centos 5.8 -> centos 6.3

Numerous other backups have restored OK, but this one fails with the above error It gets part way thru - restores the vmin settinsg before bombing I've redone a fresh backup, but still the same problem Quotas are set on the original vhost quotas were/are set on other vhosts that have restored without problems

Any ideas please why this one is failing?

Status: 
Active

Comments

Submitted by andreychek on Wed, 11/21/2012 - 13:25

What kind of Virtual Server is this?

Is it a top-level Server, Sub-Server, or Alias Server?

Submitted by JamieCameron on Wed, 11/21/2012 - 15:36

Also, could you post the full restore output for this domain?

Submitted by LonDoh on Wed, 11/21/2012 - 16:38

Hi

its a stand-alone top-level server. no sub or alias domains

So click 'Restore Backup'

on the next screen select a file (and I've tried with and without VM options included in backup) after clicking 'Show what will be restored' I get this:

    Webmin ACL files
    Logrotate configuration for log file
    Contents of server's PostgreSQL databases
    Virtual server password, description and other details
    Spam filtering
    Server's home directory and web pages
    Administration user's password, quota and Cron jobs
    Mail/FTP users and mail aliases
    Records in DNS domain, except SOA
    Contents of server's MySQL databases
    Webalizer configuration and schedule
    Apache webserver configuration
    Mailman mailing lists
    AWstats configuration file
    DAV users file

And then optionally this - depending on the backup selected:

Virtualmin configuration settings
    No selected Virtualmin settings in backup

and so click 'Restore Now' and then next screen opens and restore starts:

Starting restore of 1 domains from local file /root/backups/20-11-2012/example.tar.gz ..

Extracting backup archive file ..
.. done

Restoring backup for virtual server example.com ..
Restore failed : setquota: user vhost_owner does not exist.

and thats where it dies I deleted the incomplete install and re-backed up and tried again a few times now, but it wont have it.

Anyway... Luckily its not any kind of critical issue, and as with the other failures I noted I can more easily just re create the domain and users from scratch and copy over the files.

However on another day with a different domain it could be distressing tho!

[At least looking on the bright side: because it fails at least I dont have to copy over my newly cobbled together postfix configs :-) ]

Submitted by JamieCameron on Wed, 11/21/2012 - 17:37

That's an unusual error.

In the case above, does the example.com domain already exist on the system? If so, does deleting it before performing the restore make any difference?

Also, when you backed up (and when you restore), did you stick with the default behavior of having all features selected to include?

Submitted by LonDoh on Wed, 11/21/2012 - 20:02

Hi

In the case above, does the example.com domain already exist on the system?

initially no it didnt, I started out to migrate all sites to a new box with a fresh install of centos 6.3. I have full daily virtualmin backups on and off the server in which everything is selected in both feature blocks: "Features to backup" and "Virtualmin settings to also backup"

If so, does deleting it before performing the restore make any difference? no. I tried deleting it first and also restoring over it. same error

Also, when you backed up (and when you restore), did you stick with the default behavior of having all features selected to include?

I tried both with both, and also with different feature sets. It wasnt totally logical but I'm pretty sure I covered most combinations at least once!

And there's nothing I can point at that was particularly different about this domain than any of the others that restored OK. It fact in many ways it was easier = no sub or alias servers, minimal database. just a couple users with small maildirs.

Altho in this case it wasnt critical, I would have liked to understood the problem for obvious reasons -- but eventually boredom set in and I took the path of least resistance!

I've done a few complete migrations with virtualmin, and all previous have been faultless. But I've hit a number of niggles with this one - as per the other current tickets.

If you dont have any other questions I'm happy you mark ticket as closed.

thanks anyway.

Submitted by JamieCameron on Wed, 11/21/2012 - 20:13

If you like, I could try logging into your system and performing a test restore of this domain?

Alternately, you could email me the backup file at jcameron@virtualmin.com , and I can try a test restore on my own machine?