Log Timeout Issue in Runs - No logs received for 7m0s, killing the process group

Last updated: April 1, 2025

Issue: Logs Timing Out

Error Message: No logs received for 7m0s, killing the process group

With Spacelift runs, you may encounter log timeout errors that halt execution due to an absence of logs for a specified duration.

Troubleshooting Steps

To identify the cause of the log timeout, follow these steps:

  1. Enable Debug Logging for Terraform Stacks
    If you're using a Terraform stack, you can temporarily add the environment variable TF_LOG with the value's DEBUG/TRACE. This setting will increase the log verbosity and may reveal clues about the underlying issue.
    How to set TF_LOG:

    • Go to your stack's Environment tab, add two new variable's with:

      • Name: TF_LOG

      • Value: DEBUG

      • Name: TF_LOG

      • Value: TRACE

    This is especially helpful for identifying potential issues within the Terraform stack processes.

  2. Check Private Worker Configuration
    For stack's running on private workers, the log timeout is controlled by the SPACELIFT_LAUNCHER_LOGS_TIMEOUT environment variable. Adjusting this variable allows you to set a custom timeout period, which may prevent timeouts during longer-running tasks.

    You can read more about configuring this variable in the Spacelift documentation on worker pools.

Common Causes for Log Timeouts

Log timeouts can occur for various reasons, including:

  • Rate Limiting
    External systems (such as APIs or repositories) may impose rate limits, which can delay logging output and trigger timeouts.

  • Firewall or Networking Connectivity Issues
    Network issues, such as firewall rules or DNS resolution problems, can prevent logs from reaching Spacelift within the required timeframe. Ensure that the worker has all necessary network permissions correctly configured.

  • Run-Specific Delays
    Long-running tasks or stages that do not produce output for extended periods may also trigger timeouts. Consider modifying task behavior to periodically output logs or extending the SPACELIFT_LAUNCHER_LOGS_TIMEOUT to accommodate such cases.

Next Steps

If the above steps do not resolve your log timeout issues, consider reaching out to Spacelift support with the following details:

  • Stack ID or Name

  • Any relevant environment variable settings (e.g., TF_LOG, SPACELIFT_LAUNCHER_LOGS_TIMEOUT)

  • Description of the run being ran

These details will help support analyze the problem more effectively.