Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Known issues | ||||||||
Line: 74 to 74 | ||||||||
this most probably means "qstat" and "qacct" commands can not be successfully executed by tomcat. This could happen by several reasons:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
The BUpdaterSGE daemons does not inherits the correct GE environment variables | ||||||||
Line: 106 to 106 | ||||||||
error: unable to send message to qmaster using port 15020 on host "xxxxxxxx": can't set CA chain file | ||||||||
Added: | ||||||||
> > | The accounting file is not shared in the CreamCE or not updated on the flyBUpdaterSGE needs to consult the GE accounting file to determine how did a given job ended. Therefore, the GE accounting file must be shared between the GE SERVER / QMASTER and the CREAM CE. Moreover, to guarantee that the accounting file is updated on the fly, the GE configuration should be tunned (using qconf -mconf) in order to add under the reporting_params the following definitions: accounting=true accounting_flush_time=00:00:00 | |||||||
Significant changes introduced with Torque 2.5.7-1The updated EPEL5 build of torque-2.5.7-1 as compared to previous versions enables munge[1] as an inter node authentication method. Please see |