Re: Slave hang

[jerome]

I called victory way too fast, still can happen, just not as often. The 
fact that the slave can flood the master is a bit annoying, it should wait 
and continue later. Right now the behavior is if this happen, the 
slave/master hang (web gui is still accessible, but impossible to cancel 
the jobs) and I need to restart the Jenkins daemon everyday :-(

Maybe it's impossible to have the jobs folder under a network mount where 
the network can sometime be under heavy usage. This was solving the split 
between the master config and the jobs config/results for backup purpose. 
The master config change at slow pace and we manually backup the whole 
machine when doing update keeping the 2 last in case of problems to quickly 
revert. Jobs on the other hand need to be backup every day in incremental 
way.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/45d23afd-7861-452b-b5ec-dca615d09430%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slave hang

[jerome]

Finally find the problem. Seem like my mount drive under Linux was under 
heavy usage (the polling was occurring at the same time the IT was doing 
big backup) and therefor the Master Disk IO could not follow to write the 
jobs and the RAM vm.dirty_ was flooded. Making the build to hang.

So I changed the polling cron to avoid the conflict, but still a little 
weird that it doesn't suspend the slave until it can recover. So if the 
salve can flood the master disk IO the build hang and never recover.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3d16e7e7-3dee-4e6c-b71a-e1ef55df31fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slave hang

[jerome]

More info, it seem like if I use the Windows slave computer and the poll 
occur, it work just fine. So when the user is lock (sleep is disabled, only 
the screen is allowed to go to sleep on this computer and maximum 
performance profile is used) and a poll on the master request the slave to 
do some work, it seem like it can checkout, build and then hang either at 
the end of the build which is completed.

Windows Batch Script - (13 hr in self) 


So the batch command is done and the command have returned, but nothing 
happen after



*msbuild compilation here..00:14:37.575* 
*00:14:37.576* Build succeeded.
*00:14:37.577* 0 Warning(s)
*00:14:37.578* 0 Error(s)
*00:14:37.579* 
*00:14:37.579* Time Elapsed 00:14:09.54


I'm guessing it has something to do with the desktop access and the user 
being lock into Windows 10. If anybody have an idea why a batch script hang 
under those conditions when returning, I'm a bit lost here.

bat returnStatus: false, script: "\"${bcad.msbuild_current}\" 
${bcad.msbuild_solution_name} ${bcad.msbuild_default_arg} /t:Build"

I use the *returnStatus: False* if that may give any idea (so the build 
doesn't get fail and the pipeline stop by a warning).

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/58ee5b93-bf81-431e-9281-3e6d60e1e87e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slave hang

[jerome]

It hang again today, seem like the MSBuild Warning plugin is the pipeline 
step that hang under Windows 10 if the user is in lock (not log off) state. 
When user that run the slave client is active on the machine it work fine.

step([$class: 'WarningsPublisher', canRunOnFailed: true, consoleParsers: [[
parserName: 'MSBuild']]])

This is a problems if on top of having the user log in I need the session 
to remain unlock.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4e3a0e2f-ab4c-460b-aa5c-8a6f5095d09c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.