Posted by Barbara Brazil (68.122.126.15) on December 01, 2004 at 17:00:25:
In Reply to: Help interpreting CS32 messages posted by Tom Fulton on December 01, 2004 at 09:21:31:
Tom:
In version 4.05 of Comet Serve we added E9F when Comet fails to detect E34 or E35. We did that as a diagnostic measure to prevent a potential file system problem. Furthermore, E9F can occur following the attempted close of the system LUN (50) following an FSTAT. FSTAT on type 'S' keyed files will cause this to be logged to cometServe but there should be no negative impact on Comet. The client isn't erroring out is it? The error 33 could be a lock error from Windows. CometServe will retry the read up to 10 times before issuing a fatal error. If you are only seeing this in the CometServe log, and they are in groups of fewer than 10, the retry logic is working as intended.
bb