how to use modify-domain without updating the MySQL user password.

Submitted by reachoneinternet on Tue, 10/23/2012 - 11:19

The documentation for "virtualmin modify-domain" say

[root@titan ~]# virtualmin help modify-domain
MODIFY-DOMAIN(1)      User Contributed Perl Documentation     MODIFY-DOMAIN(1)

modify-domain.pl
       Change parameters of a virtual server.
....

       By default, virtual server plan changes that modify features will be blocked if any warnings are detected, such as an existing database or SSL certificate conflict. These can be overridden with the "--skip-warnings" flag.

That doesn't seem to be the case however (from my logs) :

https://x.x.x.x:10000/virtual-server/remote.cgi?program=modify-domain&domain=example.com&pass=****************&email=user@example.net&apply-plan=Basic<br>
Mon, 22 Oct 12 15:47:21 -0700MODIFY result from virtualmin:< /br>/n Updating virtual server example.com ..
Modifying administration user ..
.. done
Changing MySQL password ..
.. done
Updating Webmin user ..
.. done
Updating password for AWstats ..
.. done
Saving server details ..
.. done
Updating Webmin user ..
.. done
Re-loading Webmin ..
.. done
All done
Exit status: 0
Status: 
Active

Comments

Submitted by JamieCameron on Tue, 10/23/2012 - 12:39

You can stop the MySQL password from being synced with the domain's Unix password by first changing it at Edit Databases -> Passwords. There is no flag to the modify-domain command to not update MySQL.

Submitted by reachoneinternet on Tue, 10/23/2012 - 12:44

then I'd say the documentation on that script is unclear or misleading.

Submitted by JamieCameron on Tue, 10/23/2012 - 12:58

I'm confused .. which part of the documentation is inaccurate?

Submitted by reachoneinternet on Tue, 10/23/2012 - 13:24

i thought "virtual server plan changes that modify features will be blocked if any warnings are detected, such as an existing database" would qualify here, since there was an existing database... although i am just re-applying the existing plan.

Submitted by JamieCameron on Tue, 10/23/2012 - 13:48

That message means that if you make a plan change which enables a database for a domain and there is already a database with the same name on the system (not associated with any virtual server), you will need to use the --skip-warnings flag. This will cause the database to be owned by the domain.