Facebook
Twitter
M
ManuelR
Guest
Hello All,
It would seem that when I attempt to access my Plesk admin page this is unavailable. After doing some cursory checks I discovered that the server was not listening for incoming requests on port 8443 (verified remotely via telnet).
I therefore assumed that the service was not running and therefore issued the following command via SSH under the root account:
This results in the following output:
As a possibly related issue, today I experience a server outage for reasons yet unknown. As part of the investigation into this I used Plesk to reboot the server. This action completed successfully and was the last action I performed in Plesk. Since the reboot I can access all services other than plesk itself.
Having never encountered this issue before, and also being something of a newbie when it comes to administering a Linux based server, I have no idea where to go next? Is there are log file I can check for service start errors? Is the solution staring me in the face? Or maybe something else.
Thanks in advance
EDIT:
Something else that may or may not be relevant
After rebooting, and before attempting to access Plesk again I installed sysstat with yum in order to be able to use iostat. Other than that no other changes have been made to the server.
EDIT:
To cover all the bases I have asked this question elsewhere, the response I received was "I'm going to put my money on the partition containing /var being full.". So pursuing that the last entry in the /var/log/sw-cp-server/error_log file is
If I attempt to start Plesk with the command I mentioned earlier 2 new entries, the same as the one above, are added to the error log. I have found some reference to this error log entry and these relate to an updated version of SSL breaking plesk, however I have not (to my knowledge) updated SSL (unless the install of sysstat did this in the background??)
Output from df -h is:
So if I am reading that correctly there is loads of space available
EDIT
As the errors in the log seem to point to the issue that whose resolution is detailed here:
http://kb.odin.com/8338
I have followed the guidelines in that KB, with the following outputs
However, as you can see the service start still fails.
It would seem that when I attempt to access my Plesk admin page this is unavailable. After doing some cursory checks I discovered that the server was not listening for incoming requests on port 8443 (verified remotely via telnet).
I therefore assumed that the service was not running and therefore issued the following command via SSH under the root account:
This results in the following output:
As a possibly related issue, today I experience a server outage for reasons yet unknown. As part of the investigation into this I used Plesk to reboot the server. This action completed successfully and was the last action I performed in Plesk. Since the reboot I can access all services other than plesk itself.
Having never encountered this issue before, and also being something of a newbie when it comes to administering a Linux based server, I have no idea where to go next? Is there are log file I can check for service start errors? Is the solution staring me in the face? Or maybe something else.
Thanks in advance
EDIT:
Something else that may or may not be relevant
After rebooting, and before attempting to access Plesk again I installed sysstat with yum in order to be able to use iostat. Other than that no other changes have been made to the server.
EDIT:
To cover all the bases I have asked this question elsewhere, the response I received was "I'm going to put my money on the partition containing /var being full.". So pursuing that the last entry in the /var/log/sw-cp-server/error_log file is
If I attempt to start Plesk with the command I mentioned earlier 2 new entries, the same as the one above, are added to the error log. I have found some reference to this error log entry and these relate to an updated version of SSL breaking plesk, however I have not (to my knowledge) updated SSL (unless the install of sysstat did this in the background??)
Output from df -h is:
So if I am reading that correctly there is loads of space available
EDIT
As the errors in the log seem to point to the issue that whose resolution is detailed here:
http://kb.odin.com/8338
I have followed the guidelines in that KB, with the following outputs
However, as you can see the service start still fails.
Last edited by a moderator:
