Dylan Penhale wrote:
Yesterday we had two hosts fail to render due to the following error (in
rushd.log). I haven't seen it before:
02/06,20:30:37 ERROR //SERVER/SHARE/rush/rush_logs): Insufficient system resources exist to complete the requested service.
I'm guessing network timeouts, has anyone seen this before?
You might want to check the system event log on or around that time stamp
for more specific information, since the OS may have been low on memory,
file handles, or some such. You might also check the windows event log on the
file server itself.
In this context, I believe the host in question was trying to either
open a file or test read/write access permissions on the file server,
and could not due to the above error from the OS.
What the error means precisely (disk full? out of memory? out of file handles?)
is not clear; this is the actual Windows operating system error message the
operation returned.
Thing is, I think you may have trimmed some critical info from the error
message to help identify what operation was in progress at the time.
Can you include the complete error message as it reads in the file?
I believe there may be info to the left of the //SERVER/SHARE part
(due to the dangling close paren) which probably indicates the operation
that was in progress at the time the error occurred.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|