Problem after upgrading Plesk 11.0.9 to 11.5.29 and installing business manager

[MarkRe]

Hi Guys,

Ok I have two problems here, I'm not sure if they are related.

The first is my webmail.* directory no longer points to horde, inside plesk I was getting this message:

[Template_Variable_Domain] Wrong variable to subsitute: enabled

I tried to rebuild them with a link provided with no avail.

The second is I can no longer log into plesk, when I try I get to https://xxx.xxx:8443/relay and get the message:

Can not extract SAML message.

I've tried to repair plesk following this - http://kb.parallels.com/en/9266

Can anyone shed any light on this? I'm stumped.

Edit

I can log in via https://xxx.xxx:8443/plesk-billing/admin/ OK, I've also tried 'Fix Problems With Logging in to Panels' but this doesn't seem to work

 

[Andrey Dyagilev]

Hi!

Can you explain your steps?
I tried to reproduce this bug on Debian6 i386 by following steps:
1. Install Plesk 11.0.9 (Standart)
2. Add Customer with Subscription
3. Add e-mail for Customer (Horde is set by default)
4. Upgrade to 11.5.29 -> All works fine
5. Add Billing, configure -> All works fine
So, I can't reproduce this bug and I need more information about it

 

[MarkRe]

Hi!

Can you explain your steps?
I tried to reproduce this bug on Debian6 i386 by following steps:
1. Install Plesk 11.0.9 (Standart)
2. Add Customer with Subscription
3. Add e-mail for Customer (Horde is set by default)
4. Upgrade to 11.5.29 -> All works fine
5. Add Billing, configure -> All works fine
So, I can't reproduce this bug and I need more information about it

The Email problem I've fixed, I had overridden the config with a custom webmailtemplate.php file as shown here:

http://forum.parallels.com/showthre...change-Horde-Webmail-URL-(webmail-domain-com)

I recreated it.

I still have a problem with SSO though, I have to disable it to reach the panel otherwise I get the message "Can not extract SAML message.":

/usr/local/psa/bin/sso --disable

 

[mouse Jerry]

Hello I am having a similar problem and has brought me to a stand still.!!!!
all I did was - Upgrade to 11.5.29 - from 11.0.9 (which had small business admin, not used though)

left me with a panel login of -
..-. ..- -.-. -.-
Can not extract SAML message.
..-. ..- -.-. -.-
here is results of a bootstrapper repair.



START Bootstrapper 11.5.29 repair AT Sat Jun 15 18:28:45 EDT 2013

**** Product repair started.

===> Checking for previous installation ... found.
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.11.5.29-11.5.29.20130615-182845.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
Trying to resolve hostname 'mail.nantucket.net' and validate its IP address... done

Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: sitebuilder_db@localhost, aspcomplete@%, aspcomplete@localhost, [email protected], aspcsk@%, aspcsk@localhost, [email protected], aspcss@%, aspcss@localhost, [email protected], aspsession@%, aspsession@localhost, [email protected].
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.

