[CREAM-76] Minor issues from INFN-T1 Created: 27/May/13 Updated: 27/May/13 Due: 15/May/13 Resolved: 27/May/13 |
|
Status: | Resolved |
Project: | CREAM |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | 1.15.2 |
Security Level: | Public (Visbile by non-authn users.) |
Type: | Bug | Priority: | Major |
Reporter: | Paolo Andreetto | Assignee: | Paolo Andreetto |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
This ticket duplicates https://savannah.cern.ch/bugs/?101108 and refers to https://ggus.eu/ws/ticket_info.php?ticket=92492 The fix concerns: 1) After configuring with yaim, many tomcat6 errors are logged in catalina.out: java.lang.IllegalArgumentException: Document base /usr/share/tomcat6/webapps/ce-cream-es does not exist SEVERE: A web application appears to have started a thread named [Timer-4] but has failed to stop it. This is very likely to create a memory leak. SEVERE: A web application created a ThreadLocal with key of type [null] (value [org.apache.axiom.util.UIDGenerator$1@4a88e4c0]) and a value of type [long[]] (value [[J@24edb15c]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. After a while the ce starts swapping and runs out of health. WORKAROUND: 2) [root@ce01-lcg ~]# cat /etc/glite-ce-cream/log4j.properties | egrep 'MaxFileSize|MaxBackupIndex' These are too little in a production environment. An entire job lifecycle doesnt fit in 20MB of logs. furthermore, any run of yaim restores the too little values. WORKAROUND: chattr +i /etc/glite-ce-cream/log4j.properties SOLUTION: Have this fixed in the next update 3) After configuring with yaim, services are up, but the ce remains unresponsive: [sdalpra@ui01-ad32 ~]$ glite-ce-job-submit -a -r ce01-lcg.cr.cnaf.infn.it:8443/cream-lsf-dteam my.jdl [sdalpra@ui01-ad32 ~]$ glite-ce-job-submit -a -r ce01-lcg.cr.cnaf.infn.it:8443/cream-lsf-dteam my.jdl Tomcat is actually in a ill state: [root@ce01-lcg ~]# service tomcat6 status WORKAROUND: Then it works: SOLUTION: Have this fixed in the next update |