It just worked after the upgrade. I didn't do any cleanup before the
upgrade to restore the system to a pristine state between the initial
installation of crashdump and the upgrade to 10.04, but I don't think I
really did anything but install the package.
--
You received this bug notification
It's still a bug. The point is that I can NOT upgrade the machines to a
development release, they're commercial production machines that need to
be as stable as possible. I would have upgraded to 10.04 but couldn't
risk it in the time frame I had before needing to lock the system down
for a
Public bug reported:
This bug is mentioned in several places and was recently fixed in 10.04
(see #615548
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/615548). Links:
http://lkml.org/lkml/2010/1/5/179
http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591548
--
tcp_xmit_retransmit_queue panic in 2.6.31 in 9.10 server kernel
https://bugs.launchpad.net/bugs/667056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Verified it's fixed for me too using the proposed update (apache2 SSL,
calling PHP curl in turn to an SSL site).
--
Segfault on OpenSSL engine initialisation when AES-NI is enabled
https://bugs.launchpad.net/bugs/590639
You received this bug notification because you are a member of Ubuntu
Bugs,
Update: Upgrading to 10.04 seems to have fixed crash dumps, in that I
now get a core file and a .crash file gets made. Still working on the
actual crash but now I have something to work with.
--
linux-crashdump fails to record crash; reports memory not reserved
Thanks Miroslav. That fixed it for me as well. I can't believe this
hasn't been fixed.
My test environment was 32-bit so I missed this initially and then spent
way too long trying to figure it out.
--
apache exit with signal Segmentation fault (11) on access to https:// if
php5-curl enabled
Thanks Miroslav. That fixed it for me as well. I can't believe this
hasn't been fixed.
My test environment was 32-bit so I missed this initially and then spent
way too long trying to figure it out.
--
apache exit with signal Segmentation fault (11) on access to https:// if
php5-curl enabled
Public bug reported:
Having random crashes and reboots on previously stable machines. To
troubleshoot, tried installing linux-crashdump but no dumps are
appearing. Occasionally, there is an error message in
/var/crash/vmcore.log, but not consistently:
open_dump_memory: Can't open the dump
** Attachment added: Output from ubuntu-bug -p linux-crashdump
http://launchpadlibrarian.net/51083259/apport.linux-crashdump.66pQno.apport
--
linux-crashdump no output after crash, error in vmcore.log
https://bugs.launchpad.net/bugs/599601
You received this bug notification because you are a
I have 10 machines on dual core-i7 (amd64) with 16G RAM running 9.10.
They're randomly rebooting after months of stability with absolutely no
messages in the logs so I've assumed I've got a kernel panic and
installed linux-crashdump. I get no output in /var/crash, other than
once I had a log file
Both the VM and native machines are one XFS filesystem (/).
--
linux-crashdump fails to record crash; reports memory not reserved
https://bugs.launchpad.net/bugs/321970
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Found a better workaround: Install python2.4 and edit the /usr/sbin
/nagios-statd shebang to use it (#!/usr/bin/python2.4).
This bug is even worse in 9.10. Now the process locks up one core at
100% CPU when it stops responding.
Suggested fix: Ship the nagios-statd-server package with a
Looks like this might actually be a python problem or it needs to be
updated for newer versions of python. It happens with the vanilla source
version of statd from twoevils.org going all the way back to the good
version in Debian stable (3.09).
--
When using --bindto and/or --allowedhosts
I'm probably going to use xinetd as well but it bugs me because it's yet
another thing I have to watch and keep secure on a couple of machines
that are really minimized and locked down..
--
When using --bindto and/or --allowedhosts nagios-statd stops accepting
connections after a while
Public bug reported:
Ubuntu 9.04 server:
nagios-statd-server:
Installed: 3.12-1
Candidate: 3.12-1
Version table:
*** 3.12-1 0
500 http://us.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
This is happening on 3 machines now. There are 7 others with
In my case the repro was simply:
1) Install Ubuntu 7.10 from CD.
2) Log in to desktop GUI and apply available updates from notification icon.
3) Reboot and never get an interactive desktop upon GDM login while nautilus
log thrashes (text console logins work fine).
My is/was slightly different
This doesn't appear to be fixed. I just installed 7.10 today. I had a
working desktop for about 10 minutes and then installed the available
updates. Now, after rebooting, when I log in I get a blank desktop for
about 5 seconds and then the screen goes completely black except for the
mouse (cursor
18 matches
Mail list logo
