Still "File not found", even after several "repairs"

[Holger]

Hi,
since last week I couldn't connectto the Plesk Panel on my vServer.
The login-screen on https://<vserver>:8843 ist shown an I could insert root-data. But after clicking "login" a blank page is shown with "file not found" on https://<vserver>:8443/admin/
Within M$-IExplorer the normal "404-message" is shown.

I've tried several repairs. With "bootstrapper" an the new "/usr/local/psa/bin/repair", but none of these helped.
[root@vxxxx ~]# cat /usr/local/psa/version
12.5.30 CentOS 6 1205151127.16
[root@vxxxx ~]# cat /usr/local/psa/core.version
12.5.30 CentOS 6 1205151127.16

I've searched lots of support pages and followed the mentioned tips.But no luck.
Restarting "sw-cp-server" didn't give any error messages. Even restarting the whole server solves the problem.

I think it could be a problem with fastCGI but I didn't found any misconfiguered settings.

thanks for any help
bye
Holger

 

[IgorG]

If I correctly understood command

# plesk repair installation

didn't help?

 

[Holger]

Hi,
yes,you're right.
When using "plesk repair installation" I got the following output:

[root@vxxxx ~]# less /var/log/plesk/install/plesk_12.5.30_repair_problems.log

START Bootstrapper 12.5.30 repair AT Thu Jan 28 07:18:31 CET 2016
***** 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: Joomla2Admin@localhost, ibb2joadmin@localhost, svjoadmin@localhost, mrbsdb@localhost, eval2DBadm@localhost, didakt@localhost, LXCAdmin@localhost.
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 12.5.30 repair AT Thu Jan 28 07:21:13 CET 2016: PROBLEMS FOUND

But all of these users don't use the plesk panel.
But this could be the problem, because:

[root@vxxxx ~]# less /var/log/plesk/install/plesk_12.5.30_repair.log
....
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: Joomla2Admin@localhost, ibb2joadmin@localhost, svjoadmin@localhost, mrbsdb@localhost, eval2DBadm@localhost, didakt@localhost, LXCAdmin@localhost.
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 012005030... 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 20111115171314-upgrade_mysqlnd_old_passwd 20111115171314-upgrade_mysqlnd_old_passwd.
===> Plesk database was not upgraded completely. See installation log for details.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
[2016-01-28 07:18:51] ERR [panel] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-server-backup_ftp_settingactive' for key 'id':
0: /usr/local/psa/admin/externals/Zend/Db/Statement/Pdo.php:234
Zend_Db_Statement_Pdo->_execute(array)
1: /usr/local/psa/admin/externals/Zend/Db/Statement.php:300
Zend_Db_Statement->execute(array)
2: /usr/local/psa/admin/plib/Upgrade/Task/12.1.26/2015-06-29-10-12-53_UpdateBackupFtpStorageSettings.php:37
Plesk\Upgrade\Task\UpdateBackupFtpStorageSettings->upgrade(object of type Plesk\Upgrade\Deferred)
3: /usr/local/psa/admin/plib/Upgrade/Executor/Sync.php:15
Plesk\Upgrade\Executor_Sync->upgrade(string '2015-06-29-10-12-53', object of type Plesk\Upgrade\TaskLoader, object of type Plesk\Upgrade\Deferred)
4: /usr/local/psa/admin/plib/Upgrade/Command/Task.php:46
Plesk\Upgrade\Command_Task->run(string '2015-06-29-10-12-53', string 'upgrade')
5: /usr/local/psa/admin/plib/Upgrade/upgrade.php:19

taskId=2015-06-29-10-12-53 step=upgrade result=1 message=ERROR: Zend_Db_Statement_Exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry &#039;1-server-backup_ftp_settingactive&#039; for key &#039;id&#039; (Pdo.php:234)<br />
<br><a href='http://kb.odin.com/plesk-error/sear...nstraint+violation:++Duplicate+entry++for+key' target='_blank'>Search for related Knowledge Base articles</a>Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.


How to update the MySQL-Passwords?

[root@vxxxx ~]# rpm -qa | grep mysqlclient | xargs rpm -q --queryformat '%{RELEASE}\n'
2.el6.art

So,like in https://kb.odin.com/en/113737 discribed "bootstrapper" should solve the problem.

Or is the most effective error this (see above):
==> Integrity constraint violation: 1062 Duplicate entry '1-server-backup_ftp_settingactive' for key 'id':

But how to fix this (from commandline)?

Even with the serach-link I didn't found any solution.
But if I run "upgrade --repair", will all domains, mails,.... be kept or will they be deleted?

Thanks for your help.
bye
Holger

 

[IgorG]

Check this article too https://kb.odin.com/en/127983

 

[Holger]

Yes,
I've checked this article several times.
But as you see
[root@vxxxx ~]# rpm -qa | grep mysqlclient | xargs rpm -q --queryformat '%{RELEASE}\n'
2.el6.art

is the actual version of mysqlclient.
And executing "bootstrapper" should do the same like "plesk repair installation".
"plesk repair db" or "plesk repair mysql" didn't give any errors.

But I'll do a "bootstrapper" again this afternoon.

Bye
Holger

 

[Holger]

Hi,

the rerun of bootstrapper brings the following error:
taskId=2015-06-29-10-12-53 step=upgrade result=1 message=ERROR: Zend_Db_Statement_Exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry &#039;1-server-backup_ftp_settingactive&#039; for key &#039;id&#039; (Pdo.php:234)<br />
<br><a href='http://kb.odin.com/plesk-error/sear...nstraint+violation:++Duplicate+entry++for+key' target='_blank'>Search for related Knowledge Base articles</a>Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.

But wich programm should I run in "repair"-mode ?
I restartet bootstrapper twice with the following argument:
/usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/bootstrapper.sh repair

Here is the whole
[root@vxxxx /]# cat /var/log/plesk/install/plesk_12.5.30_repair.log
START Bootstrapper 12.5.30 repair AT Thu Jan 28 16:31:54 CET 2016

**** 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... mysqld (PID 25044) wird ausgeführt ...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 012005030
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.12.5.30-12.5.30.20160128-163154.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.12.5.30-12.5.30.20160128-163202.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Trying to reset database user password for 'pma_hjVERCu3FZqN@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).

Trying to reset database user password for 'pp_sb_db@vxxxx'... done
Trying to reset database user password for 'horde@localhost'... done
Trying to reset database user password for 'atmail@localhost'... done
Trying to reset database user password for 'pma_hjVERCu3FZqN@localhost'... 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: JoomlaAdmin@localhost, ibbjoadmin@localhost, sv_joadmin@localhost, mrbs_db@localhost, evalDBadm@localhost, agbdidakt12@localhost, sogoadm@localhost, funambol@localhost, agbdidaktV21@localhost, LXCAdmin@localhost.
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 012005030... 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 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.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
[2016-01-28 16:32:08] ERR [panel] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-server-backup_ftp_settingactive' for key 'id':
0: /usr/local/psa/admin/externals/Zend/Db/Statement/Pdo.php:234
Zend_Db_Statement_Pdo->_execute(array)
1: /usr/local/psa/admin/externals/Zend/Db/Statement.php:300
Zend_Db_Statement->execute(array)
2: /usr/local/psa/admin/plib/Upgrade/Task/12.1.26/2015-06-29-10-12-53_UpdateBackupFtpStorageSettings.php:37
Plesk\Upgrade\Task\UpdateBackupFtpStorageSettings->upgrade(object of type Plesk\Upgrade\Deferred)
3: /usr/local/psa/admin/plib/Upgrade/Executor/Sync.php:15
Plesk\Upgrade\Executor_Sync->upgrade(string '2015-06-29-10-12-53', object of type Plesk\Upgrade\TaskLoader, object of type Plesk\Upgrade\Deferred)
4: /usr/local/psa/admin/plib/Upgrade/Command/Task.php:46
Plesk\Upgrade\Command_Task->run(string '2015-06-29-10-12-53', string 'upgrade')
5: /usr/local/psa/admin/plib/Upgrade/upgrade.php:19

taskId=2015-06-29-10-12-53 step=upgrade result=1 message=ERROR: Zend_Db_Statement_Exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry &#039;1-server-backup_ftp_settingactive&#039; for key &#039;id&#039; (Pdo.php:234)<br />
<br><a href='http://kb.odin.com/plesk-error/sear...nstraint+violation:++Duplicate+entry++for+key' target='_blank'>Search for related Knowledge Base articles</a>Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.



Thanks for any help
bye
Holger

 

[Holger]

