System freezes after executing facter command

[Montserrat Seisdedos]

    Hello,

    We have a problem with certain kind of machines from our farm (+300) Sometime when running "facter" the machine freezes, we lose access to it and logging through IPMI doesn't show anything in the console, the only thing we can do is a cold reboot. Then if we run facter again, nothing happens. If we run puppet several days after it could be another crash or not, it is random. This program uses dmidecode and others system tools to retrieve system information.
It only happens in machines with 2.6.24-28-server kernel, older kernels are ok.

    Soft Version:
    S.O: ubuntu 8.04
    kernel: 2.6.24-28-server2.6.24-28-server
    facter 1.5.4-1ubuntu1
    puppet 0.25.1-2

Hard Version:
Manufacturer: Supermicro
Model: X8SIE

I managed to get some traces executing with "strace" that I could paste if you consider so.

Someone has experienced something like that?

[Montserrat Seisdedos (mseisdedos)]

I will attach SysRq+t report when reproducing the problem

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

If your machine is freezing completely on some kernels and not others, this is very unlikely to be a bug in puppet or facter and much more likely to be a bug in the kernel, so I'm reassigning this bug to the kernel.

Note that 2.6.24-28 is not the current kernel for 8.04, and I assume it would help the kernel bug triagers if you can test the latest 8.04 kernel as well as report the exact version number of a previous known good one. I think they'll want the vanilla upstream kernel tested too. If this turns out to be a regression, then a bisection would help: https://wiki.ubuntu.com/Kernel/KernelBisection

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1084489

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Montserrat Seisdedos (mseisdedos)]

I didn't find apport-collect for Hardy, does it exist? where can I get it?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc7-raring/

[Montserrat Seisdedos (mseisdedos)]

Tested vmlinuz-3.7.0-030700rc7-generic.
Unable to mount root fs

[penalvch (penalvch)]

Montserrat Seisdedos, thank you for reporting this and helping make Ubuntu better. Hardy Server reached EOL on May 9, 2013.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Montserrat Seisdedos (mseisdedos)]

Hello Christopher,
We found out that virtual.rb (in facter package) in combination with out environment was causing the problem.
Due to the fact that this facter is not being used in ours recipes we just dropped it out.
Thanks for your help

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]