Bug #33429
closed
Added by Anonymous almost 13 years ago.
Updated about 6 years ago.
Description
When I run the Scheduler with the scheduler_http (a useful extension for websites which are not able to run shell) I always get the return var 127.
I don't know how to handle this.
Is it the error code of the scheduler script or of the operating system?
And how can I fix it?
Could you please ask the author of scheduler_http extension first? I don't know, why such a return value is passed through. Usually single scheduler tasks return boolean.
I've asked the author of the mentioned extension first an he wrote:
return_var's are a bit arbitrary, because the value depends on what the developer of the script returns (e.g. in php "exit(127);" will result in an error code of "127"). If the value comes from the operating system, the codes depend on the operating system used - e.g. for linux: http://tldp.org/LDP/abs/html/exitcodes.html#EXITCODESREF
So it seems to be a problem with the scheduler.
Most likely you have another error in your configuration.
Can you please debug the scheduler_http extension (it has such an option) and tell what the output it.
Anyway, on 6.0 it always returns 0 (zero) or 99 (exception) even if an error happened.
- Status changed from New to Resolved
As far as I understand, this is not an issue in the scheduler extension.
- Category set to scheduler
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by