and the second output( first post was more than 10000 characters:


WARNING!
Some problems are found during execute post install/upgrade actions(see log file: /var/log/plesk/install/plesk_12.5.30_repair.log)

Continue...

===> 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 and repair SpamAssassin service configuration... Upgrade or repair for 'spamassassin' (stage 'files') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (prep stage)... Upgrade or repair for 'courier_imap' (stage 'prep') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (post stage)... Upgrade or repair for 'courier_imap' (stage 'post') is not required
done
Trying to upgrade and repair Courier-IMAP services configuration (bootstrapper-post stage)... Upgrade or repair for 'courier_imap' (stage 'bootstrapper-post') is not required
done
Trying to condrestart service courier-imapd... done
Trying to condrestart service courier-imaps... done
Trying to condrestart service courier-pop3d... done
Trying to condrestart service courier-pop3s... done
Trying to upgrade and repair Roundcube webmail configuration... Upgrade or repair for 'roundcube' (stage 'files') is not required
done
Upgrade of Roundcube Web Based mail client configs and DB is not required - no previous version
Trying to upgrade and repair Horde webmail configuration... Upgrade or repair for 'horde' (stage 'files') is not required
done
Trying to upgrade and repair Firewall service configuration... Upgrade or repair for 'firewall' (stage 'post') is not required
done
Trying to stop service named... version: 9.8.2rc1-RedHat-9.8.2-0.37.rc1.el6_7.5 (none)
CPUs found: 12
worker threads: 2
number of zones: 27
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (PID 27904) wird ausgeführt ...
Named beenden: . [ OK ]
done
Trying to start service named... named wurde beendet
Named starten: [ OK ]
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: mail_imap_restore... ok
==> 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... not found, skipped
==> Checking for: mail_outgoing_restore... ok
==> Checking for: mail_transport_restore... ok
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Trying to register service sw-cp-server... done
Trying to register service sw-engine... done
Trying to register service courier-imapd... done
Trying to register service courier-imaps... done
Trying to register service courier-pop3d... done
Trying to register service courier-pop3s... done
Trying to register service spamassassin... done
Trying to register service pc-remote... done
Reconfiguring SSL ciphers and protocols...
Trying to configure SSL ciphers and protocols... done
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
Errors occurred while performing the following actions: cumulative Plesk upgrade and repair revertible stage, upgrade Plesk business logic.
Check '/var/log/plesk/install/plesk_12.5.30_repair.log' and '/var/log/plesk/install/plesk_12.5.30_repair_problems.log' for details.
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: JoomlaAdmin@localhost, ibbjoadmin@localhost, sv_joadmin@localhost, mrbs_db@localhost, evalDBadm@localhost, agbdidakt12@localhost, sogoadm@localhost, funambol@localhost, agbdidaktV21@localhost, LXCAdmin@localhost.
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 12.5.30 repair AT Thu Jan 28 16:34:07 CET 2016


===========================================================

[root@vxxxx /]# cat /var/log/plesk/install/plesk_12.5.30_repair_problems.log
START Bootstrapper 12.5.30 repair AT Thu Jan 28 16:31:54 CET 2016
***** 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: JoomlaAdmin@localhost, ibbjoadmin@localhost, sv_joadmin@localhost, mrbs_db@localhost, evalDBadm@localhost, agbdidakt12@localhost, sogoadm@localhost, funambol@localhost, agbdidaktV21@localhost, LXCAdmin@localhost.
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 12.5.30 repair AT Thu Jan 28 16:34:07 CET 2016: PROBLEMS FOUND

 

[trialotto]

@Holger,

I am pretty sure that the bootstrapper/repair issue is unrelated to your original problem: after all, the bootstrapper/repair problems arise with

Currently following users have passwords in old format: JoomlaAdmin@localhost, ibbjoadmin@localhost, sv_joadmin@localhost, mrbs_db@localhost, evalDBadm@localhost, agbdidakt12@localhost, sogoadm@localhost, funambol@localhost, agbdidaktV21@localhost, LXCAdmin@localhost.

and those are not really relevant Plesk users, if you have a problem when logging into Plesk Panel as admin.

That leaves us with the "blank screen" issue, at least that is what you are essentially indicating to be the original problem.

In order to resolve that issue, you could have a look at various KB articles:

a) KB #127983; you already did that and that was not succesful, but as such, that is very likely to be an important result (!)
b) KB #120715: admin password related issues,
c) KB #127211: package conflicts or duplicates,
d) some other articles.

In essence, the information in your first post is not enough too exclude some potential causes for the original problem.

Please follow the steps below (in chronological order):

1 - verify that /etc/sysconfig/i18n contains: LANG = en_US.utf8 (or en_US.UTF-8)
2 - verify that duplicate packages are not present, run: package-cleanup --dupes
3 - delete any duplicate packages, run: package-cleanup --cleandupes (note: you can combine steps 2 and 3, but I would strongly advice to do a "visual inspection", i.e. do two steps)
4 - verify that the admin password can be returned, run: /usr/local/psa/bin/admin --show-password
5 - do a restart of the service: service psa restart (or /etc/init.d/psa restart)
6 - try to access Plesk Panel again, if not succesful, run: plesk repair installation

and try to keep track of output at every step.

Please present some of the output (please attach files to your post), if the steps above do result in some error of any kind.

Regards......

 

[Holger]

Hi,

