kdump_post : busybox returns "Applet not found"
Subsystems (2)
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Quoted 27 lines · Louis Bouchard
<!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.shI get the following from busybox :kdump-post.sh: applet not found<br>
<br>
<blockquote><tt>Copying data : [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 changedkdump_post.shto one single "echo This is working" line and I still get the same thing :<br>
Quoted 8 lines
<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
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Am 05.12.10 21:19, schrieb Neil Horman:
Quoted 3 lines
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
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Hello,
Quoted 8 lines · Bernhard Walle
Am 05.12.10 21:19, schrieb Neil Horman:
Quoted 3 lines
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/shis the default interpreter.
Quoted 7 lines
Regards,
Bernhard_______________________________________________
kexec mailing list
[email protected]
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
Signature · 17 lines
Louis Bouchard Linux Support Engineer Team lead, EMEA Linux Competency Center, Linux Advocate, HP HP Technology Services - Global Competency Center Hewlett-Packard Company [email protected] / Email Mon-Fri 9-17<WET>,<GMT+2> / Working Hours Mark Fay / Manager [email protected] / Manager's Email _______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
Re: kdump_post : busybox returns "Applet not found"'
Quoted 14 lines · Louis Bouchard
Hello,
Quoted 11 lines · Bernhard Walle
Am 05.12.10 21:19, schrieb Neil Horman:
Quoted 3 lines
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/shis the default interpreter.Regards,
Bernhard
Quoted 9 lines
Quoted 4 lines
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexecWhile, as Bernhard said,
/bin/shis 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
Quoted 22 lines
Kind regards,
..Louis
Signature · 17 lines
Louis Bouchard Linux Support Engineer Team lead, EMEA Linux Competency Center, Linux Advocate, HP HP Technology Services - Global Competency Center Hewlett-Packard Company [email protected] / Email Mon-Fri 9-17<WET>,<GMT+2> / Working Hours Mark Fay / Manager [email protected] / Manager's Email _______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Re: kdump_post : busybox returns "Applet not found"'
Hello Neil & al,
Quoted 2 lines · Neil Horman
Try modifying it to #1/bin/msh then, its possible that the script
which busybox
Quoted 1 line
puts together to emulate
/bin/shisn't working properly. That would
tell us
Quoted 3 lines
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
Signature · 17 lines
Louis Bouchard Linux Support Engineer Team lead, EMEA Linux Competency Center, Linux Advocate, HP HP Technology Services - Global Competency Center Hewlett-Packard Company [email protected] / Email Mon-Fri 9-17<WET>,<GMT+2> / Working Hours Mark Fay / Manager [email protected] / Manager's Email _______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
Re: kdump_post : busybox returns "Applet not found"'
Quoted 24 lines · Louis Bouchard
Hello Neil & al,
Quoted 2 lines · Neil Horman
Try modifying it to #1/bin/msh then, its possible that the script
which busybox
Quoted 1 line
puts together to emulate
/bin/shisn't working properly. That wouldtell us
Quoted 3 lines
what needs fixing
NeilLooks 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
Quoted 8 lines
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
Quoted 13 lines
Signature · 12 lines
Louis Bouchard Linux Support Engineer Team lead, EMEA Linux Competency Center, Linux Advocate, HP HP Technology Services - Global Competency Center Hewlett-Packard Company [email protected] / Email Mon-Fri 9-17<WET>,<GMT+2> / Working Hours Mark Fay / Manager [email protected] / Manager's Email
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Quoted 7 lines · Bernhard Walle
Am 05.12.10 21:19, schrieb Neil Horman:
Quoted 3 lines
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/shis 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
Quoted 8 lines
Regards,
Bernhard_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec