Bug 2260124
| Summary: | [abrt] setroubleshoot-server: g_malloc(): python3.12 killed by SIGTRAP | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joerg Skottke <jsk_priv> | ||||||||||||||||||||||||
| Component: | setroubleshoot | Assignee: | Petr Lautrbach <plautrba> | ||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 39 | CC: | dwalsh, jsk_priv, jsullivan3, mmalik, plautrba, vmojzis | ||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/57c9f0e69ccd8a76c3db767e51c8d1f1c929028 | ||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:05c90fc3d12e02a7eee7e22522c33610862485a3;VARIANT_ID=workstation; | ||||||||||||||||||||||||||
| Fixed In Version: | setroubleshoot-3.3.33-1.fc39 | Doc Type: | If docs needed, set a value | ||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||
| Last Closed: | 2024-02-25 01:25:43 UTC | Type: | --- | ||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||
|
Description
Joerg Skottke
2024-01-24 15:36:33 UTC
Created attachment 2010226 [details]
File: proc_pid_status
Created attachment 2010227 [details]
File: maps
Created attachment 2010228 [details]
File: limits
Created attachment 2010229 [details]
File: environ
Created attachment 2010230 [details]
File: open_fds
Created attachment 2010231 [details]
File: mountinfo
Created attachment 2010232 [details]
File: os_info
Created attachment 2010233 [details]
File: cpuinfo
Created attachment 2010234 [details]
File: core_backtrace
Created attachment 2010235 [details]
File: dso_list
Created attachment 2010236 [details]
File: backtrace
A backup program that is receiving a BTRFS snapshot in a permissive context reliably causes setroubleshootd to exit with a SIGTRAP and a log indicating it could not allocate 4096 bytes. reporter: libreport-2.17.11 type: CCpp reason: python3.12 killed by SIGTRAP journald_cursor: s=8006dcfc6b484285a13cd7a935ba0802;i=cb1f;b=a0a513c547b448f89630ada625c6453e;m=1f9f0809d;t=6113268fe59aa;x=b5561e01607e7d2f executable: /usr/bin/python3.12 cmdline: /usr/bin/python3 -Es /usr/sbin/setroubleshootd -f cgroup: 0::/system.slice/setroubleshootd.service rootdir: / uid: 811 kernel: 6.7.4-200.fc39.x86_64 package: setroubleshoot-server-3.3.32-7.fc39 runlevel: N 3 backtrace_rating: 4 crash_function: g_malloc comment: A backup program that is receiving a BTRFS snapshot in a permissive context reliably causes setroubleshootd to exit with a SIGTRAP and a log indicating it could not allocate 4096 bytes. Log message in question: ../glib/gmem.c:136: failed to allocate 4096 bytes I found that the setroubleshootd.service unit has the directive "LimitAS=1G" in its "[Service]" section. The systemd documentation recommends using "MemoryMax" instead of "LimitAS" since "LimitAS=1G" limits the memory to the first 1G, whereas "MemoryMax=1G" limits the memory to using no more than 1G. I created the file /etc/systemd/system/setroubleshootd.service.d/memory.conf with the following contents: [Service] LimitAS=infinity MemoryMax=1G Since implementing this change, I haven't seen the errors. This commit, which seems to be part of 3.3.33, implements this change: https://gitlab.com/setroubleshoot/setroubleshoot/-/commit/2d3e32fe2cd356f7ccc25004102177431d3ca2bc Thanks for the report and the investigation! FEDORA-2024-145c2c9ee8 (setroubleshoot-3.3.33-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-145c2c9ee8 FEDORA-2024-6162b056b8 (setroubleshoot-3.3.33-1.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-6162b056b8 FEDORA-2024-6162b056b8 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6162b056b8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6162b056b8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-145c2c9ee8 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-145c2c9ee8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-145c2c9ee8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-145c2c9ee8 (setroubleshoot-3.3.33-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-6162b056b8 (setroubleshoot-3.3.33-1.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |