cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

Server status = 13

Rick_Flair
Level 4
Partner Accredited Certified
Hi all,

I am having a problem with what I believe is related to port issues. We have a Win2003 NBU5.1 client called TestClient in a DMZ, while the Solaris 8 NBU5.1mP3 master/media called TestServer is on the other side. Backups of this client are ending due to a file read failure (Status 13).

* on the master server's host properties > client attributes, I have selected BPCD connect-back with VNETD port.
* the port ranges are set to default; exactly as displayed in the 5.1 SysAdmin Unix Guide.
* all ports, NIC cards and switches are set to the same media and transport type.
* the firewall has the necessary ports open
* a different Win2003 client with the same settings experiences no issues backing up.


Here is a section of the all Log Entires report
Error 14674 Backup backup of client TestClient exited with status 13 (file read failed) bpsched
Error 14674 Backup system call failed - Connection reset by peer (at child.c.1132) bptm
Error 14674 Backup socket read failed: errno = 131 - Connection reset by peer bpbrm
Error 14674 Backup unable to perform read from client socket, connection may have been broken bptm
Error 14674 Backup could not send server status message bpbrm
Warning 14674 Backup Could not set linger value on socket. Errno = 22: Invalid argument


Here is a section of the bpbrm, showing where the backup goes awry (For the sake of privacy, I have replaced the last two octects of the IP Address with "xx.xxx")

22:47:22.023 <2> bpbrm send_bpsched_connected_msg: sending bpsched msg: CONNECTED TO CLIENT FOR TestClient_1138794436
22:47:23.362 <2> bpbrm readline: Returning READ_INFORM_WHEN_DONE
22:47:23.362 <2> bpbrm read_backup_start: from client TestClient: read client start message
22:47:23.362 <2> bpbrm write_continue_backup: wrote CONTINUE BACKUP on COMM_SOCK <8>
22:47:23.362 <2> bpbrm write_filelist: wrote C:\ on COMM_SOCK
22:47:23.362 <2> bpbrm write_filelist: wrote D:\ on COMM_SOCK
22:47:23.362 <2> bpbrm write_filelist: wrote CONTINUE on COMM_SOCK
22:47:23.363 <4> bpbrm handle_backup: from client TestClient: TRV - BACKUP 1/02/2006 10:47:28 PM TestClient WINDOWS_FILE Daily_Incremental_Backup INCR
22:47:27.581 <16> bpbrm readline: socket read failed: errno = 131 - Connection reset by peer
22:47:27.584 <2> nb_bind_on_port_addr: bound to port 54594
22:47:27.584 <2> logconnections: BPJOBD CONNECT FROM 10.16.xx.xxx.54594 TO 10.16.xx.xxx.13723
22:47:27.587 <2> vauth_authentication_required: vauth_comm.c.793: no methods for address: no authentication required
22:47:27.589 <2> vauth_connector: vauth_comm.c.193: no methods for address: no authentication required
22:47:27.589 <2> job_authenticate_connection: no authentication required
22:47:27.594 <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.838: VxSS magic: 1450726224 0x56785350
22:47:27.596 <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.932: Not using VxSS authentication: 2 0x00000002
22:47:27.596 <2> job_connect: Connected to the host testserver.com.au contype 10 jobid <14691> socket <10>
22:47:27.596 <2> job_connect: Connected on port 54594
22:47:27.596 <2> set_job_details: Sending Tfile jobid (14691)
22:47:27.596 <2> set_job_details: LOG 1138794447 16 bpbrm 14447 socket read failed: errno = 131 - Connection reset by peer

22:47:27.596 <2> set_job_details: Done
22:47:27.791 <2> job_monitoring_exex: ACK disconnect
22:47:27.791 <2> job_disconnect: Disconnected
22:47:27.866 <2> clear_held_signals: clearing signal mask stack, mask_stack_depth = 0
22:47:27.866 <2> inform_client_of_status: INF - Server status = 13
22:47:27.866 <2> sighdl: pipe signal
22:47:27.866 <2> put_long: (11) network write() error: Broken pipe (32); socket = 8
22:47:27.866 <16> inform_client_of_status: could not send server status message

