Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SES working, but cannot access web interface 1

Status
Not open for further replies.

robi1306

Technical User
Apr 6, 2010
16
HR
Hello all,

I have an old SES server which is running, the SIP phones are registered and working, but the administration web interface cannot be loaded, I get "The server at xxx is taking too long to respond". This happens from time to time, but after a few days I can access it again.

I can login via SSH, but I am unfamiliar with commands. What can I do to reset the web service and access the server ?
 
no idea offhand. Maybe the services are named normal - like tomcat or httpd or maybe they're not.

If you've got root, you should be able to service --status-all. If you access on port 80 or 443, you should be able to netstat -tunap |grep 80 (or the same command grep 443) and see what process and ID is using that port.

Maybe it has 'statapp' like CM linux to tell you process state. You can use various start and stop commands to manage processes, but they're avaya specific and not linux in general, but they might be in SES. I've never worked on one.

Heck, do a 'uptime' and 'df -h' - maybe it's just been up too long or a disk volume filled to 100% with logs for some silly reason
 
Cannot opet the web interface again, The server at ... is taking too long to respond.

It was working a few days ago.

Anything out of the ordinary ?

sip_server_df-h_jz0e3t.png
sip_server_top_zowuob.png
 
that looks ok. got root? access by http/https? try netstat -tunap|grep 80 to see what's listening on 80. Same with 443
 
try Linux cli

ps -eaf | grep httpd

/sbin/service httpd status
/sbin/service httpd start
/sbin/service httpd stop


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
/sbin/service httpd status => httpd dead but subsys locked

/sbin/service httpd start =>

Starting httpd: Syntax error on line 92 of /etc/httpd/conf.d/01_ssl.conf:
SSLCertificateKeyFile: file '/etc/opt/ecs/certs/private/server.key' does not exist or is empty

missing SSL cert. any solution for an old ses ?
 
Update the RFA license file

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
I was told I cannot do any updates becase the hardware is too old.

S8500C servers for CM and SES.
 
Not updates, reinstall the license file.

"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top