SQL Update Failed - Printable Version +- ispCP - Board - Support (http://www.isp-control.net/forum) +-- Forum: ispCP Omega Support Area (/forum-30.html) +--- Forum: Update/Upgrade (/forum-44.html) +--- Thread: SQL Update Failed (/thread-3074.html) |
SQL Update Failed - metalmessiah - 04-18-2008 05:05 AM Hy, I'm going to update from RC2c to RC4, I did all steps on the Documentation. By starting perl ispcp-update, I get the follow error: Code: Welcome to ispCP '1.0.0 RC4 OMEGA' Update Dialog. Ispcp worked nice before, I didn't change any SQL Passwort in the /etc/ispcp/ispcp.conf, so what's the matter? Regards. RE: SQL Update Failed - metalmessiah - 04-21-2008 05:49 AM No Ideas? RE: SQL Update Failed - RatS - 04-21-2008 03:55 PM two Ideas: 1) you have overwritten your key-files 2) there is a bug in the update script. RE: SQL Update Failed - metalmessiah - 04-22-2008 03:41 AM RatS Wrote:two Ideas: So, what shall I do? Is it possible to override the update-script for a re-enter of my SQL pass? Regards. EDIT: I recovered the keys, update did finish successful, but when I'm going access my Logon Page I get this errors: Code: Notice: Undefined index: LOGIN_TEMPLATE_PATH in /var/www/ispcp/gui/include/system-message.php on line 37 RE: SQL Update Failed - joximu - 04-22-2008 07:37 AM http://www.isp-control.net/forum/error-after-succes-update-%28index-website%29-t-2943.html RE: SQL Update Failed - metalmessiah - 04-23-2008 04:36 AM joximu Wrote:http://www.isp-control.net/forum/error-after-succes-update-%28index-website%29-t-2943.htmlHi That didn't work for me, I still have this error. What should I recover from my backuped files before the update? Regards. RE: SQL Update Failed - metalmessiah - 04-23-2008 04:51 AM Hi, You forgot to say in the Upgrade Guide, that you must recopy all DB-Keys on the old place. Please add some lines on your Guide. Regards RE: SQL Update Failed - joximu - 04-23-2008 07:41 AM The important message in your Log above is: *** ERROR: Unable to connect to SQL server ! SQL returned: Access denied for user 'root'@'localhost' (using password: YES) *** |