issues with kdump
by Adam Stokes
So with kdump nothing is passed to the server stating an IP or a
directory that was created for the dump etc. Only suggestion I've come
up with is to setup some sort of fastback daemon to utilize inotify.
Problem is that is on the kdump server which may or may not be the same
system fastback is run on. Same goes for netdump as well, where we run
into an issue where files exists on different systems but still need to
be tied to one system.
We can upload bits and pieces like sosreport from crashing server, then
the core from the kdump/netdump server and attempt to get it tied to a
ticket but I see this as being problematic.
Another suggestion is to just setup one box as the fastback server
which may or may not be the coredump server and have all data sent to
that server for processing and transfer to RH.
any ideas?
--
__ __
.-----.| |_.-----.| |--.-----.-----.
|__ --|| _| _ || <| -__|__ --|
|_____||____|_____||__|__|_____|_____|
.----------------------------------.
( ajs(a)redhat.com || 919.754.4187 )
`----------------------------------'
15 years, 3 months