It was a while ago, and I didn't have time to finish looking at this, but IIRC last I checked, the code in question seemed to make some assumptions about the way the system was partitioned --- I think it assumed everything was all in one big / partition. Is your VM partitioned that way, but your other machine partitioned with a separate /var partition, by any chance?
On 06/21/2010 08:58 PM, Rhomboid wrote: > 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 that said it failed attempting to save a crash. > The log file disappeared so I don't have the exact message. I also don't > have console access so I'm not sure if I'm getting an error about > reserved memory that's not in a log file. The machines are in a remote > facility. > > The wiki page (https://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe) says > 'In Karmic all that is needed is to install the "linux-crashdump" > package. After a reboot the system should be able to catch crash dumps > automatically and provide them to apport.'. This does not appear to be > true. The machines also have no direct internet access so apport does > not appear to work correctly, even with http_proxy set. > > I don't get any crash dumps when simulating/forcing a crash (echo c> > /proc/sysrq-trigger) either. > > However, I have a test VM with only 2GB of RAM and I do see dumps when I > force a crash. I'm wondering if the large memory (16GB) may have > something to do with this. The only other thing I have set differently > between the VM and the remote machines is kernel.panic=5 in sysctl. I > was thinking that may be forcing a reboot before the dump can complete? > I'm really not wanting to eliminate that setting though because I *need* > those machines to come back if they panic due to them being offsite. > > -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
