Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2193258

Summary: insights-client service generating ABRT core dumps: "[Errno 2] No such file or directory: '/tmp/insights-client.ppid"
Product: Red Hat Enterprise Linux 7 Reporter: Amar Huchchanavar <ahuchcha>
Component: insights-clientAssignee: CSI Client Tools Bugs <csi-client-tools-bugs>
Status: CLOSED MIGRATED QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.9CC: ahitacat, cmarinea, fjansen, redakkan, ribanerj, stomsa
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-14 13:43:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amar Huchchanavar 2023-05-04 21:57:02 UTC
Description of problem:
Insights service generating ABRT core dumps. 

# abrt-cli ls
id 4d8793e4166e92034865a78d6e2a5654112c0898
reason:         utilities.py:127:write_to_disk:OSError: [Errno 2] No such file or directory: '/tmp/insights-client.ppid'
time:           Fri 07 Apr 2023 03:30:00 AM GMT
cmdline:        /usr/bin/python /usr/bin/insights-client --retry 3
package:        insights-client-3.1.7-2.el7_9
uid:            0 (root)
count:          1
Directory:      /var/spool/abrt/Python-2023-04-07-03:30:00-29062
Run 'abrt-cli report /var/spool/abrt/Python-2023-04-07-03:30:00-29062' for creating a case in Red Hat Customer Portal

# insights-client --version
Client: 3.1.7
Core: 3.1.16-1

# systemctl status insights-client
● insights-client.service - Insights Client
   Loaded: loaded (/usr/lib/systemd/system/insights-client.service; static; vendor preset: disabled)
   Active: inactive (dead) since Fri 2023-04-07 03:30:00 GMT; 5h 30min ago
     Docs: man:insights-client(8)
  Process: 29065 ExecStartPost=/bin/bash -c echo 1G >/dev/null 2>&1 > /sys/fs/cgroup/memory/system.slice/insights-client.service/memory.soft_limit_in_bytes (code=exited, status=0/SUCCESS)
  Process: 29063 ExecStartPost=/bin/bash -c echo 2G >/dev/null 2>&1 > /sys/fs/cgroup/memory/system.slice/insights-client.service/memory.memsw.limit_in_bytes (code=exited, status=0/SUCCESS)
  Process: 29062 ExecStart=/usr/bin/insights-client --retry 3 (code=exited, status=0/SUCCESS)
 Main PID: 29062 (code=exited, status=0/SUCCESS)

Apr 07 03:29:59 system1.example.com insights-client[29062]: File "/var/lib/insights/last_stable.egg/insights/client/utilities.py", line 127, in write_to_disk
Apr 07 03:29:59 system1.example.com insights-client[29062]: os.remove(filename)
Apr 07 03:29:59 system1.example.com insights-client[29062]: OSError: [Errno 2] No such file or directory: '/tmp/insights-client.ppid'
Apr 07 03:29:59 system1.example.com insights-client[29062]: Error in sys.exitfunc:
Apr 07 03:29:59 system1.example.com python[29062]: detected unhandled Python exception in '/usr/bin/insights-client'
Apr 07 03:30:00 system1.example.com insights-client[29062]: Traceback (most recent call last):
Apr 07 03:30:00 system1.example.com insights-client[29062]: File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs
Apr 07 03:30:00 system1.example.com insights-client[29062]: func(*targs, **kargs)
Apr 07 03:30:00 system1.example.com insights-client[29062]: File "/var/lib/insights/last_stable.egg/insights/client/utilities.py", line 127, in write_to_disk
Apr 07 03:30:00 system1.example.com insights-client[29062]: OSError: [Errno 2] No such file or directory: '/tmp/insights-client.ppid'

Version-Release number of selected component (if applicable):
insights-client-3.1.7-2.el7_9.noarch

How reproducible:
Customer site only

Steps to Reproduce:
1.


Actual results:
Apr 07 03:30:00 system1.example.com insights-client[29062]: OSError: [Errno 2] No such file or directory: '/tmp/insights-client.ppid'

Expected results:
It should not fail with above-mentioned error.

Additional info:
- This issue does not occur if we execute #insights-client manually

Comment 29 RHEL Program Management 2023-09-14 12:58:13 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 30 RHEL Program Management 2023-09-14 13:43:49 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 31 Red Hat Bugzilla 2024-01-13 04:25:25 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days