Np errors in the backup client errorlog indicate the opposite condition, that is the backup client is trying to read a response sent from the journal daemon which isn't available at the moment the read is being done.
This error can happen if the journal daemon ends (obviously a problem) or (I believe) if the response the backup client is looking for from the journal daemon is still in progress, meaning that the journal daemon hasn't finished processing/sending it. In most cases the response is ready when the backup client goes to read it, but if it isn't the backup client will keep trying to read the response until it either arrives or a timeout occurs (don't know the exact wait time of the top of my head). That being said, I think development (myself) needs to look at the np error logging on both sides and try to eliminate logging messages which aren't really errors, but in some situations it's difficult to determine if an error condition is legitimate and should be logged or if it is innocuous and can be ignored. Hope this helps ...... Pete Tanenhaus Tivoli Storage Solutions Software Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 02/11/2003 10:13 AM --------------------------- "Magura, Curtis" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/11/2003 09:27:26 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: journal errors - return code 121 \\.\pipe\jnl Pete, What about the message - 02/11/2003 04:02:14 NpPeek: No data. ? We are also seeing this daily in dsmserror on the same clients. Is there a connection? Curt Magura Lockheed Martin EIS Orlando, Fla. 321-235-1203 -----Original Message----- From: Pete Tanenhaus [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 9:18 AM To: [EMAIL PROTECTED] Subject: Re: journal errors - return code 121 \\.\pipe\jnl This error occurs when the journal daemon process attempts to send a response on a named pipe provided by a backup client process and the pipe no longer exists or isn't valid. This can happen if the backup process/session ends or closes the pipe before the journal daemon sends or is finished sending the response or in some cases when the journal daemon is shutting down and cleaning up resources. By itself the error is innocuous but I understand it is annoying to see error messages in the log which can't be explained. Hope this helps .... Pete Tanenhaus Tivoli Storage Solutions Software Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 02/11/2003 09:14 AM --------------------------- "Magura, Curtis" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/11/2003 06:49:34 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: journal errors - return code 121 \\.\pipe\jnl Don't have good news other to say that I still see the message at 5.1.5.9 of the client talking to 5.1.5.4 server. Haven't had time to call the support center yet. Working a different call with the support center related to cleanup backupgroups on one of the servers that just went to 5.1.5.4! Curt Magura Lockheed Martin EIS Orlando, Fla. 321-235-1203 -----Original Message----- From: chris rees [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 3:34 AM To: [EMAIL PROTECTED] Subject: journal errors - return code 121 \\.\pipe\jnl Hi All I'm getting the following from a new client that is running journaling. TSM Client is 5.1.5.2, server is 5.1.5.4. 10-02-2002 09:20:05 NpOpen : Named pipe error connecting to server WaitOnPipe failed. NpOpen: call failed with return code:121 pipe name \\.\pipe\jnl I see there was a similar thread last week ( G.Gill and C.Magura )and wondered if you guys got any further with it. We have a few clients at the above levels using journaling but only 1 seems to be giving the pipe problem. TIA Chris _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail
