[JIRA] (JENKINS-15315) Slave polling hungup

Alexey Larsky created JENKINS-15315

Slave polling hungup

Issue Type:	Bug
Affects Versions:	current
Assignee:	Unassigned
Components:	perforce
Created:	26/Sep/12 9:23 AM
Description:	Project on slave builders with perforce SCM are hanging after several hours. Perforces workspaces configered as permanent with only one checkbox "Don't update client workspace". Main log: Sep 26, 2012 1:16:28 PM hudson.plugins.perforce.PerforceSCM getEffectiveClientName WARNING: Could not get hostname for slave <SlaveName> Polling log: Started on Sep 26, 2012 1:19:27 PM Looking for changes... Using node: Builder Using remote perforce client: <ws_name> terminate here
Environment:	Windows 7 SP1 x64 master Windows 7 SP1 x64 slave connection over JNLP agent
Project:	Jenkins
Priority:	Major
Reporter:	Alexey Larsky

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

Rob Petti assigned JENKINS-15315 to Rob Petti

Slave polling hungup

Change By:	Rob Petti (27/Sep/12 2:23 AM)
Assignee:	Rob Petti

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

Rob Petti commented on JENKINS-15315

Slave polling hungup

Can you provide a threaddump when the hang occurs? http://jenkinsurl/threadDump

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

Alexey Larsky updated JENKINS-15315

Slave polling hungup

Change By:	Alexey Larsky (28/Sep/12 1:42 PM)
Attachment:	Thread dump [Jenkins] (2012-09-28 17-35-47).htm

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

Alexey Larsky commented on JENKINS-15315

Slave polling hungup

Treaddump has attached. Perforce Polling Log Started on Sep 27, 2012 9:31:26 PM Looking for changes... Using node: Builder Using remote perforce client: Alexey.Larsky_NM_v01_builder ...nothing here...

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

 

Alexey Larsky edited a comment on JENKINS-15315

Slave polling hungup

Treaddump is attached. Perforce Polling Log Started on Sep 27, 2012 9:31:26 PM Looking for changes... Using node: Builder Using remote perforce client: Alexey.Larsky_NM_v01_builder ...nothing here...

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

Rob Petti commented on JENKINS-15315

Slave polling hungup

It looks like your p4 client executable is hanging for some reason. Double check all your settings, and make sure you are using a client version that matches your server version. Also make sure that you aren't using any special characters in your workspace name.

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

Alexey Larsky commented on JENKINS-15315

Slave polling hungup

Thanks Rob. I have updated p4 to P4/NTX64/2012.1/490371 (2012/07/02) from 2010.1 on server and client. In workspace's names using only dots and underscores. I will check issue on updated version.

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

Jesper Hansen commented on JENKINS-15315

Slave polling hungup

I have also experienced this problem a few times. The log only contains: Perforce Polling Log Started on Oct 4, 2012 12:18:23 PM Looking for changes... Using node: cphwrk0249 Using remote perforce client: jenkins_bsp-trunk--379981060 I can't find any p4.exe processes running on cphwrk0249. Two of the times I experienced this was on days where I know that the network connection on cphwrk0249 had been disconnected for several minutes during the day. perforce client is version P4/NTX64/2012.1/442152 (2012/04/06) server is P4D/LINUX26X86/2012.1/518826 (2012/08/30)

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

Rob Petti assigned JENKINS-15315 to Unassigned

Slave polling hungup

Change By:	Rob Petti (10/Oct/12 9:11 PM)
Assignee:	Rob Petti

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

Alexey Larsky commented on JENKINS-15315

Slave polling hungup

I again get hungup sitiation on slave. P4 versions - last. Attaching new threaddump.

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

 

Alexey Larsky edited a comment on JENKINS-15315

Slave polling hungup

Threaddump for p4 polling hungup on slaves.

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

Alexey Larsky updated JENKINS-15315

Slave polling hungup

Threaddump for p4 polling hungup on slaves. That intresting - now hungup polls on master too.
Change By:	Alexey Larsky (12/Oct/12 10:09 AM)
Attachment:	Thread dump [Jenkins] (2012-10-12 14-00-59).htm

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

 

Alexey Larsky edited a comment on JENKINS-15315

Slave polling hungup

Uploading "Thread dump [Jenkins] (2012-10-12 14-00-59).htm" Threaddump for p4 polling hungup on slaves.

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

 

Alexey Larsky edited a comment on JENKINS-15315

Slave polling hungup

I again get hungup sitiation on slave. P4 versions - lastest 2012.2. Attaching new threaddump.

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

Rob Petti commented on JENKINS-15315

Slave polling hungup

It's hanging in IO, which to me suggests a network problem. I'm not sure what else I can do aside from adding some kind of timeout. :/

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

Alexey Larsky commented on JENKINS-15315

Slave polling hungup

But network problem - is ordinary suation between two computers (master and slave). And this situation mustn't influence to future builds. In other words task should restoring after network error. Thank you

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

 

Alexey Larsky edited a comment on JENKINS-15315

Slave polling hungup

But network problem - is ordinary situation between two computers (master and slave(s)). And this situation mustn't influence to future builds. In other words task should be able to restore after network error. Thank you

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

 

Alexey Larsky edited a comment on JENKINS-15315

Slave polling hungup

But network problem - is ordinary situation between two computers (master and slave(s)). And this situation mustn't influence to future builds. In other words task should restoring after network error. Thank you

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

Rob Petti commented on JENKINS-15315

Slave polling hungup

Yeah, I agree, but the remoting API is supposed to take care of those details. If there is a connection issue, it should be failing outright instead of hanging.

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