9:26 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
Is /usr/bin/crashdc itself a shell script?
Dave
Yes, crashdc itself is a shell script, as well as the run-crashdc-*
which are intended to be invoked by the kdump mechanisms (kdump_post in
RHEL, KDUMP_POSTSCRIPT in SLES).
Kind Regards,
- --
Louis Bouchard, Linux Support Engineer
Team lead, EMEA Linux Competency Center,
Linux Ambassador, HP
HP Services 1 Ave du Canada
HP France Z.A. de Courtaboeuf
louis.bouchard(a)hp.com 91 947 Les Ulis
http://www.hp.com/go/linux France
http://www.hp.com/fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkq80yAACgkQDvqokHrhnCycRQCfbRmrQHpGnbBfZab3KDgROJFD
hnMAoKUTU2gIDs/WWl2golnM6JUoDC89
=ErtS
-----END PGP SIGNATURE-----
10:42 a.m.
New subject: crashdc : automatic data collection for new vmcores in text format
----- "Louis Bouchard" <louis.bouchard(a)hp.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
> Is /usr/bin/crashdc itself a shell script?
>
> Dave
Yes, crashdc itself is a shell script, as well as the run-crashdc-*
which are intended to be invoked by the kdump mechanisms (kdump_post in
RHEL, KDUMP_POSTSCRIPT in SLES).
Another question -- as I understand it, the RHEL kdump_post mechanism
only runs from the initramfs -- which doesn't contain the crash utility
and the vmlinux file (on purpose). How do you have it working?
Dave
10:47 a.m.
New subject: crashdc : automatic data collection for new vmcores in text format
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dave Anderson a écrit :
Another question -- as I understand it, the RHEL kdump_post mechanism
only runs from the initramfs -- which doesn't contain the crash utility
and the vmlinux file (on purpose). How do you have it working?
Dave
The initramfs mounts the whole root FS so both crash & vmlinux are
available. This is a main difference with SLES where the root FS is
mounted under /root while we're in the kexec kernel so some path reorg
is needed in order to access the files.
I also need to tell SLES11's kdump to load crash, gdb & a few other
things to make it work. This is my current task.
But right now, my RHEL version is almost working :-)
Kind Regards & good weekend,
- --
Louis Bouchard, Linux Support Engineer
Team lead, EMEA Linux Competency Center,
Linux Ambassador, HP
HP Services 1 Ave du Canada
HP France Z.A. de Courtaboeuf
louis.bouchard(a)hp.com 91 947 Les Ulis
http://www.hp.com/go/linux France
http://www.hp.com/fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkq85gAACgkQDvqokHrhnCwxgwCg0jPneCMTuLHRw5OMZFoplW2o
nZMAoLD4qGnyUiOOP8NNAbXZ/g6Y2i0Z
=7Odp
-----END PGP SIGNATURE-----
1:01 p.m.
New subject: crashdc : automatic data collection for new vmcores in text format
Louis Bouchard schrieb:
Dave Anderson a écrit :
> Another question -- as I understand it, the RHEL kdump_post mechanism
> only runs from the initramfs -- which doesn't contain the crash utility
> and the vmlinux file (on purpose). How do you have it working?
The initramfs mounts the whole root FS so both crash & vmlinux are
available. This is a main difference with SLES where the root FS is
mounted under /root while we're in the kexec kernel so some path reorg
is needed in order to access the files.
I also need to tell SLES11's kdump to load crash, gdb & a few other
things to make it work. This is my current task.
If you have any questions regarding kdump on SLES11, you can also ask
here since I implemented it and I'm still reading the list (although I
don't maintain it any more since I don't work at SUSE nowadays).
The fact that the root file system is always mounted in SLES11 was not
the ultimate goal. The plan was handle also the case when mounting the
root file system was not successful (mostly for netdump), of course with
less features (without copying kernel and debugging information). But I
doubt that it really works. :-(
In any case: I really appreciate that automatic data collection. In
fact, LKCD had also a simple program that generated a crash report and I
always wanted to implement it also for kdump, but never had time to do it.
Regards,
Bernhard
1:58 a.m.
New subject: crashdc : automatic data collection for new vmcores in text format
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Bernhard,
Bernhard Walle a écrit :
The fact that the root file system is always mounted in SLES11 was
not
the ultimate goal. The plan was handle also the case when mounting the
root file system was not successful (mostly for netdump), of course with
less features (without copying kernel and debugging information). But I
doubt that it really works. :-(
In any case: I really appreciate that automatic data collection. In
fact, LKCD had also a simple program that generated a crash report and I
always wanted to implement it also for kdump, but never had time to do it.
Thanks for your offer. I might need some help eventually.
Regarding the LKCD report, I'm familiar with it and always thought it
was a good help for us. This is why crashdc came about.
Hopefully, my daytime work won't keep me too busy so I should have
something to propose in the next few weeks.
Kind Regards,
- --
Louis Bouchard, Linux Support Engineer
Team lead, EMEA Linux Competency Center,
Linux Ambassador, HP
HP Services 1 Ave du Canada
HP France Z.A. de Courtaboeuf
louis.bouchard(a)hp.com 91 947 Les Ulis
http://www.hp.com/go/linux France
http://www.hp.com/fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkrAXpQACgkQDvqokHrhnCyv3gCgi5V7kstijix0qAcXXPw0NTw8
QtkAoOL0/UXgQYkpN6gxDAKPIiPR5Ipj
=d7+d
-----END PGP SIGNATURE-----
5538
days inactive
5541
days old
devel@lists.crash-utility.osci.io
4 comments
3 participants
participants (3)
-
Bernhard Walle -
Dave Anderson -
Louis Bouchard