On Sat, 14 Jul 2007, Kyriakos Ginis wrote:
> On Fri, Jul 13, 2007 at 05:21:19PM +0300, Stathakopoulos Giorgos wrote:
> > Hello all,
> >
> > Our CE (ce01.kallisto.hellasgrid.gr) is overloaded due to many
> > globus-job-manager processes of
> >
> > 1) globus-job-manager -conf /opt/globus/etc/globus-job-manager.conf
> > -type fork -rdn jobmanager-fork -machine-type unknown -publish-jobs
> > 2) /usr/bin/perl /opt/globus/libexec/globus-job-manager-script.pl -m pbs
> > -f /tmp/gram_xxxxx -c remote_io_file_create
> > 3) /opt/globus/libexec/globus-gass-cache-util -cleanup-tag -t
> > https://ce01.kallisto.hellasgrid.gr:xxxxx/xxxxx/xxxxxxx
> >
> > Above processes start with a ratio of about 50/hour and they stay
> > running. After a few hours CE stops responding and it runs out of
> > memory. We have to reboot it to get it back.
> >
> > We have the latest update of middleware installed.
> >
> > Any ideas?
>
>
> Hello,
>
> We also have observed a recent increase in the processes spawned through
> the fork jobmanager. Has anything been changed recently regarding the
> way the jobs are submitted and monitored by the RB/WMS?
No. Can you check if those processes are coming from a certain RB or WMS?
Look e.g. with "netstat -a". Which accounts show that problem?
|