[RESOLVED] 1.0.7 Ubuntu Database Schema Failed

[anarking]

Hi All,

I've done many upgrades of ispCP in the past so tried the usual tricks, but this is a new one on me... I get:

Pre-installation tasks for
* Nothing to do... [ Done ]
* Loading old ispCP configuration file: [ Done ]
* Update ispCP configuration file: [ Done ]
* Check ispCP configuration file: [ Done ]
* Update ispCP key configuration file: [ Done ]

ispCP database
* Update ispCP database schema: [ Failed ]

[FATAL] An error occurred during update process!
Correct it and re-run this program.

Log files are stored in /var/log/ispcp/setup

And then in the log file I have...

sys_command_rs() | Starting...
system() | [DEBUG] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/mhash.so' - /usr/lib/php5/20090626/mhash.so: cannot open shared object file: No such file or directory in Unknown on line 0

[ERROR]: Error: Configuration variable `PORT_POSTGREY` is missing!

StackTrace:
#0 /var/www/ispcp/gui/include/ispCP/Config/Handler.php(93): ispCP_Config_Handler->get('PORT_POSTGREY')
#1 /var/www/ispcp/gui/include/ispCP/Update/Database.php(1809): ispCP_Config_Handler->__get('PORT_POSTGREY')
#2 /var/www/ispcp/gui/include/ispCP/Update.php(195): ispCP_Update_Database->_databaseUpdate_43(false)
#3 /var/www/ispcp/engine/setup/updDB.php(49): ispCP_Update->executeUpdates()
#4 {main}



sys_command_rs() | Ending...

So what's up with it failing because of the port_postgrey variable it can't find? I have the postgrey line in postfix's main.cf file commented out and such because I don't use it, but enabling doesn't help. Where can I add this or what I can change so that the upgrade can continue? Everything is down with the installation midway... Thanks for the help, I appreciate everything that's done here.

[motokochan]

Add the "PORT_POSTGREY" setting in ispcp.conf and try to re-run the update.

[anarking]

Oh it was supposed to be in the conf. I was trying the table in the DB. Thanks so much, that got it past that.

Now it's:

Rebuilding all services configuration files
* ispCP system resolver: [ Failed ]


[ERROR] Unable to found your resolv.conf file!

All I have on my system are:
find / -name *resolv.conf*
/var/lib/backuppc/pc/localhost/0/f%2fetc/fresolv.conf
/var/lib/wicd/resolv.conf.orig
/var/spool/postfix/etc/resolv.conf
/home/configs/etc/resolv.conf
/usr/share/ubuntu-docs/ubuntu/sample/resolv.conf
/usr/share/ubuntu-serverguide/html/sample/resolv.conf
/usr/share/ubuntu-serverguide/html/sample/sample/resolv.conf
/usr/share/man/man5/resolv.conf.5.gz
/root/Backups/etc/resolv.conf
/etc/resolv.conf


What does it want?

---

Okay I fixed that, now I get
Rebuilding all customers configuration files
* Please wait, this may take some time: [ Failed ]

And nothing in the logs! Bloody hell.

Right before, it said it couldn't find my default pma config file and made a new one. I had it use the same pma username and password as was used before, just in case. Upgrading to 1.0.6 had a lot fewer hickups than this. hopefully it's just failing now because the setup doesn't have the right login to the DB???

after running the update and it fails, i get this in the log:

getCmdExitValue() | [DEBUG] External command exited with value 0
getCmdExitValue() | Ending...
sys_command('/bin/cp -f /etc/ispcp/pma/working/config.inc.php /var/www/ispcp/gui/tools/pma/') | Ending...
setup_gui_pma() | Ending...
setup_gui_cfg() | Ending...
rebuild_customers_cfg() | Starting...
doSQL() | Starting...
doSQL() | Ending...
doSQL() | Starting...
doSQL() | Ending...
doSQL() | Starting...
doSQL() | Ending...
doSQL() | Starting...
doSQL() | Ending...
doSQL() | Starting...
doSQL() | Ending...
doSQL() | Starting...
doSQL() | Ending...
exit_msg() | Starting...
exit_msg() | Ending...
del_file() | Starting...
del_file() | Ending...

[anarking]

Okay, that just wasn't going to work, I was trying the trunk from 4/1/2011 after 1.0.7 wasn't taking, so side note, that won't work. went back to trying 1.0.7 after the tip about the postgrey port, and then it had trouble logging into SQL, so per another thread I copied the old hash keys into the two ispcp-db-keys.php and ispcp-db-keys.pl files that had the new incorrect ones, and it worked. thanks very much motokochan, for the tip that helped get past that point.