headers
Louis Bouchard | 3 Dec 2010 14:01
Picon
Favicon

Presentation of crashdc

Hello everyone

I just want to take  a few minutes of your time to let you know about
crashdc, a project that I have been working on for the last year.

It is a set of scripts that leverage kexec's kdump_post mechanism to
generate a text file called crash-data-{date}.txt containing some
specific 'crash' command output.

This allows kexec to automatically generate a high level text file that
can be sent to support engineers without going through the pain of
sending multi-gigabyte files over the Internet.

crashdc can also be triggered by an initscript upon reboot if sysadmins
prefer to avoid execution of crash commands in the kexec booted kernel
context, as it sometimes require a sensible increase in the
crashkernel's reserved memory.

It is currently working on RHEL5, SLES10 and SLES11 and I'm working on
RHEL6 enablement (x86 and x86_64).

You can find more details about it here :

http://cariblog.kamikamamak.com/2009/10/17/crashdc-the-architecture/

The project is hosted here :

http://crashdc.sourceforge.net

If some of you are insterested in more details, don't hesitate to let me
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stanislaw Gruszka | 3 Dec 2010 18:11
Picon
Favicon

Re: kdump broken on 2.6.37-rc4

On Fri, Dec 03, 2010 at 06:46:09PM +0300, Maxim Uvarov wrote:
> 2010/12/3 Stanislaw Gruszka <sgruszka@...>:
> > On my T-60 laptop, i686 system with 2.6.37-rc4 kernel,
> > "echo c > /proc/sysrq-trigger" just hung the system. Kdump
> > works on 2.6.36. Is this known issue? If not, what info
> > I should provide to solve it (I think the easiest way
> > to solve the problem would be bisect) ?
> >
> > Stanislaw
> >
> 
> I tested x86 QEMU yesterday with the latest git. It worked.
> Might be something target specific.., What does console print?

Here is the photo 
http://people.redhat.com/sgruszka/20101203_005.jpg

There are two BUGs, first "sleeping function called from invalid
context" and then "unable to handle null pointer dereference".

Stanislaw
Permalink | Reply | 64 comments |
headers
Louis Bouchard | 3 Dec 2010 17:14
Picon
Favicon

kdump_post : busybox returns "Applet not found"

Hello (again)

I did not think that I would come back to you so quickly, but I am having an issue with RHEL6 implementation of kexec-tools (apparently adapted for kexec-tools 2.0) while testing crashdc on RHEL6 (the initial release).

Everytime I trigger a crash with 'kdump_post' set to /var/crash/scripts/kdump_post.sh I get the following from busybox : kdump-post.sh: applet not found

Copying data        : [100%]
Saving core complete
kdump-post.sh: applet not found
dropping to initramfs shell
exiting this shell will reboot your system
For a while, I thought that my crashdc calling script was in cause, but I changed kdump_post.sh to one single "echo This is working" line and I still get the same thing :

# cat /var/crash/scripts/kdump-post.sh
echo "This is working"
/var/crash/scripts/kdump-post.sh
kdump-post.sh: applet not found
msh/ # /var/crash/scripts/kdump-post.sh
This is working
FYI, my crashdc scripts all work fine when I call them manually from the CLI.

I did not encounter this situation with SLES11, but from what I gather, it does not rely on  busybox.

Maybe someone could suggest ways to further investigate this issue. I'm available to test.

Kind regard,

...Louis

-- Louis Bouchard Linux Support Engineer Team lead, EMEA Linux Competency Center, Linux Advocate, HP HP Technology Services - Global Competency Center Hewlett-Packard Company louis.bouchard-VXdhtT5mjnY@public.gmane.org / Email Mon-Fri 9-17<WET>,<GMT+2> / Working Hours Mark Fay / Manager mark.fay-VXdhtT5mjnY@public.gmane.org / Manager's Email 
_______________________________________________
kexec mailing list
kexec@...
http://lists.infradead.org/mailman/listinfo/kexec
Permalink | Reply | 7 comments |
headers
Neil Horman | 5 Dec 2010 21:19
Picon
Favicon

Re: kdump_post : busybox returns "Applet not found"

