Semaphore error on everything!

[ShoneA]

This is totally my fault. We were trying to diagnose a network glitches (long story short) I ended up running killall -9 php to close down 4 php processes that I thought were knocking our office offline (they weren't). Ever since then our control panel wont load, and any Plesk command line operations we run (including the installer/updater I think) result in an "unable to acquire semaphore" error. Is there a way to fix this via some sort of command or do I HAVE to pay Plesk support to fix it? Thanks.

This is our control panel login error:

ERROR: PleskFatalException
Up Level
Unable to acquire semaphore: Declaration of Skin::initFromSubmit() should be compatible with that of cObject::initFromSubmit()
0: common_func.php3:8
lock_level(string 'SEM_SERVICE_NODE_PROPERTIES')
1: Semaphore.php:16
Semaphore::lock(string 'SEM_SERVICE_NODE_PROPERTIES')
2: Properties.php:146
Service_Node_Properties->sync(NULL null, boolean false)
3: Components.php:20
Service_Node_Components->sync()
4: Properties.php:32
Service_Node_Properties->__construct(object of type Db_Table_Row_ServiceNode)
5: ServiceNode.php:185
Db_Table_Row_ServiceNode->components()
6: ServiceNode.php:88
Db_Table_Row_ServiceNode->refreshProperties()
7: auth.php3:505

EDIT: I'm not seeing any semaphore related errors in the autoinstaller log file. Maybe it's possible to do a full upgrade of the panel? I might just break it more though. Everything is operational except for the panel itself right now.

 

[IgorG]

Have you tried restart psa service at least?

 

[ShoneA]

Oh yeah, I've tried some basic things such as:

- Restarting PSA
- Rebooting the server
- Installing Micro-updates (I think they were successful but I can't remember for sure.)

 

[IgorG]

What about bootstrapper repair procedure?

 

[ShoneA]

The bootstrapper repair doesn't seem to return anything:

srv:/usr/local/psa/bootstrapper/pp10.13.4-bootstrapper # /usr/local/psa/bootstrapper/pp10.13.4-bootstrapper/bootstrapper.sh repair
srv:/usr/local/psa/bootstrapper/pp10.13.4-bootstrapper #

No log file is returned in the /tmp directory either to find out why this has happened...

 

[ShoneA]

I got the crazy idea to try the Plesk 11 bootstrapper repair that for some reason exists on this server, and it actually did things but didn't fix our errors:

srv:/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper # dir
total 288
-rwxr-xr-x 1 root root 284457 Jun 8 01:44 bootstrapper.sh
drwxr-xr-x 3 root root 4096 Jun 13 10:39 db
-rw-r--r-- 1 root root 2644 Jun 8 01:30 psa.conf.default
srv:/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper # ./bootstrapper.sh repair
Changing login shell for popuser.
Shell not changed.
Changing login shell for mhandlers-user.
Shell not changed.
===> Preparing upgrade
mysqldump: Got error: 1049: Unknown database 'horde' when selecting the database
redirecting to systemctl
psa.service - LSB: Start the Plesk Server Administrator
Loaded: loaded (/etc/init.d/psa)
Active: inactive (dead) since Tue, 16 Oct 2012 11:25:41 -0700; 401ms ago
Process: 5473 ExecStop=/etc/init.d/psa stop (code=exited, status=0/SUCCESS)
Process: 28564 ExecStart=/etc/init.d/psa start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/psa.service
mysqldump: Got error: 1049: Unknown database 'horde' when selecting the database
===> Cumulative database upgrade has been started
===> Upgrade completed.
"headers" already present
mknod: `/srv/www/vhosts/chroot/dev/null': File exists
"suexec" already present
"perl" already present
"python" already present
"rewrite" already present
"SSL" already present
===> Cumulative upgrade has been started
===> Upgrade completed.
"dav" already present
"dav_fs" already present
"auth_digest" already present
"authz_user" already present
"dav_lock" already present
redirecting to systemctl
Stopping psa... done
Plesk: Stopping Mail Server... done
Stopping mailer service... not installed
Stopping mysql service... done
Stopping postgresql service... done
Stopping drwebd service... not installed
Stopping tomcat6 service... not installed
Stopping apache2 service... done
redirecting to systemctl

Congratulations!
All stages of the upgrade were successful.
psa is now running on your system.
To complete the system configuration process, please proceed to URL:
x
x
Use 'admin' and '<YOUR ADMIN PASSWORD>' as login name and password.

Further, use the following commands to start and stop the system:
/etc/init.d/psa start and
/etc/init.d/psa stop respectively.

localemng: error: locale ko-KR not exists
localemng: error: locale ko-KR not exists