here are the outputs:
[root@vxxx sysconfig]# package-cleanup --dupes
Geladene Plugins: fastestmirror, priorities
[root@vxxx sysconfig]# package-cleanup --problems
Geladene Plugins: fastestmirror, priorities
No Problems Found
[root@vxxx sysconfig]# /usr/local/psa/bin/admin --show-password
<CORRECT_PASSWORD>
[root@vxxx sysconfig]# /etc/init.d/psa restart
Stopping sw-engine-fpm: [ OK ]
Starting sw-engine-fpm: [ OK ]


Reconfiguring the Plesk installation

Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
Stopping psa... done

**** 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... mysqld (pid 3858) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 012005030
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.12.5.30-12.5.30.20160129-105238.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.12.5.30-12.5.30.20160129-105250.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Trying to reset database user password for 'pma_hjVERCu3FZqN@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).

Trying to reset database user password for 'pp_sb_db@vxxx'... done
Trying to reset database user password for 'horde@localhost'... done
Trying to reset database user password for 'atmail@localhost'... done
Trying to reset database user password for 'pma_hjVERCu3FZqN@localhost'... 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: JoomlaAdmin@localhost, ibbjoadmin@localhost, sv_joadmin@localhost, mrbs_db@localhost, evalDBadm@localhost, agbdidakt12@localhost, sogoadm@localhost, funambol@localhost, agbdidaktV21@localhost, LXCAdmin@localhost.
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.

===> Plesk database was not upgraded completely. See installation log for details.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.

**** Product repair started.


==> continued in next message

 

[Holger]

===> 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... mysqld (pid 3858) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 012005030
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.12.5.30-12.5.30.20160129-105238.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.12.5.30-12.5.30.20160129-105250.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Trying to reset database user password for 'pma_hjVERCu3FZqN@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).

Trying to reset database user password for 'pp_sb_db@v45443'... done
Trying to reset database user password for 'horde@localhost'... done
Trying to reset database user password for 'atmail@localhost'... done
Trying to reset database user password for 'pma_hjVERCu3FZqN@localhost'... 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: JoomlaAdmin@localhost, ibbjoadmin@localhost, sv_joadmin@localhost, mrbs_db@localhost, evalDBadm@localhost, agbdidakt12@localhost, sogoadm@localhost, funambol@localhost, agbdidaktV21@localhost, LXCAdmin@localhost.
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 012005030... 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 20111115171314-upgrade_mysqlnd_old_passwd 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.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
[2016-01-29 10:52:55] ERR [panel] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-server-backup_ftp_settingactive' for key 'id':
0: /usr/local/psa/admin/externals/Zend/Db/Statement/Pdo.php:234
Zend_Db_Statement_Pdo->_execute(array)
1: /usr/local/psa/admin/externals/Zend/Db/Statement.php:300
Zend_Db_Statement->execute(array)
2: /usr/local/psa/admin/plib/Upgrade/Task/12.1.26/2015-06-29-10-12-53_UpdateBackupFtpStorageSettings.php:37
Plesk\Upgrade\Task\UpdateBackupFtpStorageSettings->upgrade(object of type Plesk\Upgrade\Deferred)
3: /usr/local/psa/admin/plib/Upgrade/Executor/Sync.php:15
Plesk\Upgrade\Executor_Sync->upgrade(string '2015-06-29-10-12-53', object of type Plesk\Upgrade\TaskLoader, object of type Plesk\Upgrade\Deferred)
4: /usr/local/psa/admin/plib/Upgrade/Command/Task.php:46
Plesk\Upgrade\Command_Task->run(string '2015-06-29-10-12-53', string 'upgrade')
5: /usr/local/psa/admin/plib/Upgrade/upgrade.php:19

taskId=2015-06-29-10-12-53 step=upgrade result=1 message=ERROR: Zend_Db_Statement_Exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry &#039;1-server-backup_ftp_settingactive&#039; for key &#039;id&#039; (Pdo.php:234)<br />
<br><a href='http://kb.odin.com/plesk-error/sear...nstraint+violation:++Duplicate+entry++for+key' target='_blank'>Search for related Knowledge Base articles</a>Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.


WARNING!
Some problems are found during execute post install/upgrade actions(see log file: /var/log/plesk/install/plesk_12.5.30_repair.log)

Continue...

===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
rndc: connect failed: 127.0.0.1#953: connection refused
Reconfiguring mail subsystem...

Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Reconfiguring SSL ciphers and protocols...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
Errors occurred while performing the following actions: cumulative Plesk upgrade and repair revertible stage, upgrade Plesk business logic.
Check '/var/log/plesk/install/plesk_12.5.30_repair.log' and '/var/log/plesk/install/plesk_12.5.30_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Parallels support.
***** 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: JoomlaAdmin@localhost, ibbjoadmin@localhost, sv_joadmin@localhost, mrbs_db@localhost, evalDBadm@localhost, agbdidakt12@localhost, sogoadm@localhost, funambol@localhost, agbdidaktV21@localhost, LXCAdmin@localhost.
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.

