There is no “daemon”
running on the RHEL client usually. Instead xinetd should be
listening on the port and start the client process when a request is
made.
By default xinetd is
NOT installed on RHEL. The NBU Client is brain dead so assumes you have
inetd when it doesn’t find xinetd running. It then creates an
/etc/inetd.conf file which is useless since inetd isn’t
running.
Verify you have xinetd
installed (rpm –q xinetd) and that it has the following files in
/etc/xinetd.d:
-rw-r--r-- 1 root
root 311 Mar 14 2008 bpcd
-rw-r--r-- 1 root
root 377 Mar 14 2008 bpjava-msvc
-rw-r--r-- 1 root
root 344 Mar 14 2008 vnetd
-rw-r--r-- 1 root
root 307 Mar 14 2008 vopied
If not the simplest
solution would be to remove the NBU software from the client then install xinetd
then reinstall the client so it configures xinetd
properly.
The fact it works
sometimes makes me wonder if the above is your problem
though.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of bbb bb
Sent: Monday, February 09, 2009 10:17
AM
To: aaa aaa
Subject: [Veritas-bu] [Q] How to check
Veritas client 6.5 daemon running onLinux????
We have Veritas Netbackup client
6.5 install on Redhat As 4.7. It has been run for a period of
time.
Sometime we got "can not connect to client" message" and Veritas server
can NOT perform backup.
Our support engineer say it may be Netbackup
client daemon is die on LINUX server.
Does there has way to check Veritas
client daemon running status on Linux server?
Thanks.
Windows Live™: E-mail. Chat.
Share. Get more ways to connect. Check it out.