topic Re: Server not Responding. in Operating System - HP-UX

Server not Responding.

Robjan — Fri, 18 Jan 2008 03:04:47 GMT

Hi
Often my server is not responding for telnet ,rlogin from other servers or ssh from remote but the server is still able to be pinged from remote . Please provide some quick solution .
Thanks in Advance .

--Robin

Re: Server not Responding.

Warren_9 — Fri, 18 Jan 2008 03:20:40 GMT

Hi Robin,

how about console login?

GOOD LUCK!!

Re: Server not Responding.

A. Clay Stephenson — Fri, 18 Jan 2008 03:21:56 GMT

The very first thing that I would check is that inetd is running. If not then "/sbin/init.d/inetd start" should fix you. Because inetd is such a critical daemon (especially for remote connections), it's a good idea to have a cron job to check on inetd and restart it if necessary.

Re: Server not Responding.

Robjan — Fri, 18 Jan 2008 03:47:17 GMT

Hi
Console Login is also not working.

How can I check without entering into the server whether inetd is running or not.

--Robin.

Re: Server not Responding.

Bill Hassell — Fri, 18 Jan 2008 03:59:18 GMT

I'll make a big assumption that you are running a recent HP-UX server and that you are connecting to the console with a serial cable and a terminal, or using telnet to connect to the GSP/MP port. In that case, you should be able to type CTRL-b to get the service prompt. If not, you need to get the correct cable.

When you try telnet, rlogin or ssh, do you get a connection closed message? Or do you get any prompt at all? What model is your server?

Re: Server not Responding.

Khairy — Fri, 18 Jan 2008 04:01:53 GMT

hi robjan,

maybe you could share with us server model.

If its rpxxxx boxes, you could telnet to GSP and you will get to access the console. Press Ctrl-Ecf to get the console activate. If your system is up, you should be able to see login prompt. Log in and check for / and /var filesystem % usage. And also check for inetd.conf. Is the system admin disable telnet?

From what you explained earlier, the server still respond to ping request but doesn't allow any login from telnet/ssh/rlogin, right?

Is it possible the server has ipfilter which allow only selected IP to telnet to it or is there any firewall in between blocking or filtering access to the server?

Let us know.

Rgds

Re: Server not Responding.

Robjan — Fri, 18 Jan 2008 04:05:39 GMT

Hi

I am not getting any connection closed message or the login prompt when I do an ssh or telnet . Even from MP login its not possible to access.my server model no 9000/785/J6700.

--Robin.

Re: Server not Responding.

Asif Sharif — Fri, 18 Jan 2008 04:30:41 GMT

Hi Robin,

This looks like a workstation. Connect serial cable with server and check the network configuration,inetd etc.

here is the docs of HP j6700 Workstation.

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual〈=en&cc=us&docIndexId=64180&taskId=110&prodTypeId=12454&prodSeriesId=75761

Regards,
Asif Sharif

Re: Server not Responding.

Torsten. — Fri, 18 Jan 2008 06:57:06 GMT

"Even from MP login its not possible to access.my server model no 9000/785/J6700"

MP login can't work, because there is **NO** MP in this system.

The serial connection may not work if the console is set to the graphics terminal - is one connected? You should also check for IP conflicts - if a PC is using the same IP, there is probably no ssh or telnet daemon running ...

Re: Server not Responding.

Robjan — Fri, 18 Jan 2008 07:53:44 GMT

Hi

Also while pinging the host I am getting message like .
"source quench reached" .Is this a problem with the network ??

--Robin

Re: Server not Responding.

Asif Sharif — Fri, 18 Jan 2008 09:54:37 GMT

Hi Robin,

Check the following link,
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=17173

Regards,
Asif Sharif

Re: Server not Responding.

Robjan — Fri, 18 Jan 2008 10:30:04 GMT

Hi

Can anyone tell me how to increase the buffer size and decrease the delay interval to avoid the source quench message.
--Robin

Re: Server not Responding.

Robjan — Mon, 21 Jan 2008 02:59:20 GMT

The issue is solved only after restarting the server.