socket read failed errno 131 - Veritas Net Backup

This is a discussion on socket read failed errno 131 - Veritas Net Backup ; I am using Netbackup 5.0 MP3 on solaris 8 to backup a Windows 2000 client on a secondary network connection (backup LAN). The hostname (production LAN) of the client is different to the backup LAN interface name in DNS. I ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: socket read failed errno 131

  1. socket read failed errno 131


    I am using Netbackup 5.0 MP3 on solaris 8 to backup a Windows 2000 client
    on a
    secondary network connection (backup LAN). The hostname (production
    LAN) of the client is different to the backup LAN interface name in DNS.

    I get a socket read failed error 131 on the backup - which results in the
    job failing
    with a code 13 (file read failed).

    The server backs up without issue if I use production LAN interface. It
    also
    backs up over the backup LAN if I add the backup LAN IP address into DNS
    on
    the Master and Media servers with the production LAN hostname - spoof the
    address as it were.

    It seems that I cannot backup a Windows 2000 client over a secondary interface
    on MP3. Can you confirm that this is the case. I have no problem backing
    up
    Solaris clients on NBU 5 MP3, nor do I have a problem backing up Windows
    2000
    clients at NBU 4.5 FP5. Any ideas?


  2. Re: socket read failed errno 131

    in article 42b69bfa@ROSASTDMZ05., Simon at simon.j.rehling@accenture.com
    wrote on 6/20/05 3:35 AM:

    >
    > I am using Netbackup 5.0 MP3 on solaris 8 to backup a Windows 2000 client
    > on a
    > secondary network connection (backup LAN). The hostname (production
    > LAN) of the client is different to the backup LAN interface name in DNS.
    >
    > I get a socket read failed error 131 on the backup - which results in the
    > job failing
    > with a code 13 (file read failed).
    >
    > The server backs up without issue if I use production LAN interface. It
    > also
    > backs up over the backup LAN if I add the backup LAN IP address into DNS
    > on
    > the Master and Media servers with the production LAN hostname - spoof the
    > address as it were.
    >
    > It seems that I cannot backup a Windows 2000 client over a secondary
    > interface
    > on MP3. Can you confirm that this is the case. I have no problem backing
    > up
    > Solaris clients on NBU 5 MP3, nor do I have a problem backing up Windows
    > 2000
    > clients at NBU 4.5 FP5. Any ideas?
    >


    Have you added the backup interface hostname as a valid client name to the
    client NB configuration? Have you added the backup interface hostname to
    your sitewide DNS?

    Output of bpcd log on the client would also yield useful information.


  3. Re: socket read failed errno 131

    in article 42b6f1f0@ROSASTDMZ05., Simon at simon.j.rehling@accenture.com
    wrote on 6/20/05 9:42 AM:

    >
    > ps wrote:
    >> in article 42b69bfa@ROSASTDMZ05., Simon at simon.j.rehling@accenture.com
    >> wrote on 6/20/05 3:35 AM:
    >>
    >>>
    >>> I am using Netbackup 5.0 MP3 on solaris 8 to backup a Windows 2000 client
    >>> on a
    >>> secondary network connection (backup LAN). The hostname (production
    >>> LAN) of the client is different to the backup LAN interface name in DNS.
    >>>
    >>> I get a socket read failed error 131 on the backup - which results in

    > the
    >>> job failing
    >>> with a code 13 (file read failed).
    >>>
    >>> The server backs up without issue if I use production LAN interface. It
    >>> also
    >>> backs up over the backup LAN if I add the backup LAN IP address into

    > DNS
    >>> on
    >>> the Master and Media servers with the production LAN hostname - spoof

    > the
    >>> address as it were.
    >>>
    >>> It seems that I cannot backup a Windows 2000 client over a secondary
    >>> interface
    >>> on MP3. Can you confirm that this is the case. I have no problem backing
    >>> up
    >>> Solaris clients on NBU 5 MP3, nor do I have a problem backing up Windows
    >>> 2000
    >>> clients at NBU 4.5 FP5. Any ideas?
    >>>

    >>
    >> Have you added the backup interface hostname as a valid client name to the
    >> client NB configuration? Have you added the backup interface hostname to
    >> your sitewide DNS?
    >>
    >> Output of bpcd log on the client would also yield useful information.
    >>

    > The client name on the NB client is the backup interface hostname, and is
    > in DNS. The ptr records in DNS are correct.
    > Here is the bpcd client log as requested:
    >
    > 16:06:19.683 [3476.3624] <2> bpcd main: offset to GMT 0
    > 16:06:19.699 [3476.3624] <2> bpcd main: Got socket for input 496
    > 16:06:19.699 [3476.3624] <2> logconnections: BPCD ACCEPT FROM ?.?.188.2.737
    > TO ?.?.190.53.13782
    > 16:06:19.699 [3476.3624] <2> bpcd main: setup_sockopts complete
    > 16:06:19.777 [3476.3624] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.356:
    > no methods for address: no authentication required
    > 16:06:19.777 [3476.3624] <2> bpcd main: no authentication required
    > 16:06:19.777 [3476.3624] <2> bpcd peer_hostname: Connection from host
    > media1-1-veritas
    > (?.?.188.2) port 737
    > 16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing
    > MasterCluster-veritas
    > and media1-1-veritas
    > 16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing media2 and
    > media1-1-veritas
    > 16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing media1 and
    > media1-1-veritas
    > 16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media2-1-veritas
    > and media1-1-veritas
    > 16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media2-2-veritas
    > and media1-1-veritas
    > 16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media1-1-veritas
    > and media1-1-veritas
    > 16:06:24.996 [3476.3624] <4> bpcd valid_server: hostname comparison succeeded
    > 16:06:24.996 [3476.3624] <2> bpcd main: output socket port number = 674
    > 16:06:24.996 [3476.3624] <2> bpcd peer_hostname: Connection from host
    > media1-1-veritas
    > (?.?.188.2) port 737
    > 16:06:24.996 [3476.3624] <2> bpcd main: Peer hostname is media1-1-veritas
    > 16:06:24.996 [3476.3624] <2> nb_bind_on_port_addr: bound to port 790
    > 16:06:24.996 [3476.3624] <2> bpcd main: Got socket for output 700, lport
    > = 790
    > 16:06:24.996 [3476.3624] <2> bpcd main: Connected on output socket
    > 16:06:24.996 [3476.3624] <2> bpcd main: Duplicated socket on stderr
    > 16:06:24.996 [3476.3624] <2> bpcd main: <---- NetBackup 5.0GA 0
    > ------------initiated
    > 16:06:24.996 [3476.3624] <2> bpcd main: Not using VxSS authentication with
    > media1-1-veritas
    >
    > Interface: ?.?.190.53 on Interface 0x1000003
    > Internet Address Physical Address Type
    > ?.?.191.254 00-00-0c-07-ac-be dynamic
    >
    > Interface: ?.?.139.10 on Interface 0x1000004
    > Internet Address Physical Address Type
    > ?.?.139.13 00-08-02-de-f6-b1 dynamic
    > ?.?.139.254 00-00-0c-07-ac-8b dynamic
    > 16:06:25.074 [3476.3624] <2> bpcd main:
    > 16:06:26.012 [3476.3624] <2> bpcd main: BPCD_GET_VERSION_RQST
    > 16:06:26.012 [3476.3624] <2> bpcd main: BPCD_GET_PLATFORM_RQST
    > 16:06:26.121 [3476.3624] <2> bpcd main: BPCD_FORK_CMD_RQST
    > 16:06:26.121 [3476.3624] <2> bpcd main: fork cmd =
    > /usr/openv/netbackup/bin/bpbkar
    > bpbkar -r 451352 -ru root -dt 0 -to 0 -clnt client-veritas
    >
    > -class HN-W2K-W_ALL-FS-1 -sched Weekly-Full -st FULL -bpstart_to 1800
    > -bpend_to
    > 1800 -read_to 1800 -use_otm -fso -b client-veritas_1119279898
    >
    > -kl 28 -use_ofb
    > 16:06:26.121 [3476.3624] <2> bpcd main: Convert args to CreateProcess format
    > 16:06:26.121 [3476.3624] <2> bpcd main: Done converting args to CreateProcess
    > format
    > 16:06:26.121 [3476.3624] <2> bpcd main: new fork cmd =
    > C:\Progra~1\VERITAS\NetBackup\bin\bpbkar32.exe
    > -r 451352 -ru root -dt 0 -to 0 -clnt
    >
    > client-veritas -class HN-W2K-W_ALL-FS-1 -sched Weekly-Full -st FULL
    > -bpstart_to
    > 1800 -bpend_to 1800 -read_to 1800 -use_otm -fso -b
    >
    > client-veritas_1119279898 -kl 28 -use_ofb
    > 16:06:26.121 [3476.3624] <2> bpcd main: Before CreateProcess
    > 16:06:26.121 [3476.3624] <2> bpcd main: StdOutput assigned the value
    > STDOUTSOCK
    > 16:06:26.183 [3476.3624] <2> bpcd main: After CreateProcess, pid = 2264
    > 16:06:26.183 [3476.3624] <2> bpcd exit_bpcd: exit status 0
    > ----------->exiting
    > 16:07:09.137 [4116.3548] <2> bpcd main: offset to GMT 0
    > 16:07:09.137 [4116.3548] <2> bpcd main: Got socket for input 512
    > 16:07:09.137 [4116.3548] <2> logconnections: BPCD ACCEPT FROM ?.?.188.2.907
    > TO ?.?.190.53.13782
    > 16:07:09.137 [4116.3548] <2> bpcd main: setup_sockopts complete
    > 16:07:09.183 [4116.3548] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.356:
    > no methods for address: no authentication required
    > 16:07:09.183 [4116.3548] <2> bpcd main: no authentication required
    > 16:07:09.183 [4116.3548] <2> bpcd peer_hostname: Connection from host
    > media1-1-veritas
    > (?.?.188.2) port 907
    > 16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing
    > MasterCluster-veritas
    > and media1-1-veritas
    > 16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing media2 and
    > media1-1-veritas
    > 16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing media1 and
    > media1-1-veritas
    > 16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media2-1-veritas
    > and media1-1-veritas
    > 16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media2-2-veritas
    > and media1-1-veritas
    > 16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media1-1-veritas
    > and media1-1-veritas
    > 16:07:09.199 [4116.3548] <4> bpcd valid_server: hostname comparison succeeded
    > 16:07:09.199 [4116.3548] <2> bpcd main: output socket port number = 732
    > 16:07:09.199 [4116.3548] <2> bpcd peer_hostname: Connection from host
    > media1-1-veritas
    > (?.?.188.2) port 907
    > 16:07:09.199 [4116.3548] <2> bpcd main: Peer hostname is media1-1-veritas
    > 16:07:09.199 [4116.3548] <2> nb_bind_on_port_addr: bound to port 773
    > 16:07:09.199 [4116.3548] <2> bpcd main: Got socket for output 700, lport
    > = 773
    > 16:07:09.199 [4116.3548] <2> bpcd main: Connected on output socket
    > 16:07:09.199 [4116.3548] <2> bpcd main: Duplicated socket on stderr
    > 16:07:09.199 [4116.3548] <2> bpcd main: <---- NetBackup 5.0GA 0
    > ------------initiated
    > 16:07:09.199 [4116.3548] <2> bpcd main: Not using VxSS authentication with
    > media1-1-veritas
    >
    > Interface: ?.?.190.53 on Interface 0x1000003
    > Internet Address Physical Address Type
    > ?.?.190.90 mac-address dynamic
    > ?.?.191.254 mac-address dynamic
    >
    > Interface: ?.?.139.10 on Interface 0x1000004
    > Internet Address Physical Address Type
    > ?.?.139.3 mac-address dynamic
    > ?.?.139.13 mac-address dynamic
    > ?.?.139.254 mac-address dynamic
    > 16:07:09.262 [4116.3548] <2> bpcd main:
    > 16:07:09.262 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    > 16:07:09.293 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    > 16:07:09.402 [4116.3548] <2> bpcd main: BPCD_READ_USERS_CONFIG_RQST
    > 16:07:09.496 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    > 16:07:09.590 [4116.3548] <2> bpcd main: BPCD_READ_HOST_CONFIG_RQST
    > 16:07:09.699 [4116.3548] <2> bpcd main: BPCD_DISCONNECT_RQST
    > 16:07:09.699 [4116.3548] <2> bpcd exit_bpcd: exit status 0
    > ----------->exiting
    >
    > Thanks for looking at this!


    I show error 131 as being a client permission error, not a socket fail
    error--is the socket fail error appearing on the media or master server?
    This troubleshooting guide excerpt appears to point at a
    hostname/DNS/routing issue:


    NetBackup Status Code: 131
    Message: client is not validated to use the server

    Explanation: The client name, as determined from the connection to the
    server, did not
    match any client name in the NetBackup configuration and there was no
    altnames
    configuration for this client on the master server. A client and server that
    have multiple
    network connections can encounter this problem if the name by which the
    client is
    configured is not the one by which its routing tables direct connections to
    the server.
    Recommended Action:
    1. Examine the NetBackup Problems report.
    2. Create a debug log directory for bprd and retry the operation. Check the
    resulting
    debug log to determine the connection and client names.
    Depending on the request type (restore, backup, and so on.), you may need or
    want
    to:
    Change the clientıs configured name.
    Modify the routing tables on the client.
    On the master server, set up an altnames directory and file for this client
    (see the
    NetBackup System Administratorıs Guide).
    or
    On a UNIX master server, create a soft link in the NetBackup image catalog.
    3. Review ³Verifying Host Names and Services Entries² on page34.
    4. Run the NetBackup Configuration Validation Utility (NCVU) -conf option>
    on the master server for the associated NetBackup clients. Note the client
    hostname
    checks in section seven.



  4. Re: socket read failed errno 131


    ps wrote:
    >in article 42b69bfa@ROSASTDMZ05., Simon at simon.j.rehling@accenture.com
    >wrote on 6/20/05 3:35 AM:
    >
    >>
    >> I am using Netbackup 5.0 MP3 on solaris 8 to backup a Windows 2000 client
    >> on a
    >> secondary network connection (backup LAN). The hostname (production
    >> LAN) of the client is different to the backup LAN interface name in DNS.
    >>
    >> I get a socket read failed error 131 on the backup - which results in

    the
    >> job failing
    >> with a code 13 (file read failed).
    >>
    >> The server backs up without issue if I use production LAN interface. It
    >> also
    >> backs up over the backup LAN if I add the backup LAN IP address into

    DNS
    >> on
    >> the Master and Media servers with the production LAN hostname - spoof

    the
    >> address as it were.
    >>
    >> It seems that I cannot backup a Windows 2000 client over a secondary
    >> interface
    >> on MP3. Can you confirm that this is the case. I have no problem backing
    >> up
    >> Solaris clients on NBU 5 MP3, nor do I have a problem backing up Windows
    >> 2000
    >> clients at NBU 4.5 FP5. Any ideas?
    >>

    >
    >Have you added the backup interface hostname as a valid client name to the
    >client NB configuration? Have you added the backup interface hostname to
    >your sitewide DNS?
    >
    >Output of bpcd log on the client would also yield useful information.
    >

    The client name on the NB client is the backup interface hostname, and is
    in DNS. The ptr records in DNS are correct.
    Here is the bpcd client log as requested:

    16:06:19.683 [3476.3624] <2> bpcd main: offset to GMT 0
    16:06:19.699 [3476.3624] <2> bpcd main: Got socket for input 496
    16:06:19.699 [3476.3624] <2> logconnections: BPCD ACCEPT FROM ?.?.188.2.737
    TO ?.?.190.53.13782
    16:06:19.699 [3476.3624] <2> bpcd main: setup_sockopts complete
    16:06:19.777 [3476.3624] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.356:
    no methods for address: no authentication required
    16:06:19.777 [3476.3624] <2> bpcd main: no authentication required
    16:06:19.777 [3476.3624] <2> bpcd peer_hostname: Connection from host media1-1-veritas
    (?.?.188.2) port 737
    16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing MasterCluster-veritas
    and media1-1-veritas
    16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing media2 and media1-1-veritas
    16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing media1 and media1-1-veritas
    16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media2-1-veritas
    and media1-1-veritas
    16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media2-2-veritas
    and media1-1-veritas
    16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media1-1-veritas
    and media1-1-veritas
    16:06:24.996 [3476.3624] <4> bpcd valid_server: hostname comparison succeeded
    16:06:24.996 [3476.3624] <2> bpcd main: output socket port number = 674
    16:06:24.996 [3476.3624] <2> bpcd peer_hostname: Connection from host media1-1-veritas
    (?.?.188.2) port 737
    16:06:24.996 [3476.3624] <2> bpcd main: Peer hostname is media1-1-veritas
    16:06:24.996 [3476.3624] <2> nb_bind_on_port_addr: bound to port 790
    16:06:24.996 [3476.3624] <2> bpcd main: Got socket for output 700, lport
    = 790
    16:06:24.996 [3476.3624] <2> bpcd main: Connected on output socket
    16:06:24.996 [3476.3624] <2> bpcd main: Duplicated socket on stderr
    16:06:24.996 [3476.3624] <2> bpcd main: <---- NetBackup 5.0GA 0 ------------initiated
    16:06:24.996 [3476.3624] <2> bpcd main: Not using VxSS authentication with
    media1-1-veritas

    Interface: ?.?.190.53 on Interface 0x1000003
    Internet Address Physical Address Type
    ?.?.191.254 00-00-0c-07-ac-be dynamic

    Interface: ?.?.139.10 on Interface 0x1000004
    Internet Address Physical Address Type
    ?.?.139.13 00-08-02-de-f6-b1 dynamic
    ?.?.139.254 00-00-0c-07-ac-8b dynamic
    16:06:25.074 [3476.3624] <2> bpcd main:
    16:06:26.012 [3476.3624] <2> bpcd main: BPCD_GET_VERSION_RQST
    16:06:26.012 [3476.3624] <2> bpcd main: BPCD_GET_PLATFORM_RQST
    16:06:26.121 [3476.3624] <2> bpcd main: BPCD_FORK_CMD_RQST
    16:06:26.121 [3476.3624] <2> bpcd main: fork cmd = /usr/openv/netbackup/bin/bpbkar
    bpbkar -r 451352 -ru root -dt 0 -to 0 -clnt client-veritas

    -class HN-W2K-W_ALL-FS-1 -sched Weekly-Full -st FULL -bpstart_to 1800 -bpend_to
    1800 -read_to 1800 -use_otm -fso -b client-veritas_1119279898

    -kl 28 -use_ofb
    16:06:26.121 [3476.3624] <2> bpcd main: Convert args to CreateProcess format
    16:06:26.121 [3476.3624] <2> bpcd main: Done converting args to CreateProcess
    format
    16:06:26.121 [3476.3624] <2> bpcd main: new fork cmd = C:\Progra~1\VERITAS\NetBackup\bin\bpbkar32.exe
    -r 451352 -ru root -dt 0 -to 0 -clnt

    client-veritas -class HN-W2K-W_ALL-FS-1 -sched Weekly-Full -st FULL -bpstart_to
    1800 -bpend_to 1800 -read_to 1800 -use_otm -fso -b

    client-veritas_1119279898 -kl 28 -use_ofb
    16:06:26.121 [3476.3624] <2> bpcd main: Before CreateProcess
    16:06:26.121 [3476.3624] <2> bpcd main: StdOutput assigned the value STDOUTSOCK
    16:06:26.183 [3476.3624] <2> bpcd main: After CreateProcess, pid = 2264
    16:06:26.183 [3476.3624] <2> bpcd exit_bpcd: exit status 0 ----------->exiting
    16:07:09.137 [4116.3548] <2> bpcd main: offset to GMT 0
    16:07:09.137 [4116.3548] <2> bpcd main: Got socket for input 512
    16:07:09.137 [4116.3548] <2> logconnections: BPCD ACCEPT FROM ?.?.188.2.907
    TO ?.?.190.53.13782
    16:07:09.137 [4116.3548] <2> bpcd main: setup_sockopts complete
    16:07:09.183 [4116.3548] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.356:
    no methods for address: no authentication required
    16:07:09.183 [4116.3548] <2> bpcd main: no authentication required
    16:07:09.183 [4116.3548] <2> bpcd peer_hostname: Connection from host media1-1-veritas
    (?.?.188.2) port 907
    16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing MasterCluster-veritas
    and media1-1-veritas
    16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing media2 and media1-1-veritas
    16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing media1 and media1-1-veritas
    16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media2-1-veritas
    and media1-1-veritas
    16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media2-2-veritas
    and media1-1-veritas
    16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media1-1-veritas
    and media1-1-veritas
    16:07:09.199 [4116.3548] <4> bpcd valid_server: hostname comparison succeeded
    16:07:09.199 [4116.3548] <2> bpcd main: output socket port number = 732
    16:07:09.199 [4116.3548] <2> bpcd peer_hostname: Connection from host media1-1-veritas
    (?.?.188.2) port 907
    16:07:09.199 [4116.3548] <2> bpcd main: Peer hostname is media1-1-veritas
    16:07:09.199 [4116.3548] <2> nb_bind_on_port_addr: bound to port 773
    16:07:09.199 [4116.3548] <2> bpcd main: Got socket for output 700, lport
    = 773
    16:07:09.199 [4116.3548] <2> bpcd main: Connected on output socket
    16:07:09.199 [4116.3548] <2> bpcd main: Duplicated socket on stderr
    16:07:09.199 [4116.3548] <2> bpcd main: <---- NetBackup 5.0GA 0 ------------initiated
    16:07:09.199 [4116.3548] <2> bpcd main: Not using VxSS authentication with
    media1-1-veritas

    Interface: ?.?.190.53 on Interface 0x1000003
    Internet Address Physical Address Type
    ?.?.190.90 mac-address dynamic
    ?.?.191.254 mac-address dynamic

    Interface: ?.?.139.10 on Interface 0x1000004
    Internet Address Physical Address Type
    ?.?.139.3 mac-address dynamic
    ?.?.139.13 mac-address dynamic
    ?.?.139.254 mac-address dynamic
    16:07:09.262 [4116.3548] <2> bpcd main:
    16:07:09.262 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    16:07:09.293 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    16:07:09.402 [4116.3548] <2> bpcd main: BPCD_READ_USERS_CONFIG_RQST
    16:07:09.496 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    16:07:09.590 [4116.3548] <2> bpcd main: BPCD_READ_HOST_CONFIG_RQST
    16:07:09.699 [4116.3548] <2> bpcd main: BPCD_DISCONNECT_RQST
    16:07:09.699 [4116.3548] <2> bpcd exit_bpcd: exit status 0 ----------->exiting

    Thanks for looking at this!

  5. Re: socket read failed errno 131


    "Simon" wrote:
    >
    >I am using Netbackup 5.0 MP3 on solaris 8 to backup a Windows 2000 client
    > on a
    >secondary network connection (backup LAN). The hostname (production
    > LAN) of the client is different to the backup LAN interface name in DNS.
    >
    >I get a socket read failed error 131 on the backup - which results in the
    >job failing
    >with a code 13 (file read failed).
    >
    >The server backs up without issue if I use production LAN interface. It


    >also
    >backs up over the backup LAN if I add the backup LAN IP address into DNS
    >on
    >the Master and Media servers with the production LAN hostname - spoof the
    >address as it were.
    >
    >It seems that I cannot backup a Windows 2000 client over a secondary interface
    >on MP3. Can you confirm that this is the case. I have no problem backing
    >up
    >Solaris clients on NBU 5 MP3, nor do I have a problem backing up Windows
    >2000
    >clients at NBU 4.5 FP5. Any ideas?
    >



  6. Re: socket read failed errno 131


    ps wrote:
    >in article 42b6f1f0@ROSASTDMZ05., Simon at simon.j.rehling@accenture.com
    >wrote on 6/20/05 9:42 AM:
    >
    >>
    >> ps wrote:
    >>> in article 42b69bfa@ROSASTDMZ05., Simon at simon.j.rehling@accenture.com
    >>> wrote on 6/20/05 3:35 AM:
    >>>
    >>>>
    >>>> I am using Netbackup 5.0 MP3 on solaris 8 to backup a Windows 2000 client
    >>>> on a
    >>>> secondary network connection (backup LAN). The hostname (production
    >>>> LAN) of the client is different to the backup LAN interface name in

    DNS.
    >>>>
    >>>> I get a socket read failed error 131 on the backup - which results in

    >> the
    >>>> job failing
    >>>> with a code 13 (file read failed).
    >>>>
    >>>> The server backs up without issue if I use production LAN interface.

    It
    >>>> also
    >>>> backs up over the backup LAN if I add the backup LAN IP address into

    >> DNS
    >>>> on
    >>>> the Master and Media servers with the production LAN hostname - spoof

    >> the
    >>>> address as it were.
    >>>>
    >>>> It seems that I cannot backup a Windows 2000 client over a secondary
    >>>> interface
    >>>> on MP3. Can you confirm that this is the case. I have no problem backing
    >>>> up
    >>>> Solaris clients on NBU 5 MP3, nor do I have a problem backing up Windows
    >>>> 2000
    >>>> clients at NBU 4.5 FP5. Any ideas?
    >>>>
    >>>
    >>> Have you added the backup interface hostname as a valid client name to

    the
    >>> client NB configuration? Have you added the backup interface hostname

    to
    >>> your sitewide DNS?
    >>>
    >>> Output of bpcd log on the client would also yield useful information.
    >>>

    >> The client name on the NB client is the backup interface hostname, and

    is
    >> in DNS. The ptr records in DNS are correct.
    >> Here is the bpcd client log as requested:
    >>
    >> 16:06:19.683 [3476.3624] <2> bpcd main: offset to GMT 0
    >> 16:06:19.699 [3476.3624] <2> bpcd main: Got socket for input 496
    >> 16:06:19.699 [3476.3624] <2> logconnections: BPCD ACCEPT FROM ?.?.188.2.737
    >> TO ?.?.190.53.13782
    >> 16:06:19.699 [3476.3624] <2> bpcd main: setup_sockopts complete
    >> 16:06:19.777 [3476.3624] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.356:
    >> no methods for address: no authentication required
    >> 16:06:19.777 [3476.3624] <2> bpcd main: no authentication required
    >> 16:06:19.777 [3476.3624] <2> bpcd peer_hostname: Connection from host
    >> media1-1-veritas
    >> (?.?.188.2) port 737
    >> 16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing
    >> MasterCluster-veritas
    >> and media1-1-veritas
    >> 16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing media2 and
    >> media1-1-veritas
    >> 16:06:19.777 [3476.3624] <2> bpcd valid_server: comparing media1 and
    >> media1-1-veritas
    >> 16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media2-1-veritas
    >> and media1-1-veritas
    >> 16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media2-2-veritas
    >> and media1-1-veritas
    >> 16:06:24.996 [3476.3624] <2> bpcd valid_server: comparing media1-1-veritas
    >> and media1-1-veritas
    >> 16:06:24.996 [3476.3624] <4> bpcd valid_server: hostname comparison succeeded
    >> 16:06:24.996 [3476.3624] <2> bpcd main: output socket port number = 674
    >> 16:06:24.996 [3476.3624] <2> bpcd peer_hostname: Connection from host
    >> media1-1-veritas
    >> (?.?.188.2) port 737
    >> 16:06:24.996 [3476.3624] <2> bpcd main: Peer hostname is media1-1-veritas
    >> 16:06:24.996 [3476.3624] <2> nb_bind_on_port_addr: bound to port 790
    >> 16:06:24.996 [3476.3624] <2> bpcd main: Got socket for output 700, lport
    >> = 790
    >> 16:06:24.996 [3476.3624] <2> bpcd main: Connected on output socket
    >> 16:06:24.996 [3476.3624] <2> bpcd main: Duplicated socket on stderr
    >> 16:06:24.996 [3476.3624] <2> bpcd main: <---- NetBackup 5.0GA 0
    >> ------------initiated
    >> 16:06:24.996 [3476.3624] <2> bpcd main: Not using VxSS authentication

    with
    >> media1-1-veritas
    >>
    >> Interface: ?.?.190.53 on Interface 0x1000003
    >> Internet Address Physical Address Type
    >> ?.?.191.254 00-00-0c-07-ac-be dynamic
    >>
    >> Interface: ?.?.139.10 on Interface 0x1000004
    >> Internet Address Physical Address Type
    >> ?.?.139.13 00-08-02-de-f6-b1 dynamic
    >> ?.?.139.254 00-00-0c-07-ac-8b dynamic
    >> 16:06:25.074 [3476.3624] <2> bpcd main:
    >> 16:06:26.012 [3476.3624] <2> bpcd main: BPCD_GET_VERSION_RQST
    >> 16:06:26.012 [3476.3624] <2> bpcd main: BPCD_GET_PLATFORM_RQST
    >> 16:06:26.121 [3476.3624] <2> bpcd main: BPCD_FORK_CMD_RQST
    >> 16:06:26.121 [3476.3624] <2> bpcd main: fork cmd =
    >> /usr/openv/netbackup/bin/bpbkar
    >> bpbkar -r 451352 -ru root -dt 0 -to 0 -clnt client-veritas
    >>
    >> -class HN-W2K-W_ALL-FS-1 -sched Weekly-Full -st FULL -bpstart_to 1800
    >> -bpend_to
    >> 1800 -read_to 1800 -use_otm -fso -b client-veritas_1119279898
    >>
    >> -kl 28 -use_ofb
    >> 16:06:26.121 [3476.3624] <2> bpcd main: Convert args to CreateProcess

    format
    >> 16:06:26.121 [3476.3624] <2> bpcd main: Done converting args to CreateProcess
    >> format
    >> 16:06:26.121 [3476.3624] <2> bpcd main: new fork cmd =
    >> C:\Progra~1\VERITAS\NetBackup\bin\bpbkar32.exe
    >> -r 451352 -ru root -dt 0 -to 0 -clnt
    >>
    >> client-veritas -class HN-W2K-W_ALL-FS-1 -sched Weekly-Full -st FULL
    >> -bpstart_to
    >> 1800 -bpend_to 1800 -read_to 1800 -use_otm -fso -b
    >>
    >> client-veritas_1119279898 -kl 28 -use_ofb
    >> 16:06:26.121 [3476.3624] <2> bpcd main: Before CreateProcess
    >> 16:06:26.121 [3476.3624] <2> bpcd main: StdOutput assigned the value
    >> STDOUTSOCK
    >> 16:06:26.183 [3476.3624] <2> bpcd main: After CreateProcess, pid = 2264
    >> 16:06:26.183 [3476.3624] <2> bpcd exit_bpcd: exit status 0
    >> ----------->exiting
    >> 16:07:09.137 [4116.3548] <2> bpcd main: offset to GMT 0
    >> 16:07:09.137 [4116.3548] <2> bpcd main: Got socket for input 512
    >> 16:07:09.137 [4116.3548] <2> logconnections: BPCD ACCEPT FROM ?.?.188.2.907
    >> TO ?.?.190.53.13782
    >> 16:07:09.137 [4116.3548] <2> bpcd main: setup_sockopts complete
    >> 16:07:09.183 [4116.3548] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.356:
    >> no methods for address: no authentication required
    >> 16:07:09.183 [4116.3548] <2> bpcd main: no authentication required
    >> 16:07:09.183 [4116.3548] <2> bpcd peer_hostname: Connection from host
    >> media1-1-veritas
    >> (?.?.188.2) port 907
    >> 16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing
    >> MasterCluster-veritas
    >> and media1-1-veritas
    >> 16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing media2 and
    >> media1-1-veritas
    >> 16:07:09.183 [4116.3548] <2> bpcd valid_server: comparing media1 and
    >> media1-1-veritas
    >> 16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media2-1-veritas
    >> and media1-1-veritas
    >> 16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media2-2-veritas
    >> and media1-1-veritas
    >> 16:07:09.199 [4116.3548] <2> bpcd valid_server: comparing media1-1-veritas
    >> and media1-1-veritas
    >> 16:07:09.199 [4116.3548] <4> bpcd valid_server: hostname comparison succeeded
    >> 16:07:09.199 [4116.3548] <2> bpcd main: output socket port number = 732
    >> 16:07:09.199 [4116.3548] <2> bpcd peer_hostname: Connection from host
    >> media1-1-veritas
    >> (?.?.188.2) port 907
    >> 16:07:09.199 [4116.3548] <2> bpcd main: Peer hostname is media1-1-veritas
    >> 16:07:09.199 [4116.3548] <2> nb_bind_on_port_addr: bound to port 773
    >> 16:07:09.199 [4116.3548] <2> bpcd main: Got socket for output 700, lport
    >> = 773
    >> 16:07:09.199 [4116.3548] <2> bpcd main: Connected on output socket
    >> 16:07:09.199 [4116.3548] <2> bpcd main: Duplicated socket on stderr
    >> 16:07:09.199 [4116.3548] <2> bpcd main: <---- NetBackup 5.0GA 0
    >> ------------initiated
    >> 16:07:09.199 [4116.3548] <2> bpcd main: Not using VxSS authentication

    with
    >> media1-1-veritas
    >>
    >> Interface: ?.?.190.53 on Interface 0x1000003
    >> Internet Address Physical Address Type
    >> ?.?.190.90 mac-address dynamic
    >> ?.?.191.254 mac-address dynamic
    >>
    >> Interface: ?.?.139.10 on Interface 0x1000004
    >> Internet Address Physical Address Type
    >> ?.?.139.3 mac-address dynamic
    >> ?.?.139.13 mac-address dynamic
    >> ?.?.139.254 mac-address dynamic
    >> 16:07:09.262 [4116.3548] <2> bpcd main:
    >> 16:07:09.262 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    >> 16:07:09.293 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    >> 16:07:09.402 [4116.3548] <2> bpcd main: BPCD_READ_USERS_CONFIG_RQST
    >> 16:07:09.496 [4116.3548] <2> bpcd main: BPCD_GET_VERSION_RQST
    >> 16:07:09.590 [4116.3548] <2> bpcd main: BPCD_READ_HOST_CONFIG_RQST
    >> 16:07:09.699 [4116.3548] <2> bpcd main: BPCD_DISCONNECT_RQST
    >> 16:07:09.699 [4116.3548] <2> bpcd exit_bpcd: exit status 0
    >> ----------->exiting
    >>
    >> Thanks for looking at this!

    >
    >I show error 131 as being a client permission error, not a socket fail
    >error--is the socket fail error appearing on the media or master server?
    >This troubleshooting guide excerpt appears to point at a
    >hostname/DNS/routing issue:
    >
    >
    >NetBackup Status Code: 131
    >Message: client is not validated to use the server
    >
    >Explanation: The client name, as determined from the connection to the
    >server, did not
    >match any client name in the NetBackup configuration and there was no
    >altnames
    >configuration for this client on the master server. A client and server

    that
    >have multiple
    >network connections can encounter this problem if the name by which the
    >client is
    >configured is not the one by which its routing tables direct connections

    to
    >the server.
    >Recommended Action:
    >1. Examine the NetBackup Problems report.
    >2. Create a debug log directory for bprd and retry the operation. Check

    the
    >resulting
    >debug log to determine the connection and client names.
    >Depending on the request type (restore, backup, and so on.), you may need

    or
    >want
    >to:
    >Change the clientıs configured name.
    >Modify the routing tables on the client.
    >On the master server, set up an altnames directory and file for this client
    >(see the
    >NetBackup System Administratorıs Guide).
    >or
    >On a UNIX master server, create a soft link in the NetBackup image catalog.
    >3. Review ³Verifying Host Names and Services Entries² on page34.
    >4. Run the NetBackup Configuration Validation Utility (NCVU) -conf >option>
    >on the master server for the associated NetBackup clients. Note the client
    >hostname
    >checks in section seven.
    >
    >

    Hello,

    I am also facing the same problem. The log file pasted by the problem owner
    matches exactly to the message that I get in my Netbackup console. Actually
    in the above reply message posted I can see the reply given for status 131
    and not for status 13. Howver the error is status 13 with console displaying
    errno 131. So if someone has any solution for this please let me know. It
    would be of great help as I am trying to fix this issue for the past 2 weeks
    and in vain.

    In my environment we have master and Media server in Solaris 8, Netbackup
    5.1 MP4 and Client is Windows 2003 64 Bit edition with SP2 which is behind
    a firewall. I tried installing Netbackup 5.1 client and then upgraded the
    patch. But during installation of Netbackup 5.1 I see the message not able
    to connect to the master and media servers. However after instalation I am
    able to ping and telnet to both master and media server and also the other
    way too. Also I heard only MP4 will work on 64 bit edition and upgraded to
    MP4. I tried updating the services file in both system32\drivers\etc\services
    and SysWOW64\Drivers\etc\service both manually and automatically(netbackup
    application installation) to include netbackup ports. But nothing works.
    Even after upgrade it doesnt work. The problem part is that I dont have an
    installation utility which can install the application with MP4. I have to
    install the basic 5.1 version and then upgrade the patch to MP4. If someone
    has got a solution for this issue it would be of great help.

+ Reply to Thread