[Bug 1699618] [NEW] jetty hangs on startup under latest 3.13.0-121-generic kernel
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699618 Title: jetty hangs on startup under latest 3.13.0-121-generic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jetty/+bug/1699618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699608] Re: qmail smtp server no longer starts up using latest kernel
*sigh* - even the second attempt I missed a zero in that sed command. I'll take myself to bed soon. It should have read: * sed -i s/700/900/ /etc/service/qmail-smtpd/run -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699608 Title: qmail smtp server no longer starts up using latest kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qmail/+bug/1699608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699608] Re: qmail smtp server no longer starts up using latest kernel
Apologies, I missed a couple of lines from my steps to reproduce when copy & pasting it over from my terminal history. It should read something more like: * Installed Ubuntu 16.04 on Digital ocean * edit /etc/hosts to ensure a FQDN is present * apt-get update * apt-get install qmail * qmailctl stat & tail -1 /var/log/qmail/smtp/current "/etc/service/qmail-smtpd: down 1 seconds, normally up, want up" "tcpserver: fatal: unable to figure out port number for smtp" * sed -i s/700/90/ /etc/service/qmail-smtpd/run * tail -1 /var/log/qmail/smtp/current "status: local 0/10 remote 0/20" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699608 Title: qmail smtp server no longer starts up using latest kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qmail/+bug/1699608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699608] [NEW] qmail smtp server no longer starts up using latest kernel
Public bug reported: Following on from some patching I've done this week after the release of the latest kernels, I observed that qmail-smtpd no longer starts due to the following error: "tcpserver: fatal: unable to figure out port number for smtp" You will see this is logged repeatedly out to "/var/log/qmail/smtpd/current" I've just spent a little time tracing it and have concluded that the softlimit defined in "/etc/service/qmail-smtpd/run" is no longer high enough which presumably gets in the way of it loading /etc/services into memory. Changing the softlimit from 700 to 900 allows the service to start up as before, as does rolling back to the previous kernel. Presumably the stack clash patching has caused this change in memory requirements for the process and hence the softlimit increase. I've just provisioned a clean Ubuntu 16.04 host to confirm that it's not any existing configuration: * Installed Ubuntu 16.04 on Digital ocean * edit /etc/hosts to ensure a FQDN is present * apt-get update * apt-get install qmail * qmailctl stat "/etc/service/qmail-smtpd: down 1 seconds, normally up, want up" * tail /var/log/qmail/current "@4000594ae38c2c31ed3c status: local 0/10 remote 0/20" I've observed the same issue on hosts running Ubuntu 16.04, 14.04 and Debian 8 for what it's worth. ** Affects: qmail (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699608 Title: qmail smtp server no longer starts up using latest kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qmail/+bug/1699608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75135] Re: installation fails due to tty error
Also having exactly the same problems with Feisty Final - it crashes out to a busybox prompt, erroring that it can't find a plethora of paths. Looking through the logs, it fails to mount /root/cdrom and gets in a pickle from then onwards. I've tried booting with break=mount and mounting manually, which I can do, but I think its already missed running some important scripts by then as ctrl d doesn't fire it off again. Definitely not a media problem as it works fine on another machine -- installation fails due to tty error https://bugs.launchpad.net/bugs/75135 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
Exactly same problem for me here too - no LVM in sight, just a md0 and md1 as /boot and / respectively, fixed by using break=mount and mounting manually. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/75681 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83231] Re: linux software RAID not working after herd 3 installation..
Same thing here, just done an install of Feisty server beta and done an apt-get update && apt-get dist-upgrade, came up with the same problems as before - have to manual mount the arrays in the busybox shell or use the udevsettle temporary workaround. Just a basic install with a small RAID1 array for /boot and a 7gb one for / - Silicon Image SATA controller on an Asus A7N8X (althoguh not configured for any on board RAID, purely mdadm software raid) -- linux software RAID not working after herd 3 installation.. https://bugs.launchpad.net/bugs/83231 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
