Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Odd error messages from bperror..... 1

Status
Not open for further replies.

jdespres

MIS
Aug 4, 1999
230
0
0
US
I'm getting these messages



11/08/2004 14:08:08 cscbk02 wnd4n997 could not send server status message
11/08/2004 14:08:09 cscbk02 wnd4n997 Could not set linger value on socket.
Errno = 22: Invalid argument

11/08/2004 14:18:01 cscbk02 wnd4n997 could not write KEEPALIVE to COMM_SOCK

NBU everywhere is NBU 4.5 fp6...
Master & Media Server are Solaris 2.8
and the client is Windows.....

The backups appear to be functional... but extremely slow!

Joe Despres
 
Hi Joe,

we encounter this phenomenon in our environment with Win clients as well (Master & Media Server are running on Solaris 8. We are on NBU 5.1).
Does this happen with your Brick Level backups? They are in general very slow due to backup every mailbox on it's own; at least that's were we often get these messages.
I reckon it is simply a communication timeout. The media server does not receive any answer from the client over a certain period of time as you might probably see in your error logs as well:

bpdm unable to perform read from client socket, connection may have been broken
1099953370 1 4 16 media server 1015528 1015528 0 client bpbrm could not send server status message
1099953371 1 4 8 media server 1015528 1015528 0 client bpbrm Could not set linger value on socket. Errno = 22: Invalid argument
1099953372 1 68 4 media server 1015528 1015528 0 client bpsched CLIENT client POLICY policy SCHED schedule=brick EXIT STATUS 42
(network read failed)
1099953372 1 4 16 media server 1015528 1015528 0 client bpsched backup of client client exited with status 42 (network read failed)

mrjazz
 
Hi Joe,

What are the chances of rebooting or stopping and starting NBU services on the client server? I had this issue a while back on a solaris server (client) and a rebooot of the the server solved this problem.
A reboot will free up the socket used by bpbrm to allow NBU re-initiate the request all over again.


Valoky
 
Looks like a reboot did the trick..... Atleast I don't see any of those error's!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top