jenkins on debian 8 jessie

48 views
Skip to first unread message

Nicholas Geovanis

unread,
Mar 5, 2016, 10:00:23 PM3/5/16
to Jenkins Users
Hi - New jenkins user trying to start jenkins on Debian 8 jessie. I receive the following messages at failed startup, was wondering if someone could point me in the right direction: (many thanks)
nick@nickdell:~/src$ java -jar /usr/share/jenkins/jenkins.war
Running from: /usr/share/jenkins/jenkins.war
webroot: $user.home/.jenkins
Mar 05, 2016 8:42:05 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Mar 05, 2016 8:42:05 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-winstone-2.9
Mar 05, 2016 8:42:05 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Can't reuse /tmp/jetty-0.0.0.0-8080-war--any-, using /tmp/jetty-0.0.0.0-8080-war--any-_7587508702438688318
Mar 05, 2016 8:42:07 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet
Jenkins home directory: /home/nick/.jenkins found at: $user.home/.jenkins
Mar 05, 2016 8:42:08 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: FAILED SelectChann...@0.0.0.0:8080: java.net.BindException: Address already in use
java.net.BindException: Address already in use
    at sun.nio.ch.Net.bind0(Native Method)
    at sun.nio.ch.Net.bind(Net.java:463)
    at sun.nio.ch.Net.bind(Net.java:455)

Vivekanand S V

unread,
Mar 5, 2016, 11:44:48 PM3/5/16
to Jenkins Users

Looks like something else is already running in port 8080. You need to stop that before starting this.


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f3783c5d-11c7-4a4f-ab26-95e96f9f8be0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Nicholas Geovanis

unread,
Mar 8, 2016, 11:21:22 AM3/8/16
to Jenkins Users
Indeed. It turned out that previous invocations of jenkins were running, reparented to PID 1. Killed them and jenkins started-up fine.
Thanks....Nick Geo
Reply all
Reply to author
Forward
0 new messages