Hi all
I am a bit confused, or someone does not know what is in the LCG2.3.1
distro
I wget your edg-rgma-restart-all script, and diff'ed with the one
I have presently in my mon box, and it is the same, so the rgma version
presently in the testbed should be ok, i.e.:
edg-rgma-common-3.4.36-sl3
I chacked the compiled date and its 1 Dec 2004
[root@se01 libexec]# rpm -qi edg-rgma-common-3.4.36-sl3
Name : edg-rgma-common Relocations: /opt/edg
Version : 3.4.36 Vendor: (none)
Release : sl3 Build Date: Wed 01 Dec 2004 04:23:14
PM WET
Install Date: Sat 12 Feb 2005 01:07:13 PM WET Build Host:
rgma03.pp.rl.ac.uk
Group : Grid Source RPM:
edg-rgma-common-3.4.36-sl3.src.rpm
Size : 9941865 License: EU DataGrid License
Signature : (none)
Packager : DataGrid WP3
URL : http://hepunx.rl.ac.uk/grid/wp3
Summary : R-GMA Common Files
Description :
Grid Middleware arising for EU-DataGrid project.
R-GMA is a relational implementation of Grid Monitoring Architecture as defined
by Global Grid Forum.
This contains the common files which are used by many other pacakages.
I did't substituted the script from the release with this one
so the diff is not facked
OK, since don't remember when I don't have the problems of stoping tomcat4
although I had it when I upgraded to LCG2.3.0.
cheers
Mario
Quoting "Wilson, AJ (Antony)" <[log in to unmask]>:
> Hi Cal
>
> A replacement script can be found at
> http://hepunx.rl.ac.uk/egee/jra1-uk/LCG/edg-rgma-restart-all
> We have passed a new set of rpms to LCG which we hope will be released at the
> end of the month
>
> Regards
> Antony
>
> > -----Original Message-----
> > From: LHC Computer Grid - Rollout
> > [mailto:[log in to unmask]] On Behalf Of Charles Loomis
> > Sent: 14 March 2005 06:41
> > To: [log in to unmask]
> > Subject: Re: [LCG-ROLLOUT] rgma going mad on 2.3.1
> >
> >
> > Hi Jeff,
> >
> > This is indirectly caused by the rgma-servlet-monitor cron
> > entry which tries to restart the rgma daemons (and hence
> > tomcat) every so often. Unfortunately, the tomcat4 shutdown
> > script tries to exit gracefully and never succeeds in
> > stopping the processes. This eventually exhausts the system
> > memory, ....
> >
> > Eric Fede had found this sometime back and I believe
> > submitted a bug report for it. (He can confirm this.) In
> > the meantime, in /etc/init.d/tomcat4 you can add the hack
> > below to the stop method to ensure that the shutdown actually happens:
> >
> > stop() {
> > echo -n "Stopping $TOMCAT_PROG: "
> >
> > if [ -f /var/lock/subsys/tomcat4 ] ; then
> > if [ -x /etc/rc.d/init.d/functions ]; then
> > daemon --user $TOMCAT_USER $TOMCAT_SCRIPT stop
> > else
> > su - $TOMCAT_USER -c "$TOMCAT_SCRIPT stop"
> > fi
> > RETVAL=$?
> >
> > # Hack to ensure that processes really die.
> > sleep 15
> > killall -u=tomcat4 java
> > sleep 5
> >
> > tc4run=1
> > until [ $tc4run = '0' ]
> > do
> > tc4run=`ps -aux | grep catalina | grep -v grep |
> > grep $TOMCAT_USER -c\`
> > sleep 1
> > done
> > rm -f /var/lock/subsys/tomcat4 /var/run/tomcat4.pid
> > fi
> >
> > echo
> >
> > [ $RETVAL = 0 ]
> >
> > }
> >
> > Perhaps this has been fixed in some official way, but I've
> > failed to notice. If so, I'd appreciate a pointer to the
> > official fix.
> >
> > Cheers.
> >
> > Cal
> >
> >
> >
> > Jeff Templon wrote:
> > > Hi,
> > >
> > > we've seen our R-GMA service go nuts a few times since upgrading to
> > > 2.3.1. I just now caught it in the act: load on the
> > machine was about
> > > 150. Checking, there were an awful lot of 'ps' processes floating
> > > around. Here is a snippet of the output of pstree:
> > >
> > > java
> > > crond86*[crondshshedg-rgm+
> > > 4*[crondshshedg-rgma+
> > > 2*[crondshshedg-rgma+
> > > 5*[crondshshedg-rgma+
> > > 6*[crondshshedg-rgma+
> > > 2*[crondshshedg-rgma+
> > > 4*[crondshshedg-rgma+
> > > crondshshedg-rgma-se+
> > > crondshshedg-rgma-se+
> > > 5*[crondshshedg-rgma+
> > > crondshshedg-rgma-se+
> > > 2*[crondshshedg-rgma+
> > > crondshshedg-rgma-se+
> > > crondshshedg-rgma-se+
> > > crondshshedg-rgma-se+
> > > crondshshedg-rgma-se+
> > >
> > >
> > > looks like the culprits are:
> > >
> > > - edg-rgma-restart
> > > - edg-rmga-service-status
> > > - edg-rgma-servlet-status
> > > - edg-rgma-servlet-monitor
> > >
> > > and there are hundreds of processes running that are all trying to
> > > stop tomcat4 ...
> > >
> > > anybody else seeing this??
> > >
> > > JT
> > >
> >
>
|