Failed To Start Sunshine.service: Unit Sunshine.service Not Found.

MIster jashon

6 min read

·

Oct 01, 2024

66

Share

Troubleshooting "failed to start sunshine.service: unit sunshine.service not found."

The error message "failed to start sunshine.service: unit sunshine.service not found." is a common issue encountered when trying to manage services on Linux systems, particularly using the systemd init system. This message indicates that the system cannot locate the service definition file for "sunshine.service". This file is essential for systemd to understand how to start, stop, and manage the service.

Common Causes of "failed to start sunshine.service: unit sunshine.service not found."

There are a few common reasons why you might see this error message:

1. The service file is missing or incorrectly named: The service definition file for "sunshine.service" must be present in the correct location and named accurately. It usually resides in /etc/systemd/system/ directory. If the file doesn't exist or is named incorrectly, systemd will be unable to find it.

2. The service file has an incorrect path in its unit file: The ExecStart= directive in the service file should point to the correct location of the executable responsible for the service. If the path is wrong, systemd won't be able to find the executable and will fail to start the service.

3. The service file has incorrect permissions: The service file must have the correct permissions to allow systemd to read and execute it. Typically, service files need to be owned by the root user and have read and execute permissions for the owner, group, and others.

4. The service file is not enabled: While a service file might be present, it needs to be enabled in order to start automatically at boot time. You can use the systemctl enable command to enable a service.

Troubleshooting Steps

Here's a step-by-step guide to troubleshooting "failed to start sunshine.service: unit sunshine.service not found.":

1. Verify the existence and name of the service file:

   • Use the command ls /etc/systemd/system/ to list all the service files present in the system directory.
   • Ensure that "sunshine.service" is among the listed files.

2. Inspect the service file contents:

   • If the file exists, open it using a text editor (e.g., nano /etc/systemd/system/sunshine.service).
   • Verify that the service name, description, and the ExecStart= directive are correctly defined.

3. Check the service file's permissions:

   • Use the ls -l /etc/systemd/system/sunshine.service command to check the permissions of the service file.
   • Ensure that the file is owned by the root user and has read and execute permissions for all users.
   • If not, use the chown and chmod commands to adjust the ownership and permissions accordingly.

4. Verify the executable path:

   • Make sure the path specified in the ExecStart= directive within the service file points to the correct executable responsible for the service.
   • Use which or whereis to find the correct location of the executable if you're unsure.

5. Enable the service:

   • If you want the service to start automatically at boot time, enable it using systemctl enable sunshine.service.
   • If you only want to start the service manually, you don't need to enable it.

6. Restart the systemd-systemd:

   • After making changes to the service file or permissions, restart systemd to ensure the changes are applied: systemctl daemon-reload.

Example Service File:

Here's an example of a sunshine.service file:

[Unit]
Description=Sunshine Service
After=network.target

[Service]
User=root
Group=root
ExecStart=/path/to/sunshine/executable

[Install]
WantedBy=multi-user.target

Remember to replace /path/to/sunshine/executable with the actual path to the executable responsible for your "sunshine" service.

Conclusion

The "failed to start sunshine.service: unit sunshine.service not found." error occurs when systemd cannot locate the service definition file. By carefully checking the existence, naming, permissions, and content of the sunshine.service file, you can troubleshoot this issue and get your service running smoothly.