------- Comment From [email protected] 2016-01-04 21:37 EDT------- This appears to be another init-script vs upstart confusion issue. The "status" case in /etc/init.d/kdump-tools leads one to believe that "/usr/sbin/kdump-config status" will be run:
status) $KDUMP_SCRIPT status ;; This would have generated the expected output: # /usr/sbin/kdump-config status current state : ready to kdump Instead, the /lib/lsb/init-functions.d/01-upstart-lsb hook intercepts the "status" option and translates it to: "initctl status kdump-tools" which returns a slightly less useful status which I have to assume indicates that the kdump-tools startup is simply "waiting" for a kdump event. For purposes of test/setup validation, you can either check the syslog messages for kdump startup failures, or run "/usr/sbin/kdump-config status" instead of "service kdump-tools status". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528759 Title: ISST-LTE: kdump service fails to start on Ubuntu14.04.4 lpar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1528759/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
