Veritas-bu

[Veritas-bu] Cannot get bound socket - update

2000-02-10 10:59:52
Subject: [Veritas-bu] Cannot get bound socket - update
From: David Simpson davidgs AT colltech DOT com
Date: Thu, 10 Feb 2000 09:59:52 -0600 (CST)
 > 
> ----- Original Message -----
> From: "David Simpson" <davidgs AT colltech DOT com>
> To: <Veritas-users AT Eng.Auburn DOT EDU>
> Cc: <veritas-bu AT mailman.eng.auburn DOT edu>
> Sent: Monday, February 07, 2000 10:22 AM
> Subject: [Veritas-bu] Cannot get bound socket error
> 
> 
> > Good morning all.  We are running netbackup 3.2 on Solaris 2.6, and keep
> > getting the following message in the problem report:
> >
> > bkup2 -  cannot get bound socket: Address already in use (125)
> >
> > This message is repeated incessantly.  Stopping/starting netbackup
> > (cleanly, according to docs) will cause it to stop.  I cannot seem to
> > associate the messages starting to any event.  It does not seem to
> > interfere with the backups, and is more a nuisance than anything else. Any
> > suggestions would be appreciated.
> >
> > David Simpson - Consultant davidgs AT colltech DOT com
> > Collective Technologies

Thanks for the input from everyone, but the problem still persists. I have
found the following in the bpdbm log, which is where the problem starts.

17:54:30 [28059] <4> bpdbm: INITIATING bpdbm: NetBackup 3.2GA 99111100 on
bkup2 (verbose) IDIRSTRUCT=2
17:54:30 [28059] <2> bpdbm: wakeup 60 minutes, not logging queries,
catching sigs
17:54:30 [28059] <2> build_server_list: *** Server name bkup2 ***
17:54:30 [28059] <2> build_server_list:     ip address is 10.210.1.14,
(0xad2010e)
17:54:30 [28059] <2> getsockbound: service=bpdbm protocol=tcp port=13721
17:54:30 [28059] <16> getsockbound: bind() failed, Address already in use
(125)


bpdbm was already running, causing the error.  Any ideas why it tried to
start, and why it keeps on trying to start?

Thanks!






<Prev in Thread] Current Thread [Next in Thread>