Operating System - HP-UX
1753781 Members
7549 Online
108799 Solutions
New Discussion юеВ

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

 
SOLVED
Go to solution
Claire Daelman
Advisor

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

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
9 REPLIES 9
Helen French
Honored Contributor

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

What is the OS and release?
Life is a promise, fulfill it!
Claire Daelman
Advisor

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

It's HP-UX 11.11 for concerning server and 11.00 for cell server
Helen French
Honored Contributor
Solution

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

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 ?)
Life is a promise, fulfill it!
Leif Halvarsson_2
Honored Contributor

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

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.
Claire Daelman
Advisor

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

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...
Helen French
Honored Contributor

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

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
Life is a promise, fulfill it!
A. Clay Stephenson
Acclaimed Contributor

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

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.
If it ain't broke, I can fix that.
Claire Daelman
Advisor

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

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

Thanks for all helps
A. Clay Stephenson
Acclaimed Contributor

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

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.
If it ain't broke, I can fix that.