• 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

Plesk 8.4 Control Panel starts, but doesn't show panel

P

pmich

Guest
Hello
I've very strange problem:
I've reinstalled server with OpenSUSE 10.2 + Plesk 8.3. Next upgraded to 8.4 and migrated a few domains from other server. Everything works (vhosts & mail), but no page is shown at https://myserver:8443/.

# /etc/init.d/psa start
Starting xinetd service... done
Starting named service... done
Starting mysql service... done
Starting qmail service... done
Starting courier-imap service... done
Starting postgresql service... failed
Starting psa-spamassassin service... done
Syntax OK
Starting Plesk... done
Starting drwebd service... done

(PostgreSQL - no such license in Plesk, so it's not an error)
The strange is everything worked a few days and even now looks fine: any configuration errors (in logs), Plesk starts and works on server but webpage for control panel is dead.
Looking at other threads I did command:
sh -x /etc/init.d/psa start1
and that was shown:
------------------------------------------------------
+ PRODUCT_NAME=Plesk
+ PRODNAME=psa
+ PRODUCT_ROOT_D=/usr/local/psa
+ MYSQL_BIN_D=/usr/bin
+ daemon_name=httpsd
+ rc_d=/etc/init.d
+ '[' -f /etc/init.d/functions ']'
+ '[' -f /etc/sysconfig/network ']'
+ '[' -f /etc/sysconfig/psa ']'
+ test -s /etc/rc.status
+ . /etc/rc.status
++ LC_ALL=POSIX
++ export LC_ALL
++ test -z '' -o -z ''
+++ exec
+++ stty size
+++ read L C
+++ echo LINES=24 COLUMNS=80
++ eval LINES=24 COLUMNS=80
+++ LINES=24
+++ COLUMNS=80
++ test 24 -eq 0
++ test 80 -eq 0
++ export LINES COLUMNS
++ case ":$PATH:" in
++ test -t 1 -a xterm '!=' raw -a xterm '!=' dumb
++ esc=
++ extd=
++ warn=
++ done=
++ attn=
++ norm=
++ stat=
++ rc_done=..done
++ rc_running=..running
++ rc_failed=..failed
++ rc_missed=..missing
++ rc_skipped=..skipped
++ rc_dead=..dead
++ rc_unused=..unused
++ rc_unknown=..unknown
++ rc_done_up=..done
++ rc_failed_up=..failed
++ rc_reset=
++ rc_save=
++ rc_restore=
++ _rc_service=/etc/init.d/psa
++ _rc_status=0
++ _rc_status_all=0
++ _rc_todo=start1
++ test start1 = status
++ test -n start1
+ rc_reset
+ _rc_status=0
+ _rc_status_all=0
+ rc_check
+ _rc_status_ret=0
+ test 0 -eq 0
+ test 0 -eq 0
+ return
+ return 0
+ vza_file=/var/vzagent
++ cat /etc/psa/.psa.shadow
+ admin_passwd=removed_from_there ;)
+ lockdir=/var/lock/subsys
+ optional_service=postgresql
+ optional_service_wo_lock=psa-spamassassin
+ tomcat_service=tomcat5
+ httpd_service=apache2
+ named_service=named
+ start_sh=/usr/local/psa/admin/bin/httpsdctl
+ proccess=admin/bin/httpsd
+ LOCKDIR_AVAILABLE=No
+ '[' -e /var/vzagent ']'
+ service='named mysql qmail courier-imap'
+ OPENSSL_CONF=/usr/local/psa/admin/conf/openssl.cnf
+ export OPENSSL_CONF
+ LANG=C
+ export LANG
+ '[' -x /etc/init.d/xinetd ']'
+ inetd=xinetd
+ rc_syntax
+ test -z 24 -o -z 80
+ test -t 1 -a xterm '!=' raw -a xterm '!=' dumb
+ esc=
+ extd=
+ warn=
+ attn=
+ norm=
+ stat=
+ done=
+ rc_done=done
+ rc_started='already started'
+ rc_stopped='already stopped'
+ test -z 24 -o -z 80
+ test -t 1 -a xterm '!=' raw -a xterm '!=' dumb
+ esc=
+ extd=
+ warn=
+ attn=
+ norm=
+ stat=
+ done=
+ rc_done=done
+ rc_started='already started'
+ rc_stopped='already stopped'
+ rc_not_installed='not installed'
+ rc_failed=failed
+ setenv_mysql
++ get_my_cnf_param socket
++ local my_cnf cnf_files
++ cnf_files='/etc/my.cnf /etc/mysql/my.cnf /var/db/mysql/my.cnf'
++ for my_cnf in '${cnf_files}'
++ '[' -f /etc/my.cnf ']'
++ break
++ '[' -f /etc/my.cnf ']'
+++ perl -e '$p="socket";
undef $/; $_=<>; s/#.*$//gm;
/\[mysqld\](.*?)\[/sg;
$_=substr($1, rindex $1,"$p") and
/$p\s*=(.*)/m and print $1
' /etc/my.cnf
++ r=' /var/lib/mysql/mysql.sock'
++ echo /var/lib/mysql/mysql.sock
+ mysqlsock=/var/lib/mysql/mysql.sock
+ '[' -S /var/lib/mysql/mysql.sock ']'
+ MYSQL_UNIX_PORT=/var/lib/mysql/mysql.sock
+ export MYSQL_UNIX_PORT
+ case "$1" in
+ start1
+ echo -n 'Starting Plesk... '
Starting Plesk... + /usr/local/psa/admin/bin/httpsdctl start
+ ret=0
+ '[' 00 -eq 0 ']'
+ '[' -d /var/lock/subsys ']'
+ touch /var/lock/subsys/psa
+ /usr/local/psa/admin/bin/packagemng --set-dirty-flag
+ echo done
done
+ return 0
+ exit 0
------------------------------------------------------

In /usr/local/psa/admin/logs/httpsd_error_log there is:
[date] [notice] Apache configured -- resuming normal operations
[date] [notice] Accept mutex: sysvsem (Default: sysvsem)

In /usr/local/psa/admin/logs/httpsd_access_log there is also:
IP - - [23/Jun/2008:21:34:52 +0200] "\x16\x03\x01" 200 850
IP - - [23/Jun/2008:21:34:54 +0200] "\x80O\x01\x03" 200 850

Any idea what's wrong?
Thanks for any help

PMich
 
How Control Panel is not accessible? What error web-server gives in browser? What's the behavior -- is it just constantly loading and then falling with 'timeout' error or is there any particular error or blank screen?

Usually, when such things happen I use three simple steps:

1. Check firewall settings -- maybe port 8443 is blocked (useful for 'timeout' error)
2. Check any errors in /usr/local/psa/admin/logs/httpsd_error_log (especially looking for any 'Segmenation fault' messages)
3. turn on 'display_errors' in /usr/local/psa/admin/conf/php.ini to see detailed errors (if blank screen is given)

But with so little information right now it is hard to say what's wrong there.

Good luck,
 
Same problem

I also cannot access to control panel page. My browser (firefox) takes forever to load the page. I also have tried with Internet Explorer, it shows "Internet Explorer cannot display the webpage" and status bar show "Waiting for https://mydomain.com:8443/...".

Anyone please help.

I use FreeBSD 5.0.
 
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
 
Me too. After update fron 8.3 to 8.4 everything went well until I received an email telling me that the update to the Plesk key had failed whilst at the same time telling me that 1 additional key had been received. Plesk failed to restart so I restarted it from the command line without a problem. Unfortunately the problem wasn't far away.

On my first log in to the control panel I was informed that the key update had been unsuccessful and suggested manual update. I ran this and was presented with a success message showing me what was licensed.

The message had an OK button. You can guess what happened next. Like a fool I clicked it and immediately the control panel disappeared and was replaced by the following.

"The connection to https://myserver:8443 has terminated unexpectedly. Some data may have been transferred."
"The browser connected successfully, but the connection was interrupted while
transferring information. Please try again."

Since then everything works but port 8443. Could this be something to do with a bug in 8.4? I also have the same httpsd_error_log as above.

I contacted 1&1 who host my server but they just accused me of tampering with configuration files even though the timestamp showed this wasn't possible. As this seems to be more than a single incident maybe Parallels will look into it. Lets hope.

PS Yes I did post the dumb message of posting instructions. A bad habit as a forum I use regularly require you to click first and then type. Sorry.
 
Back
Top