Startup

The CoolerControl daemon (coolercontrold) is managed by systemd on most Linux distributions. This page covers how to control the daemon's startup behavior.

Service Management

Start the Daemon

sudo systemctl start coolercontrold

Stop the Daemon

sudo systemctl stop coolercontrold

Restart the Daemon

sudo systemctl restart coolercontrold

Check Status

sudo systemctl status coolercontrold

Enable/Disable Automatic Startup

Enable at Boot

To have the daemon start automatically at boot:

sudo systemctl enable coolercontrold

Disable at Boot

To prevent the daemon from starting automatically at boot:

sudo systemctl disable coolercontrold

Check if Enabled

sudo systemctl is-enabled coolercontrold

Startup Delay

If you need to delay the daemon startup, such as to allow more time for devices to come up at boot, CoolerControl has a built-in setting for that so there's no need to use i.e. a sleep function.

Viewing Logs

To view the daemon's startup logs:

sudo journalctl -u coolercontrold

For real-time logs:

sudo journalctl -u coolercontrold -f

For logs since last boot:

sudo journalctl -u coolercontrold -b

Troubleshooting Startup Issues

If the daemon fails to start:

1. Check the status and logs:

   sudo systemctl status coolercontrold
   sudo journalctl -u coolercontrold -n 100

2. Verify configuration file syntax:

   sudo coolercontrold --config

3. Check for port conflicts:

   sudo netstat -tlnp | grep 11987

Restart on Failure

The daemon systemd service is configured to restart automatically on failure.

See Also

• Configuration Files - Learn about daemon configuration files
• Logs and Debugging - Detailed logging and debugging information