On Fri, Dec 03, 2010 at 05:14:00PM +0100, Louis Bouchard wrote:
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
> 
> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
> </head>
> <body text="#000000" bgcolor="#ffffff">
> Hello (again)<br>
> <br>
> I did not think that I would come back to you so quickly, but I am
> having an issue with RHEL6 implementation of kexec-tools (apparently
> adapted for kexec-tools 2.0) while testing crashdc on RHEL6 (the
> initial release).<br>
> <br>
> Everytime I trigger a crash with 'kdump_post' set to
> /var/crash/scripts/kdump_post.sh I get the following from busybox :
> kdump-post.sh: applet not found<br>
> <br>
> <blockquote><tt>Copying data&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; : [100%]</tt><br>
>   <tt>Saving core complete</tt><br>
>   <tt>kdump-post.sh: applet not found</tt><br>
>   <tt>dropping to initramfs shell</tt><br>
>   <tt>exiting this shell will reboot your system</tt><br>
> </blockquote>
> For a while, I thought that my crashdc calling script was in cause, but
> I changed kdump_post.sh to one single "echo This is working" line and I
> still get the same thing :<br>
> <br>
> <blockquote><tt># cat /var/crash/scripts/kdump-post.sh</tt><br>
>   <tt>echo "This is working"</tt><br>
>   <tt>/var/crash/scripts/kdump-post.sh</tt><br>
>   <tt>kdump-post.sh: applet not found</tt><br>
>   <tt>msh/ # /var/crash/scripts/kdump-post.sh</tt><br>
>   <tt>This is working</tt><br>
> </blockquote>
I'm kind of suprised this is working at all.  I don't see a #!/bin/sh or
#!/bin/msh line at the top of the script.  How does the system know what
interpreter to use?

Neil
Permalink | Reply | 6 comments |
headers
Bernhard Walle | 5 Dec 2010 21:52
Picon

Re: kdump_post : busybox returns "Applet not found"

Am 05.12.10 21:19, schrieb Neil Horman:
> I'm kind of suprised this is working at all.  I don't see a #!/bin/sh or
> #!/bin/msh line at the top of the script.  How does the system know what
> interpreter to use?

/bin/sh is the default interpreter.

Regards,
Bernhard
Permalink | Reply | 5 comments |
headers
Louis Bouchard | 6 Dec 2010 11:59
Picon
Favicon

Re: kdump_post : busybox returns "Applet not found"

Hello,

On 05/12/2010 21:52, Bernhard Walle wrote:
> Am 05.12.10 21:19, schrieb Neil Horman:
>> I'm kind of suprised this is working at all.  I don't see a #!/bin/sh or
>> #!/bin/msh line at the top of the script.  How does the system know what
>> interpreter to use?
> 
> /bin/sh is the default interpreter.
> 
> 
> Regards,
> Bernhard
> 
> _______________________________________________
> kexec mailing list
> kexec@...
> http://lists.infradead.org/mailman/listinfo/kexec

While, as Bernhard said, /bin/sh is default so the test script does
work, the crashdc scripts that I'm testing do have the #!/bin/sh at the
beginning, with identical behavior.

Kind regards,

..Louis

--

-- 
Louis Bouchard
Linux Support Engineer
Team lead, EMEA Linux Competency Center,
Linux Advocate, HP

HP Technology Services - Global Competency Center
Hewlett-Packard Company

louis.bouchard@...     / Email
Mon-Fri 9-17<WET>,<GMT+2> / Working Hours
Mark Fay                  / Manager
mark.fay@...           / Manager's Email
Permalink | Reply | 3 comments |
headers
Neil Horman | 6 Dec 2010 13:03
Picon
Favicon

Re: kdump_post : busybox returns "Applet not found"

On Sun, Dec 05, 2010 at 09:52:27PM +0100, Bernhard Walle wrote:
> Am 05.12.10 21:19, schrieb Neil Horman:
> > I'm kind of suprised this is working at all.  I don't see a #!/bin/sh or
> > #!/bin/msh line at the top of the script.  How does the system know what
> > interpreter to use?
> 
> /bin/sh is the default interpreter.
> 
You might want to try adding that, is what I'm saying.  Busybox uses msh by
default, and may not have the code to handle that same inferrence.  Make the
interpreter an explicit #!/bin/sh or #!/bin/msh
Neil
> 
> Regards,
> Bernhard
> 
> _______________________________________________
> kexec mailing list
> kexec@...
> http://lists.infradead.org/mailman/listinfo/kexec
Permalink | Reply | 0 comments |
headers
Neil Horman | 6 Dec 2010 14:27
Picon
Favicon

Re: kdump_post : busybox returns "Applet not found"'

