On 03/29/2012 11:37 AM, Mario Kadastik wrote:
>>>> You can see the following link:
>>>> https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#3_18_Job_purging
>>> Yes, and this would be marvellous if it actually worked nicely :) If I kill 8000 jobs in the scheduling system the CREAM will be busy state checking and reporting to WMS etc for ages with MySQL load at 100%. I've even seen BNotifier just die under the load. It seemed to me at the time that it tried to report ALL jobs to the WMS (might have been only one WMS had sent them) together so it consumed as much RAM as I gave the node and died. I at some point gave the CREAM VM 22GB of RAM that BNotifier consumed in half a day and still it was stuck at the time.
>> Which CREAM version are you using?
>> What's the output of the command "rpm -qa | grep cream"?
> emi-cream-ce-1.0.0-1.sl5.x86_64
>
>>> Still it would be good to know how to clean this stuff also manually because last time I checked the manual Job purge script failed miserably because it couldn't connect to DB through Java.
>> What's exactly the error reported by the JobDBAdminPurger script?
>
> [root@mars ~]# JobDBAdminPurger.sh -u cream -p ##### -s ABORTED
> - Initializing CA certificate store from directory: /etc/grid-security/certificates
> JobDBAdminPurger error: org.gjt.mm.mysql.Driver
There is a problem with the classpath in the JobAdminPurger script for
the mysql-connector-java.jar library.
I need the glite-ce-cream-utils version.
What's the output of the command "rpm -qa | grep cream"?
Cheers,
E r i c.
>
> I replaced the password with #####
>
> Mario Kadastik, PhD
> Researcher
>
> ---
> "Physics is like sex, sure it may have practical reasons, but that's not why we do it"
> -- Richard P. Feynman
>
>
|