Operating System - Linux
1827757 Members
2833 Online
109969 Solutions
New Discussion

Re: omniback client problem with Red Hat 7.1

 
SOLVED
Go to solution
Carlos Ferreira_3
New Member

omniback client problem with Red Hat 7.1

hi, my problem is the following:
when i do "telnet localhost omni" the answer is:
Trying 127.0.0.1...
Connected to ecommerce.
Escape character is '^]'.
1 2 Connection closed by foreign host.

I don't know why appears "1 2" .

- the service omni is run because i gone "chkconfig --list" the answer is:
...
omni: on
- ipchains is disable
- here is my /etc/xinetd.d/omni file:
service omni
{
socket_type = stream
wait = no
user = root
server = /opt/omniback/bin/inet
server_args = inet - log /opt/omniback/log/inet.log
log_on_failure += USERID
}


Somebody can help me, please?
2 REPLIES 2
Kodjo Agbenu
Honored Contributor
Solution

Re: omniback client problem with Red Hat 7.1

Hello Carlos,

I recently installed OmniBack on RedHat 7.0 at customer site. I created /etc/xinetd.d/omni file just as you did, but something seems different between your's and mine :

server = /opt/omniback/bin/inet
server_args = inet - log /opt/omniback/log/inet.log

I suppose that if your file permissions are good, the path of OmniBack install (/opt instead of /usr) should not make any difference.

However, you should check 2 things :

There is probably a syntax error in "server_args" : no space between log and minus sign ("-log" instead of "- log").
Moreover, I would not put "inet" in that syntax. I think it is not necessary for "xinetd" to work.

Second thing to check : permissions of "inet" binary, in particular : SUID bit should be set (and normally it is).

Good luck.

Kodjo


Learn and explain...
wyan lowe
Frequent Advisor

Re: omniback client problem with Red Hat 7.1

wtf...
I guess I'll have to retype what I thought I posted...

your problem appears very similar to the one I had, where that "1 2" error message isn't very helpful

I created a symbolic link from /usr/omni to point to where I had actually installed the client software (in my case it was /var/opt/omni)

My guess is that the binaries expect the client software to be in /usr/omni...

The documentation says /usr/omni, but doesn't say anything about if you chose to place it in a different path, make sure to create a symbolic link...that might save some frustration and wasted time.

anyway, after I created the symbolic link, it still wouldn't import into the NT cell manager...

had to create 2 more files in order to import successfully..

look in the Linux->sys admin forum for the other recent omniback redhat posting by Miguel, I think I have clearly written how I was able to get it to work under 7.l

good luck