Pete, think you said it all with the statement below! Very confusing in the current state to decide if there is a problem or not.
"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." Curt Magura Lockheed Martin EIS Orlando, Fla. 321-235-1203 -----Original Message----- From: Pete Tanenhaus [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 10:27 AM To: [EMAIL PROTECTED] Subject: Re: journal errors - return code 121 \\.\pipe\jnl 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
