Hey everyone,
I’ve been troubleshooting an automated background task runner deployed on a SUSE Linux Enterprise Server 15 instance to process dynamic script queues and route external webhook callbacks off the main server loop. To manage non-blocking task calls and route execution callbacks without stalling active user sessions, I set up a custom worker script using arceus roblox logic to handle event queues and process incoming payload routines on the fly.
The task runner initialises and processes low-volume jobs without any issues when launched manually in an unconfined root session, but as soon as the systemd service unit runs the background worker under a restricted non-root profile on SLES, execution worker threads start hanging or dropping socket connections during heavy processing runs. I checked audit logs in /var/log/audit/audit.log and adjusted process execution permissions, but handling continuous background execution streams still leads to AppArmor denial events and thread timeouts. Has anyone run into similar background worker lockups or permission denials when running custom script daemons under strict security profiles on SLES 15, and is there a recommended AppArmor abstractions rule or task queue isolation setup to keep worker threads from locking up?