Pulpcore coredumps during stopping services

Support
1

Problem:
Pulcore coredumps everytime when foreman-maintain service stop is executed and critical messages are sent to /var/log/messages.
This happens everyday when offline backup is started in our environment.

Jan 16 04:00:19 hostname systemd-coredump[297768]: Process 210742 (pulpcore-api) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297770]: Process 210746 (pulpcore-api) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297769]: Process 210722 (pulpcore-api) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297767]: Process 210770 (pulpcore-api) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297794]: Process 210720 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297795]: Process 210787 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297797]: Process 210762 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297815]: Process 210908 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297817]: Process 210896 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297819]: Process 210923 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297826]: Process 210731 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:19 hostname systemd-coredump[297833]: Process 210743 (pulpcore-conten) of user 991 dumped core.
Jan 16 04:00:20 hostname systemd-coredump[297851]: Process 210696 (pulpcore-conten) of user 991 dumped core.

Expected outcome:
Foreman services will be gracefully stopped.

Foreman and Proxy versions:
foreman-3.9.1-1.el8.noarch
katello-4.11.0-1.el8.noarch

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data:

production.log (65.0 KB)
messages.log (197.1 KB)

2

Hi! Apologies for the delay with help here.

Before the core dump in your messages log, pulp is indicating that it’s unable to connect to the database. The offline backup you mentioned is likely the cause; it’s closing the db endpoints before pulp closes its connections. A workaround would be to spin down the foreman service then run the offline backup.

This is a small error on the foreman-maintain side. I’ll go ahead and submit a report for it on Monday. Thanks for letting us know.

3

Foreman maintain issue link