[Bug 1699618] [NEW] jetty hangs on startup under latest 3.13.0-121-generic kernel

2017-06-21 Thread Wilb
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 serv

[Bug 1699608] Re: qmail smtp server no longer starts up using latest kernel

2017-06-21 Thread Wilb
*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:/

[Bug 1699608] Re: qmail smtp server no longer starts up using latest kernel

2017-06-21 Thread Wilb
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 * qmailc

[Bug 1699608] [NEW] qmail smtp server no longer starts up using latest kernel

2017-06-21 Thread Wilb
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 "

[Bug 75135] Re: installation fails due to tty error

2007-04-20 Thread Wilb
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, w

[Bug 75681] Re: boot-time race condition initializing md

2007-04-03 Thread Wilb
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 o

[Bug 83231] Re: linux software RAID not working after herd 3 installation..

2007-04-03 Thread Wilb
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 f