Actions
Feature #1728
openAdd appion script to test for sinedon.cfg on processing host
Start date:
04/16/2012
Due date:
% Done:
0%
Estimated time:
Description
SubmitAppionJob() in processing.inc used to have a check for sinedon.cfg:
// check if database is configured on processing host $cmd = "/opt/myamisnap/bin/appion; python -c 'import sinedon; print sinedon.getConfig(\"leginondata\")'"; $dbcheck = exec_over_ssh($processhost, $user, $pass, $cmd, True); if ($dbcheck === false){ //Return a more accurate error message $errMsg = "Could not connect to $processhost: "; $errMsg .= pconnError(); return $errMsg; } if (trim($dbcheck)=='') return "sinedon is not configured for leginondata, check your sinedon.cfg file"; if($expId != 000){ $cmd = "/opt/myamisnap/bin/appion; python -c 'import sinedon; print sinedon.getConfig(\"projectdata\")'"; $dbcheck = exec_over_ssh($processhost,$user,$pass,$cmd,True); if (trim($dbcheck) == '') return "sinedon is not configured for projectdata, check your sinedon.cfg file"; }
This will no longer work with an installation that uses the appion wrapper (ex. /opt/myamisnap/bin/appion) because the paths are not correct when trying to import sinedon.
To get around this, we need to create a script in appion bin that we can call with the wrapper that will let us know if the sinedon cfg file is correct.
No data to display
Actions