exit status 1


NO SUCCESS

 

[trialotto]

@Holger,

You seem to have forgotten one step: set the language to en_US.

This would prevent any problems being the result of locale settings (in your case, "umlauts" and such alike).

Please redo the steps and make certain that your system is on an English based locale setting.

In the meantime, you could also consider (in chronological order)

- to access the relevant database by going to "Tools & Settings > Database Server > DB Webadmin" (note: it is the button on the right of the line concerning the default dbase)
- have a look at "information schema > Global_Variables", the values of innodb_version and lc_time_names (this is indicates the language setting, should be en_US with locale en_US)
- have a look at "db > mysql", which should display some of the <user>@localhost "users" that cause the bootstrapper/repair issue
- have a look at "psa > admin_aliases", which should be empty
- have a look at "psa > db_users", which should not contain before mentioned <user>@localhost "users"
- have a look at "psa > accounts", which should contain some passwords.......verify whether some strange entries are present.

Do NOT change values in the (default) database, first try to redo the steps with a locale set to en_US.

However, if you see some strange things in the database, please report them.

Regards....

 

[Holger]

Hi,

sorry,I didn't wrote that I've changed "LANG" in /etc/sysconfig/i18n in the first step.
[root@vxxx ~]# cat /etc/sysconfig/i18n
LANG="en_US.UTF-8"
SYSFONT="latarcyrheb-sun16"

[root@vxxx ~]# env|grep LANG
LANG=en_US.UTF-8

and i did your mentioned steps in order.

To your last post:
how could I do "Tools & Settings > Database Server > DB Webadmin" if I couldn't connect to plesk panel?

bye
Holger

 

[trialotto]

@Holger,

To your last post: how could I do "Tools & Settings > Database Server > DB Webadmin" if I couldn't connect to plesk panel?

You are right, apologies.

Try the following: login (even though the blank screen occurs) and change the URL to https://<ip of server>:8443/server/db_servers.php?cmd=dbwebadmin&db_server_id=1

This in the hope that your credentials were good and remembered by the browser, in such a way that you are still allowed access to the database server.

Note "dbwebadmin" is for Ubuntu, it should also apply for CentOS, if I am not mistaken.

Regards....

PS The SYSFONT="latarcyrheb-sun16" can cause some issues, you can try to alter that to SYSFONT="lat0-16" or SYSFONT="lat9v-12".

 

[Holger]

Hi,

changing the URL works!
I've installed Webmin in parallel and with webmin I can access the databases too.
Or via commandline "mysql -uadmin -p`cat /etc/psa/.psa.shadow`" I could list all databases and tables.

I have to translate, because everything in phpMyAdmin is written in german ;-)

- have a look at "information schema > Global_Variables", the values of innodb_version and lc_time_names (this is indicates the language setting, should be en_US with locale en_US)

==> innodb version 5.5.47
lc time names en_US

- have a look at "db > mysql", which should display some of the <user>@localhost "users" that cause the bootstrapper/repair issue

==> Yes, the are all displayed with "short" passwords

- have a look at "psa > admin_aliases", which should be empty

==> Yes, is empty

- have a look at "psa > db_users", which should not contain before mentioned <user>@localhost "users"

==> Yes (or no). None of the above users are in this table.


- have a look at "psa > accounts", which should contain some passwords.......verify whether some strange entries are present.

==> Hmmmm. The first entry "ID: 1" contains: ID: 1 type: "crypt" password: "$5$i0M/Hc......<CUT BY ME>"
while most other entries are of the form: type: "sym" password: "$AES-128-....<CUT BY ME>"
There are two entries with type "plain" and no password.
In summary there are four entries with type "crypt".

Could this be the problem?

Thanks and bye
Holger

 

[trialotto]

@Holger,

Again, the "blank screen" issue is very likely to be unrelated OR (only) indirectly related to the bootstrapper/repair issue.

I am pretty sure that the root cause of your original problem (i.e. the blank screen) is also causing the bootstrapper/repair issue.

That is a "challenge", since the normal option of running "plesk repair installation" (i.e. enforcing proper installation) is not available at this moment.

What we are looking for is a way to bypass the bootstrapper/repair issue, in order to allow you to run a "plesk repair installation" (or autoinstaller command via the command line).

First, what do you mean by

==> Yes, the are all displayed with "short" passwords

and can you give an example?

In the meantime, let´s try the following:

