• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk 11.0.9 Control Panel shows binary

M

Mschot

Guest
Parts of my control panel show as binary code in my browser (like: C �����D�); strangely not all pages do this (login is correct, some smb pages are correct but admin-home is showing binary). Any suggestions what I can do to get my Plesk up and running again?
 
Any related errors in /var/log/sw-cp-server/error_log ?
 
Nothing that actually correlates to all the times I tried to load the control panel, but there are a few messages (the invalid URLS are my tries to see what and what not I can load):


2012-08-06 16:22:15: (log.c.166) server started
2012-08-06 16:23:53: (connections.c.309) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 466: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
2012-08-06T16:31:56+02:00 ERR (3): File sharing list retrieval failed: sharing type=private, error=Naughty, not nice!
2012-08-06 17:46:24: (server.c.1543) server stopped by UID = 0 PID = 11781
2012-08-06 17:46:24: (log.c.166) server started
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 466: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
2012-08-06T18:33:13+02:00 ERR (3): Requested URL: /smb/settings/
2012-08-06T18:33:13+02:00 ERR (3): Invalid URL was requested.
2012-08-06T18:33:24+02:00 ERR (3): Requested URL: /smb/settings/databases
2012-08-06T18:33:24+02:00 ERR (3): Invalid URL was requested.
2012-08-06 18:36:15: (connections.c.309) SSL: 1 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
2012-08-06 18:52:44: (mod_fastcgi.c.2746) FastCGI-stderr: PleskBadURIException: Invalid URI: /plesk.php
 
Is it post-upgrade issue? Have you tried bootstrapper repair?
 
I have upgraded from 10.x to 11.0 a few weeks ago, but there could have been an auto-upgrade recently.

the bootstrapper repair gives the following errors:


Trying to untar named run-root directory structure...
ERROR while trying to untar named run-root directory structure
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again


===> Restoring database from backup /var/lib/psa/dumps/mysql.preupgrade.11.0.9-11.0.9.20120807-123101.dump.gz


**** Product repair failed.

***** problem report *****
ERROR while trying to untar named run-root directory structure
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again
STOP Bootstrapper 11.0.9 repair AT Tue Aug 7 12:31:17 CEST 2012
 
I got the run-root.tar file from an other server with the same plesk version and the bootstrapper repair now finishes without errors, but the problem remains....
 
Any solutions Plesk? Since I can't get to the database webadmin anymore this is becoming a risk for me, so any help would be appreciated.

Edit: the pages that get returned have a 500 Internal Server Error http code
 
Last edited by a moderator:
So far it's (at least temporarily) solved with a reboot of the server (not my favorite solution). php -v gave segmentation fault as only response, after reinstalling php5 it still did, so I rebooted the server as a last try attempt...
 
Try re-running the auto-installer this time through SHELL. May be it broke in the process of auto upgrading.
 
Back
Top