The insights-client is creating  .dump files on RHEL-9.5 machine:

 
~~~~
Feb xx 00:59:25 client systemd[1]: insights-client.service: Watchdog timeout (limit 15min)!
Feb xx 00:59:25 client systemd[1]: insights-client.service: Watchdog timeout (limit 15min)!
Feb xx 00:59:25 client systemd[1]: insights-client.service: Killing process 1507827 (insights-client) with signal SIGABRT.
Feb xx 00:59:25 client systemd[1]: insights-client.service: Killing process 1508481 (python3) with signal SIGABRT.
~~~~
 

Even increasing the timeout doesn't help to address the reported issue: 
~~~~~~~

1. Create an include directory in /etc/systemd/system/

1. mkdir -p /etc/systemd/system/insights-client.service.d

2. Create a configuration file for insights-client.service

          ~~~~~~

1. vi /etc/systemd/system/insights-client.service.d/myinsights-client.conf
   [Service]
   WatchdogSec=1200
   ~~~~~~~

3. Reload systemd manager configuration:

1. systemctl daemon-reload

4. Start insights-client.service and verify that the service is now running:

1. systemctl start insights-client.service
2. systemctl status insights-client.service

~~~~~~~

1. systemctl status insights-client.service
   ● insights-client.service - Insights Client
   Loaded: loaded (/usr/lib/systemd/system/insights-client.service; static)
   Drop-In: /etc/systemd/system/insights-client.service.d
   └─myinsights-client.conf
   Active: activating (auto-restart) (Result: watchdog) since Mon 2025-xx-xx 12:44:47 EST; 15s ago
   TriggeredBy: ● insights-client.timer
   Docs: man:insights-client(8)
   Process: 2770909 ExecStart=/usr/bin/insights-client (code=dumped, signal=ABRT)
   Main PID: 2770909 (code=dumped, signal=ABRT)
   CPU: 28.912s
   root@client /epic_xxxx # ll
   total 281M
   rw------. 1 root root 29M Mar 3 12:44 insights-client.xxxxxxxxx.2770909.1741023886.dump
   rw------. 1 root root 253M Mar 3 12:44 python3.xxxxxxxxxx.2771649.1741023886.dump