a) first run the command: plesk bin admin --set-password -passwd <mypassword> -encrypted-password (i.e. choose a value for <mypassword>)

b) check whether the "blank screen" issue is resolved

c) if not, first try to change SYSFONT and retry the steps I presented earlier.....

Hope the above helps......after all, we have two issues to resolve.

Regards....

 

[Holger]

Hi,

ok, I've startet with changing SYSFONT:
[root@vxxxx sysconfig]# cat i18n
LANG="en_US.UTF-8"
SYSFONT="lat0-16"
[root@vxxx sysconfig]# /etc/init.d/psa restart
Stopping sw-engine-fpm: [ OK ]
Starting sw-engine-fpm: [ OK ]

Here are two examples for users in "mysql -> user":

User: agbdidakt Password: *C76740......<CUT BY ME> (41 characters, this should be the normal one)
User: ibbjoadmin Password: 0cd752.....<CUT BY ME> (16 characters)

The last user is mentioned in the error log.

a) first run the command: plesk bin admin --set-password -passwd <mypassword> -encrypted-password

==> The Plesk administrator's password was successfully updated.

No luck. Still "file not found".
I've change the passwort to an very new one without any special chars, because the old uses "spezial characters" like "!" and "&".
"/usr/local/psa/bin/admin --show-password" shows the new password.

Now I restart again with bootstrapper.
No luck. Just the same messages like above. And just "file not found".

Just for your info, but this is normal for "file not found" (/var/log/plesk/httpsd_access_log):
<MY_IP> - - [30/Jan/2016:07:51:36 +0100] "GET /admin/ HTTP/1.1" 404 27 "https://<MY_SERVER>:8443/login_up.php3" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0" "-"'/admin/' '' '/usr/local/psa/admin/htdocs'

[root@vxxxx plesk]# ls -l /usr/local/psa/admin/htdocs
total 540
-rw-r--r-- 1 root root 588 Aug 26 15:16 application.php
drwxr-x--- 2 root psaadm 4096 Aug 5 2013 archives
drwxr-xr-x 2 root root 4096 Aug 26 15:16 backup
-rw-r--r-- 1 root root 318 Feb 18 2013 bu_pubkey.txt
-rw-r--r-- 1 root root 10499 Aug 26 15:16 check-plesk.php
-rw-r--r-- 1 root root 2372 Aug 26 15:16 ch_pass_by_secret.php
drwxr-xr-x 2 root root 4096 Dec 22 20:22 clients
-rw-r--r-- 1 root root 8404 Aug 26 15:16 cligate.php
drwxr-xr-x 2 root root 4096 Dec 22 20:22 creation_templates
drwxr-xr-x 4 root root 4096 Dec 22 20:24 domains
drwxr-xr-x 3 root root 4096 Dec 22 20:24 enterprise
-rw-r--r-- 1 root root 5430 Aug 26 15:16 favicon.ico
drwxr-xr-x 5 root psaadm 4096 Feb 22 2013 FtpUserEdit
-rw-r--r-- 1 root root 4691 Aug 26 15:16 get_password.php
-rw-r--r-- 1 root root 5596 Jan 27 11:32 help.php
drwxr-xr-x 6 root root 4096 Dec 22 20:22 images
-rw-r--r-- 1 root root 2780 Aug 26 15:16 index.php
drwxr-xr-x 3 root root 4096 Jan 27 11:32 javascript
-rw-r--r-- 1 root root 1972 Aug 26 15:16 license.php3
drwxr-xr-x 2 root root 4096 Dec 22 20:22 locales
-rw-r--r-- 1 root root 1076 Aug 26 15:16 login.php3
-rw-r--r-- 1 root root 9668 Aug 26 15:16 login_up.php3
-rw-r--r-- 1 root root 6828 Aug 26 15:16 logout.php3
-rw-r--r-- 1 root root 10410 Dec 16 08:14 migration.log
drwxr-xr-x 6 root root 4096 Aug 26 15:16 modules
-rw-r--r-- 1 root root 349978 Aug 26 15:16 msrdp.cab
-rw-r--r-- 1 root root 1420 Aug 26 15:16 plesk.php
drwxr-xr-x 4 root root 4096 Aug 26 15:21 schemas
drwxr-xr-x 3 root root 4096 Jan 27 11:32 server
drwxr-xr-x 2 root root 4096 Dec 22 20:24 sessions
drwxr-xr-x 4 root root 4096 Aug 5 2013 skins
drwxr-xr-x 12 root root 4096 Dec 22 20:24 spaw
drwxr-xr-x 2 root root 4096 Dec 22 20:24 sshterm
drwxr-xr-x 2 root root 4096 Dec 22 20:22 sso
drwxr-xr-x 5 root root 4096 Dec 22 20:24 theme
drwxr-xr-x 2 psaadm psaadm 4096 Aug 26 15:16 theme-skins
-rw-r--r-- 1 root root 1388 Aug 26 15:16 vzcp_redirect.php
drwxr-xr-x 2 root root 4096 Dec 22 20:22 whp



Could this be a hint to find the problem (/var/log/plesk/panel.log):
[2016-01-30 07:47:17] ERR [panel] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-server-backup_ftp_settingactive' for key 'id':
0: /usr/local/psa/admin/externals/Zend/Db/Statement/Pdo.php:234
Zend_Db_Statement_Pdo->_execute(array)
1: /usr/local/psa/admin/externals/Zend/Db/Statement.php:300
Zend_Db_Statement->execute(array)
2: /usr/local/psa/admin/plib/Upgrade/Task/12.1.26/2015-06-29-10-12-53_UpdateBackupFtpStorageSettings.php:37
Plesk\Upgrade\Task\UpdateBackupFtpStorageSettings->upgrade(object of type Plesk\Upgrade\Deferred)
3: /usr/local/psa/admin/plib/Upgrade/Executor/Sync.php:15
Plesk\Upgrade\Executor_Sync->upgrade(string '2015-06-29-10-12-53', object of type Plesk\Upgrade\TaskLoader, object of type Plesk\Upgrade\Deferred)
4: /usr/local/psa/admin/plib/Upgrade/Command/Task.php:46
Plesk\Upgrade\Command_Task->run(string '2015-06-29-10-12-53', string 'upgrade')
5: /usr/local/psa/admin/plib/Upgrade/upgrade.php:19
[2016-01-30 07:47:17] ERR [1] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-server-backup_ftp_settingactive' for key 'id'

bye and thanks
Holger

PS: Hope I don't have to reinstall the whole maschine

 

[trialotto]

@Holger,

We can exclude some common problems now.

Another obvious cause of the problem is: configuration of the unique Nginx (web)server that Plesk uses for it´s Panel.

Some questions:

- Can you post the line from /etc/sw-cp-server/config, starting with error_page 497 ... ?
- Do you have an agent.conf file in /etc/sw-cp-server/conf.d? If so, provide the contents of that file (and remove it afterwards and try to login)
- Can you have a look at /etc/sw-cp-server/conf.d/plesk.inc, the parts for "location /admin" and "location @route"
- Can you verify that, in "location @route", the path to ..sw-engine.sock is correct and that the "file" sw-engine.sock is existing?
- Can you verify that, in "location @route", the path to ..application.php is correct?

Regards

 

[Holger]

Hi,

Can you post the line from /etc/sw-cp-server/config, starting with error_page 497 ... ?

Hmmm. No line in this file starts with "error_page".
Here ist the contents:
[root@vxxx sw-cp-server]# cat config

worker_processes 1;
events {
worker_connections 1024;
}

