Quantcast

[JIRA] (JENKINS-15698) Perforce can't get hostname for slaves

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15698) Perforce can't get hostname for slaves

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Attachments: P4_settings.png
Components: perforce
Created: 02/Nov/12 6:31 AM
Description:

I have lots of Perforce warnings in log.
Perforce settings are atteched.

WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims
Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName
WARNING: Could not get hostname for slave rusbuilder-ims

Environment: Jenkins ver. 1.488
Perforce 1.3.17, ws isn't managed by perforce plugin
Project: Jenkins
Labels: slave plugin windows scm warnings
Priority: Minor Minor
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15698) Perforce can't get hostname for slaves

JIRA noreply@jenkins-ci.org
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15698) Perforce can't get hostname for slaves

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Rob Petti commented on Bug JENKINS-15698

This is a problem with core, unfortunately. Getting the hostname of a machine using java is actually quite difficult, so it doesn't work 100% of the time. Check that the hostname is resolvable in DNS, and that the slave isn't running more than one networking interface. Apart from that, there's really nothing else that can be done.

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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15698) Perforce can't get hostname for slaves

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Hostname is resolveble, network interface only one. Added to hosts self address.
Warning still present.

PS. OS Windows 7 Pro x64 SP1 on master and slave.

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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-15698) Perforce can't get hostname for slaves

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Alexey Larsky edited a comment on Bug JENKINS-15698

Hostname is resolvable, network interface is only one. I also added to etc\hosts self address.
Warning still present.

PS. OS Windows 7 Pro x64 SP1 on master and slave.

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
Loading...