Dear Ferran, > One very curious behaviour is that the first task after midnight > switches to SCHEDULED state but doesn't run. On the test server it > happens to Traces, and on the production it happens to DDD. No matter > how many hours I spend (and I have spent many!) finding why and how, the > mystery continues.
It might be related to a bug we have spot in the handling of dates, but to stay in scheduled was indeed never seen. In general it means that the task itself fails to run for some reason... > Anyhow, I needed a mechanism to automate my daily manual task to put > bibsched into manual mode, know which is the task in SCHEDULED state, > run it and put bibsched back to automatic mode. > > I have been patching bibsched to allow, at least, those basic scripting > capabilities. I don't know how many more tasks do I need (acKnowledge > errors, maybe?). I'm unsure on the names I have choosen. > > As I feel that it may be useful to somebody else, so I submit it for > your consideration. Indeed it could be useful to manipulate tasks in the queue programmatically... so thanks for your idea! The only thing is that we are about to integrate into main Invenio e refactored bibsched which is the results of several improvements we have introduced for the INSPIRE usecase... We can see how easy it is to apply your suggested CLI improvements. Regarding the scheduled bug it is going to be hopefully fixed in the upcoming changes. Note that the new bibsched (which is going to be available in master), should be easily back-portable to maint-1.1. You can have a peek at it here: <http://invenio-software.org/repo/personal/invenio-adeiana/log/?h=bibsched-refactoring> Cheers! Sam -- Samuele Kaplun Invenio Developer ** <http://invenio-software.org/> INSPIRE Service Manager ** <http://inspirehep.net/>
