Public bug reported: I'm afraid I don't have a huge amount of information to share on this one yet, but its another issue I've seen since applying this weeks kernel update.
I have a Ubuntu 14.04 host running Solr within Jetty, but this hangs on startup when running the latest kernel: $ sudo service jetty start * Starting Jetty servlet engine. jetty * /var/run/jetty.pid exists, but jetty was not running. Ignoring /var/run/jetty.pid /etc/init.d/jetty: 274: /etc/init.d/jetty: /usr/sbin/rotatelogs: not found * Jetty servlet engine started, reachable on http://hostname-goes-here:8983/. jetty ...fail! $ ps -ef | grep [j]ava root 3389 1 0 23:25 ? 00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml $ sudo service jetty stop * Stopping Jetty servlet engine (was reachable on http://tenshi-prod-ckan:8983/). jetty * (not running). $ ps -ef | grep [j]ava root 3389 1 0 23:25 ? 00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml In this instance I can only terminate it with a "sudo kill -9 3389" which causes "Service killed by signal 11" to be logged to /var/log/jetty/out.log This is when booting the 3.13.0-121-generic - booting back into 3.13.0-119-generic sees the service start fine. The host is running OpenJDK 7u131-2.6.9-0ubuntu0.14.04.2. ** Affects: jetty (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1699618 Title: jetty hangs on startup under latest 3.13.0-121-generic kernel Status in jetty package in Ubuntu: New Bug description: I'm afraid I don't have a huge amount of information to share on this one yet, but its another issue I've seen since applying this weeks kernel update. I have a Ubuntu 14.04 host running Solr within Jetty, but this hangs on startup when running the latest kernel: $ sudo service jetty start * Starting Jetty servlet engine. jetty * /var/run/jetty.pid exists, but jetty was not running. Ignoring /var/run/jetty.pid /etc/init.d/jetty: 274: /etc/init.d/jetty: /usr/sbin/rotatelogs: not found * Jetty servlet engine started, reachable on http://hostname-goes-here:8983/. jetty ...fail! $ ps -ef | grep [j]ava root 3389 1 0 23:25 ? 00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml $ sudo service jetty stop * Stopping Jetty servlet engine (was reachable on http://tenshi-prod-ckan:8983/). jetty * (not running). $ ps -ef | grep [j]ava root 3389 1 0 23:25 ? 00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml In this instance I can only terminate it with a "sudo kill -9 3389" which causes "Service killed by signal 11" to be logged to /var/log/jetty/out.log This is when booting the 3.13.0-121-generic - booting back into 3.13.0-119-generic sees the service start fine. The host is running OpenJDK 7u131-2.6.9-0ubuntu0.14.04.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jetty/+bug/1699618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
