topic Re: Can not connect to inet for getting filesystem list on host" in Operating System - HP-UX

Can not connect to inet for getting filesystem list on host"

Claire Daelman — Thu, 12 Sep 2002 16:57:08 GMT

Hello,

During backup with OBII, this alarm is generated :
Can not connect to inet for getting filesystem list on host"HOSTNAME".

I have no problem to connect from cell server to concerning server(remsh, rlogin).

Thanks .
Claire

Re: Can not connect to inet for getting filesystem list on host"

Helen French — Thu, 12 Sep 2002 17:09:27 GMT

What is the OS and release?

Re: Can not connect to inet for getting filesystem list on host"

Claire Daelman — Thu, 12 Sep 2002 17:12:47 GMT

It's HP-UX 11.11 for concerning server and 11.00 for cell server

Re: Can not connect to inet for getting filesystem list on host"

Helen French — Thu, 12 Sep 2002 17:27:03 GMT

These error messages will be coming from the 'concerning server' because of a missing OB inet agent there. You can check this by looking at two files - /etc/services and /etc/inetd.conf. You may need to add the entries if you cannot find one. Also, check the inet.log file too (/var/opt/omni/log/inet.log ?)

Re: Can not connect to inet for getting filesystem list on host"

Leif Halvarsson_2 — Thu, 12 Sep 2002 17:37:35 GMT

Hi

You can test the OmniBack inet service on the client with:

# telnet 5555
Trying...
Connected to c165.okg.sydkraft.se.
Escape character is '^]'.
HP OpenView OmniBack II A.04.10: INET, internal build 176, built on Tue Nov 13 01:16:33 2001
Connection closed by foreign host.

Re: Can not connect to inet for getting filesystem list on host"

Claire Daelman — Thu, 12 Sep 2002 18:05:54 GMT

Effectively, the telnet hostname 5555 is refused. I have add the good line in /etc/inetd.conf. I think I have to relaunch the inetd but how...

Re: Can not connect to inet for getting filesystem list on host"

Helen French — Thu, 12 Sep 2002 18:09:44 GMT

This command will be used after making any changes to /etc/inetd.conf and for that changes to be in effect:
# inetd -c
# man inetd - for details

Re: Can not connect to inet for getting filesystem list on host"

A. Clay Stephenson — Thu, 12 Sep 2002 18:11:18 GMT

If you have already put the omni entry back in /etc/inetd.conf then all you have to do is issue an 'inetd -c' to force inetd to reread its configuration file.

Re: Can not connect to inet for getting filesystem list on host"

Claire Daelman — Thu, 12 Sep 2002 18:20:17 GMT

I have done evrything but I already have with OBII (can not get the list of filesystem on host "hostname").

Thanks for all helps

Re: Can not connect to inet for getting filesystem list on host"

A. Clay Stephenson — Thu, 12 Sep 2002 18:25:10 GMT

You haven't bothered to identify the OB2 version but I do remember that newly installed 3.50 had exactly this problem on 11x boxes while the 10.20 agents worked just fine. It's pretty much a standard rule of OmniBack installs that you install from CD and then immediately install the latest cumulative patches on the Cell/Install servers. Don't forget to then push the new agents out to the clients.