<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Sorry this isn't on the box-admins list. I'm not currently on that list and this seems pressing. <div><br></div><div>Perhaps anybody using <a href="http://build.squeak.org">build.squeak.org</a> could download The Definitive Guide as a reference. That's pretty much where this all started. It's free.</div><div><br></div><div><a href="http://www.wakaleo.com/books/jenkins-the-definitive-guide">http://www.wakaleo.com/books/jenkins-the-definitive-guide</a></div><div><br></div><div>I tried restarting Jenkins with </div><div><br></div><div>/usr/init.d/jenkins [stop|restart|start}</div><div><br></div><div>and </div><div><br></div><div>/usr/sbin/service jenkins [stop|restart|start}</div><div><br></div><div>It complains that there is already a service on port 8080. So I went in with </div><div><br></div><div>ps aux | grep jenkins </div><div><br></div><div>to manually kill the last processes. They won't die. There are two. </div><div><br></div><div>I had a thought this was because Apache was running and looked like port 8080 to Jenkins. I stopped it. Tried again and that had no effect. I restarted it.</div><div><br></div><div>I have some notions that what Jenkins wants is to be restarted with something Java-esque like:</div><div><br></div><div>
<div class="page" title="Page 86">
<div class="layoutArea">
<div class="column"><p><span style="background-color: rgb(227, 228, 250);"><font face="Times">java -jar jenkins.war --httpPort=8081 --ajp13Port=8010 --prefix=jenkins</font><br>
</span></p><p><br></p><p>Though I'm not sure that makes any difference. (Note the "ajp" reference above and mentioned on page p.54 of Jenkins: The Definitive Guide, section 3.9. We're running Jenkins with mod_proxy_ajp or something like that. )</p><div><br></div><div>I Googled the problem with the error message: </div><div><br></div><div>"Restarting Jenkins Continuous Integration Server: jenkinsThe selected http port (8080) seems to be in use by another program Please select another port to use for jenkins failed!"</div><div><br></div><div>As far as I can tell that is saying Jenkins sees an existing process on port 8080 and will not start, to wit, it is seeing itself and will not start a process of itself. How can these processes be so resilient? </div><div><br></div><div>It may be possible that our version of Jenkins needs to be updated and the problem will go away. It may be that some squeak images need to be killed before the final Jenkins process will die or allow itself to be reloaded or something. </div><div><br></div><p>I'm out of ideas, but if somebody reads this over, perhaps they can see something useful to do here. </p><div><br></div><div>Chris </div></div></div></div></div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>