[
https://issues.jenkins-ci.org/browse/JENKINS-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159332#comment-159332
]
Dietrich Schulten commented on JENKINS-6964:
--------------------------------------------
In my setup, setting -Dhost.name did help if the slave is started manually from
Hudson.
But strangely, when starting the entire Hudson, I always have to kill the
slave.jar process on the slave console and then I must restart the slave from
Hudson. Otherwise, the selenium rc refuses to start with the above message.
> Selenium plugin can't start RCs on slaves.
> ------------------------------------------
>
> Key: JENKINS-6964
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6964
> Project: Jenkins
> Issue Type: Bug
> Components: selenium
> Affects Versions: current
> Environment: Windows XP
> Reporter: dpenny52
> Assignee: Kohsuke Kawaguchi
>
> Hudson can't start remote controls on slaves, but it does start them on the
> master node. The error message is "Unable to determine the host name.
> Skipping Selenium execution."
> Setting the host.name system property for the slave did not solve the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
