That message may also be caused by bug 1196335 - it may be worth checking the actual service output. kdump currently isn't starting reliably in my experience.