: Wednesday, January 20, 2010 6:03 PM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Bpjobd and other failures.
Justin,
Thanks for the reply. For whatever reason things seem to have magically
started working again. All I did was shutdown Veritas (again), turned
up
,
Simon (external)
Sent: Thursday, January 21, 2010 6:47 AM
To: Jeff Cleverley; Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Bpjobd and other failures.
Jeff
Good idea about not touching anything again...
One colleague a few years back, done a Firmware upgrade
Hi,
Taking a shot in the dark here, for the tcp issues, try adding:
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_tw_recycle = 1
To your /etc/sysctl.conf, reboot.
For vnetd, check your /etc/xinetd.d/vnetd*
Also check the logs that xinetd is not throttling connections if too many
servers are trying to
Justin,
Thanks for the reply. For whatever reason things seem to have magically
started working again. All I did was shutdown Veritas (again), turned up
the verbosity in bp.conf, and restarted it. When it first started I still
didn't have bpdbm, bpjobd, etc, running. The vnetd log had a lot
Greetings,
Our environment is NB6.5.1 on a RHEL4 server. It has a hpux SAN media
server also. All other clients are backed up over the network. Most are
RHEL4x.
The tape library in our Singapore office failed over the weekend and caused
a lot of things to fail and continue to be wedged up.
Greetings,
While continuing to work on this it seems there may be issues with vnetd.
The netstat -a |grep vnet shows this:
tcp0 0 *:vnetd *:*
LISTEN
tcp0 0 sgpbkp04.sgp.avagotec:35781 agt604.sgp.avagotech.:vnetd
ESTABLISHED
tcp0 0