http {
include mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"'
"'$fastcgi_script_name' '$fastcgi_path_info' '$document_root'";

sendfile on;
reset_timedout_connection on;
#keepalive_timeout 0;
keepalive_timeout 65;
#tcp_nodelay on;
#gzip on;
#gzip_disable "MSIE [1-6]\.(?!.*SV1)";

server_tokens off;
fastcgi_max_temp_file_size 0;
fastcgi_buffers 32 32k;
fastcgi_buffer_size 64k;

fastcgi_read_timeout 600;
fastcgi_send_timeout 600;

client_max_body_size 2048m;
include /etc/sw-cp-server/conf.d/*.conf;
}

Note: I didn't change anything in this file.
-rw-r--r-- 1 root root 903 Nov 8 2013 /etc/sw-cp-server/config

Do you have an agent.conf file

No. There is no file with this name. I didn't delete it. It wasn't there before.
I've read the KB-article with "removing this file" before. ;-)

Can you have a look at /etc/sw-cp-server/conf.d/plesk.inc

# Admin panel
location /admin {
alias /usr/local/psa/admin/panel/application/public;
try_files $uri @admin;
}

location @admin {
include /etc/sw-cp-server/fastcgi_params;
fastcgi_pass unix:/var/run/sw-engine.sock;
fastcgi_param PATH_INFO /admin/$fastcgi_path_info;
fastcgi_param SCRIPT_FILENAME /usr/local/psa/admin/panel/application/public/index.php;
}

AHHHHH !!!!!
/usr/local/psa/admin/panel/application/public doesn't exist !!!!
even /usr/local/psa/admin/panel/application/public/index.php doesn't exist !!!

[root@vxxx sw-cp-server]# ls -l /usr/local/psa/admin
total 11816
drwxr-xr-x 6 root root 4096 Dec 22 20:22 application
drwxr-x--- 2 root psaadm 4096 Aug 6 2013 archives
drwxr-xr-x 2 root root 4096 Aug 5 2013 auto_prepend
drwxr-xr-x 3 root root 4096 Jan 27 11:32 bin
drwxr-xr-x 2 root root 4096 Dec 22 20:24 common
drwxr-xr-x 5 root root 4096 Jan 30 04:34 conf
drwxr-xr-x 2 root root 4096 Dec 22 20:22 db
drwxr-xr-x 8 root root 4096 Dec 22 20:24 externals
drwxr-xr-x 23 root root 4096 Jan 27 11:32 htdocs
drwxr-xr-x 3 root root 4096 Aug 26 15:21 lib
drwxr-x--- 2 psaadm root 4096 Dec 22 20:28 logs
drwxr-xr-x 3 root psaadm 4096 Dec 30 04:04 man
-rw-r--r-- 1 root root 12000224 Jan 30 00:30 migration.log
drwxr-xr-x 101 root root 20480 Jan 27 11:32 plib
drwxr-xr-x 3 root root 4096 Jan 27 11:32 sbin
drwxr-xr-x 6 root root 4096 Dec 22 20:24 services
drwxrwx--- 2 psaadm psaadm 4096 Aug 26 15:16 sessions
drwxr-xr-x 10 root root 4096 Dec 22 20:24 share
drwxr-xr-x 3 root root 4096 Aug 26 15:16 smb
drwxrwxrwx 2 root root 4096 Aug 26 15:16 tmp

- Can you verify that, in "location @route", the path to ..sw-engine.sock is correct and that the "file" sw-engine.sock is existing?
- Can you verify that, in "location @route", the path to ..application.php is correct?

None of these options exists in /etc/sw-cp-server/conf.d/plesk.inc
-rw-r--r-- 1 root root 2077 Aug 19 2013 /etc/sw-cp-server/conf.d/plesk.inc

It seems that this file is corrupted, because it doesn't start wird a comment or so.

If these files and directories are not ok, is there the possibility to download them at a secure site?

BTW., I have checked the system with "rkhunter" and "chkconfig", but for luck no reported hacks.

I hope I'm just before the "finish line" ;-)

bye and thanks
Holger

 

[Holger]

One additional information.
I've a backup (from December 2015) with the missing directories.

Could I extract the missing dirs directly?
Bye
Holger

 

[trialotto]

@Holger,

Ehm, let´s first answer the question in your latest response: no, it is best to not revert the backup (since that will generate a number of new problems).

First of all, note that you have multiple problems, but we will tackle the Plesk Panel "blank screen" issue first (and continue with the remainder of issues afterwards).

In summary, you stated:

- no agent.conf file: excellent,
- /etc/sw-cp-server/config file: incorrect contents,
- to have @admin instead of @route (note that this does not really make a difference, but we will change it)
- to have some directives in location @admin: incorrect contents,

and that is about it.

Now, you are indeed almost finished with the "blank screen" issue, if I am not mistaken.

Just follow these steps (in chronological order):

1) adjust /etc/sw-cp-server/config to contain

error_page 497 https://$hostname:$server_port$request_uri;

just before the line with "include /etc/sw-cp-server/conf.d/*.conf;"

Note that you have customized the default values for fastcgi_buffers (by default: 16 16k) and fastcgi_buffer_size (by default: 32k) and more is not necessary. Please revert the values.

2) for the sake of convenience (and Nginx configuration), change (every) @admin to @route in the /etc/sw-cp-server/conf.d/plesk.inc file

3) also in the /etc/sw-cp-server/conf.d/plesk.inc file, change the contents of location @route (previously: location @admin) to be equal to

location @route {
include /etc/sw-cp-server/fastcgi_params;
fastcgi_pass unix:/var/run/sw-engine.sock;
fastcgi_param PATH_INFO /admin/$fastcgi_path_info;
fastcgi_param SCRIPT_FILENAME /opt/psa/admin/htdocs/application.php;
fastcgi_param HTTP_PRAGMA $http_pragma;
}

4) execute the command: /etc/init.d/sw-cp-server restart

This should resolve your most major issue, being the "blank screen".

Note that step 1 alone should be sufficient to resolve your "blank screen" issue, but since we are busy rectifying some configuration errors, the other steps were also given.

However, some additional issues with your Plesk instance can (still) be expected to occur, please do not run a "plesk repair installation" yet.

First report the results of implementation of the 4 steps above.

By the way, verify that you indeed have the /opt/psa/admin/htdocs/application.php file (I am pretty sure that you have that).

Regards.....