|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I was able to fix my problem, after spending many hours looking for a way to increase the log level of jenkins. In my case the cause was that the slave setup script was failing, that's added by an optional which runs some commands before starting the slave.jar Still, it seems that jenkins fails ugly when this happens.
Another cause was that the slave was not able to run because the build directory was not writable (after swiching from using root to using a different account, obviously the existing files were owned by root). Still, same ugly behaviour and nothing useful in the console.
Also, I still have the same problem regarding the clock, which is in sync but jenkins is reporting even 10 days behind on one of the slaves.