It would be nice if error messages in the faistate would be reported in gosa_query_job_db. Combined with the GOsa patch from issue #35 this would be a very useful feature. It's also necessary to notice when an install job has failed. I'm not sure if the red screen of death situation starts a gosa-si-client. If it does, here_i_am would be a natural place to integrate this (compare issue #34 and issue #11 ). If it doesn't, another good place to integrate this check would be gosa_query_jobdb. A 1 minute cache should be used rather than doing the LDAP scan on each call to gosa_query_jobdb. Also the scan should be asynchronous rather than delaying the gosa_query_jobdb.
From matthias...@gmail.com on March 15, 2013 21:25:55
It would be nice if error messages in the faistate would be reported in gosa_query_job_db. Combined with the GOsa patch from issue
#35this would be a very useful feature. It's also necessary to notice when an install job has failed. I'm not sure if the red screen of death situation starts a gosa-si-client. If it does, here_i_am would be a natural place to integrate this (compare issue#34and issue#11). If it doesn't, another good place to integrate this check would be gosa_query_jobdb. A 1 minute cache should be used rather than doing the LDAP scan on each call to gosa_query_jobdb. Also the scan should be asynchronous rather than delaying the gosa_query_jobdb.Original issue: http://code.google.com/p/go-susi/issues/detail?id=88