-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows 7 SP1 x64 master
Windows 7 SP1 x64 slave
connection over JNLP agent
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
- is duplicated by
-
-
- Resolved
-
[JENKINS-15315] Slave polling hungup
Alexey Larsky
created issue -
| Assignee | New: Rob Petti [ rpetti ] |
Alexey Larsky
made changes -
| Attachment | New: Thread dump [Jenkins] (2012-09-28 17-35-47).htm [ 22497 ] |
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...
Alexey Larsky
added a comment - - edited 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... 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.
Alexey Larsky
added a comment - 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.
Alexey Larsky
added a comment - 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. 
Jesper Hansen
added a comment - 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)
Jesper Hansen
added a comment - 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) | Assignee | Original: Rob Petti [ rpetti ] |
I again get hungup sitiation on slave. P4 versions - lastest 2012.2.
Attaching new threaddump.
Alexey Larsky
added a comment - - edited I again get hungup sitiation on slave. P4 versions - lastest 2012.2.
Attaching new threaddump.
Can you provide a threaddump when the hang occurs?
http://jenkinsurl/threadDump