[Veritas-bu] jnbSA console missing functionality
2003-03-13 14:14:42
Subject: |
[Veritas-bu] jnbSA console missing functionality |
From: |
dlbewley AT ucdavis DOT edu (Dale Bewley) |
Date: |
13 Mar 2003 11:14:42 -0800 |
I guess I failed to mention that this is all on the same server. Thanks
for the tip on the admin and bprd logs. I enabled those and did get some
information. From the admin log
10:38:53.116 [8238] <2> getsockconnected: Connect to HOST on port 851
10:38:53.117 [8238] <2> logconnections: BPCD CONNECT FROM 1.2.2.1.851 TO
1.2.2.1.13782
10:39:53.125 [8238] <2> bpcr_connect: bpcr_connect timeout during select
after 60 seconds on port 710
10:39:53.126 [8238] <16> bpauthorize main: Function
connect_to_remote_server(HOST) failed: 25
10:39:53.126 [8238] <2> bpauthorize: cannot connect on socket
10:39:53.126 [8238] <2> bpauthorize: EXIT status = 25
Netstat lists port 13782 as listening and I made sure hosts.deny
wouldn't block. This looks like a big clue:
# telnet localhost 13782
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
unknown argument bpcd
Usage: bpcd [-standalone] [-no_callback] [-debug] [-port portnum]
[-keyfile]
Connection closed by foreign host.
# grep bpcd /etc/inetd.conf
bpcd stream tcp nowait root /usr/local/bin/tcpd
/usr/openv/netbackup/bin/bpcd bpcd
Well, at least now I have a trail to go down. I'm not real up to speed
on the various components of NB.
On Thu, 2003-03-13 at 10:26, Mark Hickey wrote:
> I think Dave is on the right track here.
>
> Verify the following:
> - the short name for the host running the interface has a
> SERVER=... line in the bp.conf
> - the FQDN for the server also has a SERVER= entry in the bp.conf
> - you can ping the NBU server from the host running the admin interface
> - you can ping the host running the interface using both the short and FQDN
>
> Something in the network may have changed, affecting the ability to access
> NBU.
>
> If all else fails, enable bprd and admin logging on the server and see what
> turns up.
|
|
|