• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Cannot create subscription after update

Kajasheen

New Pleskian
I just updated to 11.5.30 from 11.0.9. Now I am not able to create new subscriptions.

The following error ist shown:
Code:
Error: Unable to update domain data: MySQL query failed: Unknown column 'uid' in 'field list'

I already tried running bootstrapper.sh repair. But neither the installation log nor the repair log show any problems with the database.

Code:
START Bootstrapper 11.5.30 repair AT Tue Nov 12 12:32:30 CET 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 mysql... done
 Trying to establish test connection... connected
done
 Trying to find psa database... version is 011005030
Version is OK, no need to create psa database.
 Trying to backup MySQL database... done
 MySQL databases are dumped to /srv/psa/dumps/mysql.preupgrade.11.5.30-11.5.30.20131112-123230.dump.gz
 Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).
 Trying to resolve hostname 's15395105.onlinehome-server.info' and validate its IP address... done

 Trying to set psa database version to 011005030... done
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> 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 /srv/psa/dumps/mysql.preupgrade.apsc.11.5.30-11.5.30.20131112-123233.dump.gz
===> Upgrade and repair of APS controller database has been completed.
done
 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 Horde webmail configuration... Upgrade or repair for 'horde' (stage 'files') is not required
done
 Trying to upgrade and repair Parallels Premium antivirus (DrWeb) service configuration (bootstrapper-prep stage)... Upgrade or repair for 'drweb' (stage 'bootstrapper-prep') is not required
done
 Trying to upgrade and repair Parallels Premium antivirus (DrWeb) service configuration (bootstrapper-post stage)... Upgrade or repair for 'drweb' (stage 'bootstrapper-post') is not required
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... ok
==> Checking for: mail_postfix_transport_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... 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.

Any suggestions what to do?
 
In file /usr/local/psa/bootstrapper/pp11.5.30-bootstrapper/db/psa_db.sql you can find in which tables filed 'uid' is used and check these tables in current psa database.
 
Back
Top