I had something weird happen with my gnubatch installation today, all of the jobs disappeared from the gbch-q display and stopped running. If I look in /usr/local/var/gnubatch the SPXXXXXXXX SOXXXXXXXX and ERXXXXXXXX files are still there. Is there any way to get the system to recognize these jobs again without having to resubmit them? Any ideas as to what could have triggered this problem? I'm running gnubatch 1.2 on CentOS 5.5, x86_64, and I've been running gnubatch for a few months now without having a problem like this.
The last thing that I'm aware of that was being done with gnubatch was that someone had just attempted to submit a job with the following command: gbch-r
-r minutes:20 -A- -a --userName\ swg -a --userPass\ xxxxxxxx -a
--textMap\ /usr/local/etc/swg_10.0_text_map.xml.gz -a --dailySize\
10000000 -a --genUsers True -a 192.168.46.98 192.168.46.99 -h Summary\
Daily\ Performance /usr/local/bin/genswg.py
The person who was attempting to submit this job got a few syntax errors when they issued this command, and right after that we noticed that the gnubatch scheduler had no jobs queued.