Trying to set psa database version to 011005029... done
After end of upgrade for 'core' (stage 'prep') following actions are registered as failed: 20111115171314-upgrade_mysqlnd_old_passwd 20111115171314-upgrade_mysqlnd_old_passwd.
===> Plesk database was not upgraded completely. See installation log for details.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Trying to upgrade APS controller database... ===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'db') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.11.5.29-11.5.29.20130615-182855.dump.gz
===> Upgrade and repair of APS controller database has been completed.
done
Reconfiguring mail subsystem...
Trying to execute mail_restore to synchronize mail server settings and Plesk Database... ==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_handlers_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: vhostidmng... not exists
==> Checking for: mail_spam_restore... ok
==> Checking for: mail_grey_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_drweb_restore... ok
done
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
If problems persist, please check installer logs ('/tmp/plesk_11.5.29_repair.log' and '/tmp/plesk_11.5.29_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Parallels support.

**** Product repair failed.

***** problem report *****
Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: sitebuilder_db@localhost, aspcomplete@%, aspcomplete@localhost, [email protected], aspcsk@%, aspcsk@localhost, [email protected], aspcss@%, aspcss@localhost, [email protected], aspsession@%, aspsession@localhost, [email protected].
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.
STOP Bootstrapper 11.5.29 repair AT Sat Jun 15 18:32:26 EDT 2013
START Bootstrapper 11.5.29 repair AT Sat Jun 15 21:09:51 EDT 2013

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mysqld... (pid 3536) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 011005029
Version is OK, no need to create psa database.
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.11.5.29-11.5.29.20130615-210952.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
Trying to resolve hostname 'mail.nantucket.net' and validate its IP address... done

httpsd: no process killed

Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: sitebuilder_db@localhost, aspcomplete@%, aspcomplete@localhost, [email protected], aspcsk@%, aspcsk@localhost, [email protected], aspcss@%, aspcss@localhost, [email protected], aspsession@%, aspsession@localhost, [email protected].
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.

Trying to set psa database version to 011005029... done
After end of upgrade for 'core' (stage 'prep') following actions are registered as failed: 20111115171314-upgrade_mysqlnd_old_passwd 20111115171314-upgrade_mysqlnd_old_passwd 20111115171314-upgrade_mysqlnd_old_passwd 20111115171314-upgrade_mysqlnd_old_passwd.
===> Plesk database was not upgraded completely. See installation log for details.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Trying to upgrade APS controller database... ===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'db') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.11.5.29-11.5.29.20130615-210957.dump.gz
===> Upgrade and repair of APS controller database has been completed.
done
Reconfiguring mail subsystem...
Trying to execute mail_restore to synchronize mail server settings and Plesk Database... ==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_handlers_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: vhostidmng... not exists
==> Checking for: mail_spam_restore... ok
==> Checking for: mail_grey_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_drweb_restore... ok
done
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
If problems persist, please check installer logs ('/tmp/plesk_11.5.29_repair.log' and '/tmp/plesk_11.5.29_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Parallels support.

**** Product repair failed.

***** problem report
Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: sitebuilder_db@localhost, aspcomplete@%, aspcomplete@localhost, [email protected], aspcsk@%, aspcsk@localhost, [email protected], aspcss@%, aspcss@localhost, [email protected], aspsession@%, aspsession@localhost, [email protected].
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.
STOP Bootstrapper 11.5.29 repair AT Sat Jun 15 21:12:28 EDT 2013

 

[mouse Jerry]

The Email problem I've fixed, I had overridden the config with a custom webmailtemplate.php file as shown here:

http://forum.parallels.com/showthre...change-Horde-Webmail-URL-(webmail-domain-com)

I recreated it.

I still have a problem with SSO though, I have to disable it to reach the panel otherwise I get the message "Can not extract SAML message.":

/usr/local/psa/bin/sso --disable

TY TY TY - I didn't even think at looking at the SSO - and the suggestion of shutting off was just what I needed to get at the problem

TY again

Jerry The Mouse

 

[Andrey Dyagilev]

MarkRe, try to turn on SSO and run
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all
/usr/share/plesk-billing/integration --command=repair-all
/usr/share/plesk-billing/cache -c && /etc/init.d/sw-cp-server restart

 

[MarkRe]

MarkRe, try to turn on SSO and run
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all
/usr/share/plesk-billing/integration --command=repair-all
/usr/share/plesk-billing/cache -c && /etc/init.d/sw-cp-server restart

No joy I'm afraid:

I've already tried these but did again at your suggestion. I've also tried a bootstrapper repair.

Still the only way I can access the panel is by disabling SSO.

Thanks though, any other suggestions would be appreciated!


mouse Jerry - NP, Let me know if you find anything else, this is driving me nuts!

 

[Andrey Dyagilev]

No joy I'm afraid:
I've already tried these but did again at your suggestion. I've also tried a bootstrapper repair.
Still the only way I can access the panel is by disabling SSO.

I'm afraid in this case need to manually clean and repair SSO. There are logs and command outputs required to understand what's happens with SSO. These outputs are not for shared forum.
You may ask for help Parallels Support.