From: 田中 義一 <yt...@ni...> - 2010-03-08 19:26:13
|
Hi, Thank you for your quick reply. You have thought that problems occurs when staging. But the too many file problems ocuurs even in the following job without data-staging <?xml version="1.0" encoding="UTF-8"?> <JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl"> <JobDescription> <Application> <POSIXApplication xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl-posix"> <Executable>/bin/hostname</Executable> <Output>host.txt</Output> <WorkingDirectory>./tmp</WorkingDirectory> </POSIXApplication> </Application> </JobDescription> <MyProxy xmlns="urn:gridsam:myproxy"> <ProxyServer>*******</ProxyServer> <ProxyServerUserName>******</ProxyServerUserName> <ProxyServerPassPhrase>******</ProxyServerPassPhrase> </MyProxy> </JobDefinition> Regards, Yoshikazu Tanaka >Hi, >We are aware that there is an issue relating to gsiftp transfers. >The problem seems to be an unclosed socket when staging files via gsiftp. >When a file is staged back to gridsam, the connection used for the transfer >remains in CLOSED_WAIT indefinitely. I believe that the underlying commons >vfs library, or perhaps ultimately part of the cog kit is not releasing the >resources correctly. >I am currently looking into the problem, and hope to have a fix shortly. >Regards, > Justin >On 2 Mar 2010, at 07:07, 田中 義一 wrote: >> <TooManyFiles> error occurs when we have submitted more than 500 jobs since >> invoking gridsam. >> We have observed directory in /proc/omii-server process#/fd, >> then we have understood that 1 socket file per 1 job remains left after job- >> completion. >> Please teach me how to destory job information after job-completion. Even if using gridsam-status, gridsam-terminate command, these socket files does't disappear. >> >> Environment >> CentOS 5.3 >> GridSAM 2.1.4 >> gridsam-jobmanager globus (GT 4.0.5) >> >> Center for Grid Research and Development(NAREGI) >> Yoshikazu Tanaka >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> GridSAM-Discuss mailing list >> Gri...@li... >> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss >-- >Justin Bradley >Software Engineer >j.b...@om... >OMII-UK >Bay 23, 4067, B32 >University of Southampton |