22:47:27.868 <2> nb_bind_on_port_addr: bound to port 54601
22:47:27.868 <2> logconnections: BPJOBD CONNECT FROM 10.16.xx.xxx.54601 TO 10.16.xx.xxx.13723
22:47:27.870 <2> vauth_authentication_required: vauth_comm.c.793: no methods for address: no authentication required
22:47:27.872 <2> vauth_connector: vauth_comm.c.193: no methods for address: no authentication required
22:47:27.872 <2> job_authenticate_connection: no authentication required
22:47:27.873 <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.776: Ignoring VxSS authentication: 2 0x00000002
22:47:27.873 <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.932: Not using VxSS authentication: 2 0x00000002
22:47:27.876 <2> job_connect: Connected to the host testserver.com.au contype 10 jobid <14691> socket <10>
22:47:27.876 <2> job_connect: Connected on port 54601
22:47:27.876 <2> set_job_details: Sending Tfile jobid (14691)
22:47:27.876 <2> set_job_details: LOG 1138794447 16 bpbrm 14447 could not send server status message

22:47:27.876 <2> set_job_details: Done
22:47:27.973 <2> job_monitoring_exex: ACK disconnect
22:47:27.973 <2> job_disconnect: Disconnected
22:47:27.998 <8> inform_client_of_status: Could not set linger value on socket. Errno = 22: Invalid argument
22:47:28.000 <2> nb_bind_on_port_addr: bound to port 54606
22:47:28.000 <2> logconnections: BPJOBD CONNECT FROM 10.16.xx.xxx.54606 TO 10.16.xx.xxx.13723
22:47:28.002 <2> vauth_authentication_required: vauth_comm.c.793: no methods for address: no authentication required
22:47:28.004 <2> vauth_connector: vauth_comm.c.193: no methods for address: no authentication required
22:47:28.004 <2> job_authenticate_connection: no authentication required
22:47:28.005 <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.776: Ignoring VxSS authentication: 2 0x00000002
22:47:28.005 <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.932: Not using VxSS authentication: 2 0x00000002
22:47:28.006 <2> job_connect: Connected to the host testserver.com.au contype 10 jobid <14691> socket <10>
22:47:28.006 <2> job_connect: Connected on port 54606
22:47:28.006 <2> set_job_details: Sending Tfile jobid (14691)
22:47:28.006 <2> set_job_details: LOG 1138794448 8 bpbrm 14447 Could not set linger value on socket. Errno = 22: Invalid argument

22:47:28.006 <2> set_job_details: Done
22:47:28.102 <2> job_monitoring_exex: ACK disconnect
22:47:28.102 <2> job_disconnect: Disconnected
22:47:28.111 <2> bpbrm brm_sigcld: SIGCLD caught by bpbrm
22:47:28.112 <2> bpbrm brm_sigcld: bpbrm child 14447 exit_status = 13, signal_status = 0
22:47:28.112 <2> bpbrm brm_sigcld: child 14447 exited with status 13: file read failed

22:47:28.112 <2> bpbrm send_status_to_parent: bpbrm child is done, but the media manager child is not.
22:47:28.112 <2> bpbrm tell_mm: sending media manager msg: STOP BACKUP TestClient_1138794436
22:47:28.621 <2> bpbrm read_media_msg: read from media manager: EXIT TestClient_1138794436 150
22:47:28.621 <2> bpbrm process_media_msg: media manager for backup id TestClient_1138794436 exited with status 150: termination requested by administrator
6 REPLIES 6

Stumpr2
Level 6
I had a problem with 13's that were fixed when I made changes to the Solaris master server kernel.
Minimum system requirements for the Solaris kernel when used with VERITAS NetBackup (tm), defined in /etc/system
http://seer.support.veritas.com/docs/238063.htm

Rick_Flair
Level 4
Partner Accredited Certified
Thanks Bob,

We'll give this a go, but it seems odd that another Win2003 client in the DMZ with apparently the same config is backing up okay. To me this suggests that the master server is operating correctly.

Nonetheless, I'll let you all know how this works.

- Jason B

Rick_Flair
Level 4
Partner Accredited Certified
Hi all,

The problem still persists....

I have verified the following links are correctly adhered:

http://support.veritas.com/docs/238472
http://support.veritas.com/docs/238063

Any other suggestions?Message was edited by:
Jason Blakely

Stumpr2
Level 6
I would make my troubleshooting starting point here:
22:47:27.581 <16> bpbrm readline: socket read failed: errno = 131 - Connection reset by peer

From the troubleshooter:
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.

MayurS
Level 6
Hi,

open command promt on the DMZ server and post the output of TASKLIST command

Rick_Flair
Level 4
Partner Accredited Certified
Hi all,

Upgrading the client from 5.1GA to 5.1MP3, like the master/media server, appears to have fixed the problem. Thanks for your input.

Regards,
Jason B