+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Update/Upgrade (/forum-44.html)
+--- Thread: Update ispCP database schema ... FAILED (/thread-10465.html)
RE: Update ispCP database schema ... FAILED - peman - 02-16-2012 10:43 PM
yes, this worked for me too but all email accounts doesnt work. i had to change the password for on my email account but i cant do this for all my customers in the future when i´m going to do the upgrade on my live server.
is there any fix for this, please?
RE: Update ispCP database schema ... FAILED - ephigenie - 02-16-2012 11:20 PM
you had the problem by upgrading from which version to which version ?
RE: Update ispCP database schema ... FAILED - peman - 02-17-2012 12:01 AM
sorry, i upgraded from 1.0.5 to 1.0.7 on Debian Lenny.
RE: Update ispCP database schema ... FAILED - Arno - 07-05-2012 08:44 PM
I had similar problems while updating from 1.06 to 1.07, and now I know the reason:
At first I followed the install manual, and when I recognized my fault, I went to the upgrade manual. It was just a little bit to late.
Not knowing, whether or not my way is right or wrong, it worked for me:
Switch to debug (/etc/ispcp/ispcp.conf, search for "DEBUG" and set the value to "1") and run the script ispcp-update again. Then I searched for the database connects and replaced the defaults by my data for user and password. I got the update script running.
Now I dumped the ispcp database and did a fresh install. When it was up and running, I stopped the daemon, reloaded my dump, set the status fields according the underneath statements to force a rewrite of the configuration:
PHP Code:
UPDATE domain SET domain_status = 'change' WHERE domain_status = 'ok';
UPDATE domain_aliasses SET alias_status = 'change' WHERE alias_status = 'ok';
UPDATE subdomain SET subdomain_status = 'change' WHERE subdomain_status = 'ok';
Then I run the script ispcp-rqst-mngr, started the daemon and was done.