All
I have no idea why the LSD run failed last night, the log ends abruptly, the
gumpy.lock still exists. I have to wonder if it was killed, or something,
'cos normally we'd see any crash.
INFO:gump:Perform task [preprocess]
WARN:gump:Command failed. [timeout 60 env ]. ExitCode: 127
ERROR:gump:Failed to detect [timeout]
WARN:gump:Command failed. [ruper -version ]. ExitCode: 127
ERROR:gump:Failed to detect [ruper]
WARN:gump:Workspace version [0.3] below preferred [0.4]
INFO:gump:Perform task [loadStatistics]
INFO:gump:Perform task [update]
[More expected here...]
BTW: The gumpy.lock has the PID of the Gump process. If the lock exists yet
the PID do not, ought we try to be clever and ignore it? Thoughts?
regards
Adam
--
Experience the Unwired Enterprise:
http://www.sybase.com/unwiredenterprise
Try Sybase: http://www.try.sybase.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
