Forum Discussion

Rob_Dullaart's avatar
Rob_Dullaart
Level 5
10 years ago

Novell client error 41

I've been troubleshooting an old Novell-client for a few days now, there are some threads here which write about Novell clients ending with error 41. But these didn't solve my problem. So I wonder if you have any ideas. 

My masterserver runs on Netbackup version 7.6.0.1 on WIndows 2008
The Novell-client is version 6.5, Netware v6. 

I found this in the bpcd-log on the Novell-client.

bpcd::bpcd_validate_state: INF - attempt to validate server as masterserver.domain (err = 69)

So I checked the resolv.cfg, I placed the master-server and the media-server in the Novell-clients host-file. 
I tried to do a ping from the Novell-client to the master and media-server. The ping went well. Also I have restarted the Novell-client. I have some ancient knowledge of Novell. 

I have a attached the bpcd log of the Novell-client.

Any clues what I can do to solve this? 

7.6
Backing Up
Backup and Recovery
Compatibility
Configuring
Error messages
NetBackup
Not Applicable
Troubleshooting

4 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Not initial comms error as bpcd is exiting with status 0.

    There are TCP errors responsible for break in communication:

    10:54:57: [663.1280] <16> dtcp_read: TCP - failure: recv socket (11) (TCP 54: Connection reset by peer)
10:54:58: [663.1242] <2> bpcd::bpcd_accepted_state: BPCD - Starting process
10:54:58: [663.1280] <2> tar_base::V_vTarMsgM: FTL - tar file write error (40)
10:54:58: [663.1280] <16> dtcp_write: TCP - failure: send socket (15) (TCP 32: Unknown error)
10:54:58: [663.1280] <16> dtcp_write: TCP - failure: attempted to send 32 bytes
10:54:58: [663.1280] <2> tar_base::V_vTarMsgM: INF - EXIT STATUS 14: file write failed
10:54:58: [663.1280] <16> dtcp_write: TCP - failure: send socket (15) (TCP 32: Unknown error)
10:54:58: [663.1280] <16> dtcp_write: TCP - failure: attempted to send 40 bytes
    10:55:00: [663.1280] <16> dtcp_shutdown: TCP - failure: shutdown socket (15) (TCP 57: Socket is not connected)
10:55:00: [663.1280] <16> dtcp_shutdown: TCP - failure: shutdown socket (11) (TCP 57: Socket is not connected)
10:55:00: [663.1280] <16> dtcp_read: TCP - failure: recv socket (11) (TCP 54: Connection reset by peer)
10:55:00: [663.1280] <16> dtcp_read: TCP - failure: recv socket (15) (TCP 54: Connection reset by peer)

    You need to get Netware OS and network team involved.

    I cannot see anything from NBU point of view causing the issue.

  • Rob_Dullaart's avatar
    Rob_Dullaart
    Level 5
    10 years ago

    Hello Marianne, 

    Thanks for your quick response. I am sitting next to the Novell-team. Also I can do some Novell tasks myself. Are there any other logs I can access or enable? 

    Rob

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Nothing from NBU point of view.

    No idea what to look at OS or TCP level.