Video Screencast Help

Windows maching code 23 and 58 errors

Created: 04 Feb 2014 • Updated: 18 Feb 2014 | 4 comments
This issue has been solved. See solution.

Hi,

We have a netbackup client that is receiving netbackup code 23 (socket read and 58 client can’t connect codes)  we had the Windows Sys Admin reboot the server. The subsequent backups have gone back to receiving the 23 an 58 errors.

The connections seem fine on the commands can anyone shed any light on this?

Hardware info

Windows 2003 sp2 using 7.5.0.1 client

Netbackup master server Linux (7.6.0.1) <<<this is a recent upgrade 

The bpcd and bpfis logs are attached.  The other logs including the bpkar and bptm were empty even after a couple of days.

Thanks

Operating Systems:

Comments 4 CommentsJump to latest comment

Mark_Solutions's picture

No buffer space available - havent see that since a 6.x bug!

What state is that server in?

Is it OK for disk space and memory - it does the snapshot OK but looks like it just cannot cope with anything else

Check the Application and System event logs on the client to see what gets logged around the time of the backup

Is this a normal windows backup?

Tell us as much as you can about this client and what you are backing up

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Marianne's picture

 <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED status: FAILED, (10) SOCKET_FAILED; system: (10055) No buffer space available

Seems to be a Windows problem - running out of TCP/IP sockets or else third-party software (such as Anti-Virus or other security software) preventing outgoing connections.

You need your Windows team to troubleshoot outside of NBU...

See http://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults/?Number=KBA-01196

WSAENOBUFS (10055) No buffer space available 

An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full. 

This error indicates a shortage of resources on your system. It can occur if you're trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that doesn't return system resources (like memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem. You can monitor available memory with Program Manager's 'Help/About...' command. 

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
nbustarter380's picture

Mark, Marianne,

 

Thanks, for your responses

What state is that server in?

The connection to the server is fine it's available if thats what you mean?

 

Is it OK for disk space and memory

This seems ok   ...C: drive  5.29GB free space   >> D: drive 15.4 free space>>>  S: drive 1.97 Free space

Memory 7.75 GB Ram

As far as I can tell the Application and System event logs  don't show anything thing trying to login at the time of the backup.

Is this a normal windows backup?

Yes, incremental backups and the code 23/58 happens occur for every backup.

Marianne,

Thanks...we having the Windows sys admin take a look at this. I believe there is a way to increase the buffer

Best regards

 

 

 

 

 

 

 

Marianne's picture

Your sys admins will probably need to log a call with Microsoft.

As per my post above - this is not a NBU problem.

Some software on this system seems to be preventing socket setup. Or simply too many other processes consuming all available sockets.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION