It seems like it was a memory issue. After a rest of some 12 hours, it works fine. But i'll look into the .gass_cache input/out errors. Most probably a bad disk mounting
thanks ---------------------------------------- > Date: Mon, 18 Aug 2008 21:02:09 -0500 > From: [EMAIL PROTECTED] > Subject: Re: [gt-user] Gram Error code 3 (No Resources) > To: [EMAIL PROTECTED] > CC: [email protected] > > Whenever I have seen gram error code 3 it's an actual hardware problem. > An input/output error is not only a corrupted .gass_cache, it is > probably a bad disk. You can also get a GRAM 3 error if you're out > of memory. > > Steve Timm > > > > ------------------------------------------------------------------ > Steven C. Timm, Ph.D (630) 840-8525 > [EMAIL PROTECTED] http://home.fnal.gov/~timm/ > Fermilab Computing Division, Scientific Computing Facilities, > Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader. > > On Tue, 19 Aug 2008, Omer Jilani wrote: > >> >> Hi all, >> >> I'm submitting a job using globus command and getting an error. >> >> # globus-job-run ce.glite.ecdf.ed.ac.uk:2119/jobmanager-lcgsge -q ecdf >> '&(executable="bin/myexe") (maxWallTime="360.0")' >> >> GRAM Job failed because an I/O operation failed (error code 3) >> >> I checked my disk space and there is plenty of space >> >> permissions on .gass_cache: >> >> drwxr-xr-x 4 user group 8.0K Aug 19 01:05 .gass_cache >> >> On checking the gram_job_mngr log file it returns with error when trying: >> >> in globus_gram_job_manager_reporting_file_create() >> JM: not reporting job information >> JM: in globus_gram_job_manager_history_file_create() >> Job Manager State Machine (entering): GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED >> Job Manager State Machine (entering): >> GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_CLOSE_OUTPUT >> JM: NOT empty client callback list. >> JM: sending callback of status 4 (failure code 3) to >> https://129.215.59.48:50000/1219104215658. >> >> I tried to delete the .gass_cache directory and it gave me errors for some >> directories >> # rm -rf .gass_cache >> rm: cannot remove '.gass_cache//global/md5/1e/4e....' Input/output error >> .... >> >> Did something in the .gass_cache get corrupted, which is causing problems >> for the gram >> manager? >> >> Any help is highly appreciated. >> >> thanks >> omer >> _________________________________________________________________ >> Discover the new Windows Vista >> http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE >> > _________________________________________________________________ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
