lucaegloff
From a windows workstation behind your sme server, open a browser to grc.com & do a port scan.
This will check to see if required ports are open eg 443 for server manager, 22 (or whatever you use) for ssh etc & so on.
Log in as root at the command line & show output of
service httpd-e-smith status
(Should be something like
run: /service/httpd-e-smith: (pid 2033) 12660s, normally down)
service httpd-admin status
(Should be something like
run: /service/httpd-admin: (pid 2017) 12683s, normally down; run: log: (pid 796) 13157s)
service sshd status
Did you make any changes, install software, upgrade the server etc 2 days or earlier ago ?
If so what changes ?
Can you access the text based server manager ?
To access that, Log in as root to command prompt,
type
console
then select server manager option
Use the tab key & cursor keys or mouse to move around.
Also look in the log files eg /var/log/messages
around the time you try to access services that are timing out
Also look in the specific log files for those services eg httpd-admin
eg cat /var/log/messages
It is a little more difficult to read them without access to the GUI server manager
Try issuing the command
htop
& review the output
this is a good way to list services & their status. You need to see if httpd-admin & sshd are running & so on.
As Charlie says there are many places & things to look at to determine where the problem lies, but got to start somewhere.
38 Replies
22419 Views