From: Dylan Penhale <dylan@(email surpressed).au> Subject: Insufficient system resources Date: Mon, 06 Feb 2006 18:14:30 -0500 |
Msg# 1215 View Complete Thread (2 articles) | All Threads Last Next |
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? _________________________________________ Dylan Penhale Systems Administrator Fuel International 65 King Street Newtown 2042 Sydney Australia p. (Tel# suppressed) f. (Tel# suppressed) |
From: Greg Ercolano <erco@(email surpressed)> Subject: Re: Insufficient system resources Date: Mon, 06 Feb 2006 20:06:28 -0500 |
Msg# 1216 View Complete Thread (2 articles) | All Threads Last Next |
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) |