On Jun 28, 2023, at 16:11, Patrick Dupre <pdupre(a)gmx.com> wrote:
Hello,
I am in trouble with dwagent
dwagent.service - DWAgent
Loaded: loaded (/etc/systemd/system/dwagent.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Wed 2023-06-28 21:16:30 CEST; 52min ago
Process: 1447 ExecStart=/bin/sh -c "/usr/local/dwagent/native/dwagsvc"
start_internal (code=exited, status=0/SUCCESS)
Main PID: 1463 (dwagsvc)
Tasks: 46 (limit: 38199)
Memory: 45.9M
CPU: 7.044s
CGroup: /system.slice/dwagent.service
├─1463 /bin/sh /usr/local/dwagent/native/dwagsvc run
├─1467 /usr/local/dwagent/runtime/bin/dwagent agent.pyc -filelog
├─8884 bash -l
├─9000 systemctl status dwagent
└─9001 less
Jun 28 21:16:28 homere systemd[1]: Starting dwagent.service - DWAgent...
Jun 28 21:16:28 homere sh[1447]: Starting DWAgent daemon
Jun 28 21:16:30 homere systemd[1]: Started dwagent.service - DWAgent.
It seems that when a user logout, after a while, the service stall.
It is restarted when this user login back.
I have not explanation.
Perhaps GDM is suspending due to the new power policy in fedora 38, and a network
connection is being dropped or something related?
It’s impossible to predict what’s going on without knowing what is actually run by this
non-fedora software.
--
Jonathan Billings