Skip to content
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.

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

systemd Coredumps after applying several ztp policies #536

Open
akrzos opened this issue May 14, 2021 · 0 comments
Open

systemd Coredumps after applying several ztp policies #536

akrzos opened this issue May 14, 2021 · 0 comments

Comments

@akrzos
Copy link

akrzos commented May 14, 2021

I happened to see a few coredumps after applying several of the ztp policies to an SNO VM cluster.

It seems to occur while the VM is rebooting to apply a machineconfig:

May 14 13:54:24 sno00001 systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 13:54:24 sno00001 systemd-coredump[69664]: Failed to send coredump datagram: Connection reset by peer
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time

We can see this has occurred several times:

[root@sno00001 ~]# journalctl | grep coredump
May 14 13:44:41 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 13:44:41 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 13:44:41 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 13:44:41 sno00001 systemd-coredump[31133]: Failed to send coredump datagram: Connection reset by peer                                                                                 
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 13:54:24 sno00001 systemd-coredump[69664]: Failed to send coredump datagram: Connection reset by peer                                                                                 
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 13:54:24 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 14:00:17 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 14:00:17 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 14:00:17 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 14:00:17 sno00001 systemd-coredump[41551]: Failed to send coredump datagram: Connection reset by peer                                                                                 
May 14 14:13:44 sno00001 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 14:13:44 sno00001 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 14:13:44 sno00001 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time

A second instance of this occurred on another sno clusters as well:

May 14 15:45:05 sno00002 systemd[1]: crio-conmon-a83fc4e4e11dfaeb003c6a2a49d4543dae11e97864afbdf700ccac367f878e6b.scope: Succeeded.
May 14 15:45:05 sno00002 systemd[1]: crio-conmon-a83fc4e4e11dfaeb003c6a2a49d4543dae11e97864afbdf700ccac367f878e6b.scope: Consumed 62ms CPU time
May 14 15:45:05 sno00002 systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive.
May 14 15:45:05 sno00002 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.
May 14 15:45:05 sno00002 systemd[1]: systemd-coredump.socket: Failed with result 'resources'.
May 14 15:45:05 sno00002 systemd[1]: systemd-coredump.socket: Consumed 0 CPU time
May 14 15:45:05 sno00002 systemd-logind[1126]: Session 1 logged out. Waiting for processes to exit.
May 14 15:45:05 sno00002 systemd[1]: Stopping /run/user/1000 mount wrapper...
May 14 15:45:05 sno00002 systemd[1]: Stopped target Host and Network Name Lookups.

Only these policies had been applied:

# oc get policies -n sno00002
NAME                                          REMEDIATION ACTION   COMPLIANCE STATE   AGE
common-sub.common-console-policy              enforce              Compliant          160m
common-sub.common-log-forwarder-policy        enforce              Compliant          160m
common-sub.common-log-policy                  enforce              Compliant          160m
common-sub.common-log-sub-policy              enforce              Compliant          160m
common-sub.common-master-mc-mount-ns-policy   enforce              Compliant          160m
common-sub.common-mc-chronyd-policy           enforce              Compliant          160m
common-sub.common-mc-sctp-policy              enforce              Compliant          156m
common-sub.common-pao-sub-catalog-policy      enforce              Compliant          147m
common-sub.common-pao-sub-ns-policy           enforce              Compliant          144m
common-sub.common-pao-sub-oper-policy         enforce              Compliant          140m
common-sub.common-pao-sub-policy              enforce              Compliant          125m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant