Skip to content

restart kdump service after copying cfg file #893

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 14, 2025
Merged

restart kdump service after copying cfg file #893

merged 1 commit into from
Jul 14, 2025
+2 −2

Conversation

vaishnavibhat
Copy link
Contributor

The patch takes care of restarting the kdump service after restoring to the original kdump cfg file.
When done, the next kdump iteration will run with the default kdump configuration. This will take care of post crash setup after the NFS, SSH kdump runs.

@vaishnavibhat
restart kdump service after copying cfg file
6762393 
The patch takes care of restarting the kdump service
after restoring to the original kdump cfg file.
When done, the next kdump iteration will run with the default
kdump configuration. This will take care of post crash setup
after the NFS, SSH kdump runs.

Signed-off-by: Vaishnavi Bhat <vaishnavi@linux.vnet.ibm.com>
@abdhaleegit abdhaleegit self-assigned this Jul 11, 2025
@abdhaleegit abdhaleegit self-requested a review July 11, 2025 05:35
PraveenPenguin
PraveenPenguin approved these changes Jul 11, 2025
View reviewed changes
Copy link
Collaborator

@PraveenPenguin PraveenPenguin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@abdhaleegit
Copy link
Collaborator

Updating local discussion here:

**Vaishnavi**
I checked with Sachin on this and he says the tests order has been changed now,, NFS and SSH dump are targetted last since it was causing this issue.
I have sent a patch to restart kdump services to restore the default configuration after every runs. Please check.
Will attach the logs shortly (edited) 

**Abdul Haleem**
usually the mount point in NFS/SSH is /mnt/var/crash  ...but if you see local the path is /var/crash
just curious if it is failing for local /var/crash or remote /mnt/var/crash
or due to NFS/SSH running first... it is not finding the local /var/crash ?


**Vaishnavi Bhat**
In the log file , the test were in this order :
PowerNVDump.KernelCrash_KdumpSSH()
PowerNVDump.KernelCrash_KdumpNFS()
PowerNVDump.KernelCrash_KdumpDLPAR() ———> Error seen here.
KdumpNFS —> this is setting dump target as remote and the reset to default dump location after collecting dump was not happening.
KdumpDLPAR —> checks for /var/crash as the dump location but fails as NFS is set as dump location.
Patch takes care of resetting the default dump location after every kdump run.

abdhaleegit
abdhaleegit approved these changes Jul 14, 2025
View reviewed changes
Copy link
Collaborator

@abdhaleegit abdhaleegit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@abdhaleegit abdhaleegit merged commit 50f289f into open-power:master Jul 14, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@abdhaleegit abdhaleegit abdhaleegit approved these changes

@PraveenPenguin PraveenPenguin PraveenPenguin approved these changes

Assignees

@abdhaleegit abdhaleegit

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@vaishnavibhat @abdhaleegit @PraveenPenguin