On Mon, Dec 06, 2010 at 11:59:08AM +0100, Louis Bouchard wrote:
> Hello,
> 
> On 05/12/2010 21:52, Bernhard Walle wrote:
> > Am 05.12.10 21:19, schrieb Neil Horman:
> >> I'm kind of suprised this is working at all.  I don't see a #!/bin/sh or
> >> #!/bin/msh line at the top of the script.  How does the system know what
> >> interpreter to use?
> > 
> > /bin/sh is the default interpreter.
> > 
> > 
> > Regards,
> > Bernhard
> > 
> > _______________________________________________
> > kexec mailing list
> > kexec@...
> > http://lists.infradead.org/mailman/listinfo/kexec
> 
> While, as Bernhard said, /bin/sh is default so the test script does
> work, the crashdc scripts that I'm testing do have the #!/bin/sh at the
> beginning, with identical behavior.
> 
Try modifying it to #1/bin/msh then, its possible that the script which busybox
puts together to emulate /bin/sh isn't working properly.  That would tell us
what needs fixing
Neil

> Kind regards,
> 
> ..Louis
> 
> -- 
> Louis Bouchard
> Linux Support Engineer
> Team lead, EMEA Linux Competency Center,
> Linux Advocate, HP
> 
> HP Technology Services - Global Competency Center
> Hewlett-Packard Company
> 
> louis.bouchard@...     / Email
> Mon-Fri 9-17<WET>,<GMT+2> / Working Hours
> Mark Fay                  / Manager
> mark.fay@...           / Manager's Email
> 
> _______________________________________________
> kexec mailing list
> kexec@...
> http://lists.infradead.org/mailman/listinfo/kexec
Permalink | Reply | 2 comments |
headers
Louis Bouchard | 6 Dec 2010 16:02
Picon
Favicon

Re: kdump_post : busybox returns "Applet not found"'

Hello Neil & al,

On 06/12/2010 14:27, Neil Horman wrote:
>
> Try modifying it to #1/bin/msh then, its possible that the script
which busybox
> puts together to emulate /bin/sh isn't working properly.  That would
tell us
> what needs fixing
> Neil
>

Looks like this was a "friday afternoon" kinda thing and you were right
in pointing to the shebang not being present in my test script.

For some ghostly reason, the ! at the start of the script I'm testing
disapeared so :

#!/bin/sh

became

# /bin/sh

I didn't have any issue with SLES11 since the #! is there.

Thanks for your quick help & sorry for the noise.

Kind regards,

...Louis

--

-- 
Louis Bouchard
Linux Support Engineer
Team lead, EMEA Linux Competency Center,
Linux Advocate, HP

HP Technology Services - Global Competency Center
Hewlett-Packard Company

louis.bouchard@...     / Email
Mon-Fri 9-17<WET>,<GMT+2> / Working Hours
Mark Fay                  / Manager
mark.fay@...           / Manager's Email
Permalink | Reply | 1 comment |
headers
Neil Horman | 6 Dec 2010 16:45
Picon
Favicon

Re: kdump_post : busybox returns "Applet not found"'

On Mon, Dec 06, 2010 at 04:02:57PM +0100, Louis Bouchard wrote:
> Hello Neil & al,
> 
> On 06/12/2010 14:27, Neil Horman wrote:
> >
> > Try modifying it to #1/bin/msh then, its possible that the script
> which busybox
> > puts together to emulate /bin/sh isn't working properly.  That would
> tell us
> > what needs fixing
> > Neil
> >
> 
> Looks like this was a "friday afternoon" kinda thing and you were right
> in pointing to the shebang not being present in my test script.
> 
> For some ghostly reason, the ! at the start of the script I'm testing
> disapeared so :
> 
> #!/bin/sh
> 
> became
> 
> # /bin/sh
> 
> I didn't have any issue with SLES11 since the #! is there.
> 
> Thanks for your quick help & sorry for the noise.
> 
> Kind regards,
> 
> ...Louis
> 
No problem, firday happens to the best of us :)
Neil

> -- 
> Louis Bouchard
> Linux Support Engineer
> Team lead, EMEA Linux Competency Center,
> Linux Advocate, HP
> 
> HP Technology Services - Global Competency Center
> Hewlett-Packard Company
> 
> louis.bouchard@...     / Email
> Mon-Fri 9-17<WET>,<GMT+2> / Working Hours
> Mark Fay                  / Manager
> mark.fay@...           / Manager's Email
Permalink | Reply | 0 comments |

Gmane