FAQ: Why was threatstack.service terminated by systemd?

Important

This only applies to Threat Stack® Agent version 2.3.0.

If you use an orchestration script to manage your host-based Linux Threat Stack® Agent, then a known limitation with Agent version 2.3.0 may cause systemd to terminate threatstack.service, resulting in an Agent that does not start. This is the direct result of network slowness or interruption.

To prevent this issue, you can increase the TS_SLEEP_LIMIT parameter’s value to 32 seconds and the TimeoutSec parameter’s value to 64 seconds

To increase the TS_SLEEP_LIMIT parameter’s value:

  1. Open the Command window.
  2. Go to /ExecStartPost/sbin/status/threatstack.service.
  3. Run the following command:
    systemctl set-environment TS_SLEEP_LIMIT=x
  4. To confirm the change, run the following command:
    systemctl show-environment

Note

If you need to return the TS_SLEEP_LIMIT to its original value, then run the following command:

systemctl unset-environment TS_SLEEP_LIMIT

To increase the TimeoutSec parameter’s value:

  1. Open the Command window.
  2. Go to /lib/systemd/system/threatstack.service.
  3. Find the TimeoutSec parameter.
  4. Change the value to 64.
  5. To ensure the change occurs, run the following command:
    systemctl daemon-reload
Was this article helpful?
0 out of 0 found this helpful