systemd service for auto-start in Raspberry Pi - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this systemd service status command?

Given the following systemd service file content, what will be the output of systemctl status myscript.service after enabling and starting the service successfully?

Raspberry Pi

[Unit]
Description=My Script Service
After=network.target

[Service]
ExecStart=/usr/bin/python3 /home/pi/myscript.py
Restart=on-failure

[Install]
WantedBy=multi-user.target

A Active: active (running) since <timestamp>; Main PID: <pid> (python3)

B Active: inactive (dead) since <timestamp>

C Failed to start myscript.service: Unit not found.

D Active: activating (start) since <timestamp>

💡 Hint

Think about what happens when a service is enabled and started without errors.

When a systemd service is enabled and started successfully, the status shows it as active (running) with the main process ID and timestamp.

🧠 Conceptual

intermediate

Which section of a systemd service file controls when the service starts?

In a systemd service file, which section defines the conditions or targets that determine when the service should start automatically?

A [Unit]

B [Install]

C [Service]

D [Timer]

💡 Hint

Look for the section that mentions 'WantedBy' or 'RequiredBy'.

The [Install] section specifies the target under which the service will be enabled to start automatically, such as multi-user.target.

🔧 Debug

advanced

Why does this systemd service fail to start?

This systemd service file fails to start the script. What is the cause?

Raspberry Pi

[Unit]
Description=Test Service

[Service]
ExecStart=/home/pi/myscript.py

[Install]
WantedBy=multi-user.target

A The ExecStart path lacks the interpreter, causing a permission error.

B The [Unit] section is missing the After=network.target line.

C The service file is missing the Restart=always directive.

D The WantedBy target is incorrect; it should be graphical.target.

💡 Hint

Consider how systemd executes scripts and what is needed to run a Python script.

ExecStart must specify the interpreter or the script must be executable with a shebang. Without it, systemd cannot run the script.

📝 Syntax

advanced

Identify the syntax error in this systemd service file snippet

Which option shows the correct syntax for the ExecStart line in a systemd service file?

Raspberry Pi

[Service]
ExecStart=python3 /home/pi/myscript.py

A ExecStart=>python3 /home/pi/myscript.py

B ExecStart: python3 /home/pi/myscript.py

C ExecStart = python3 /home/pi/myscript.py

D ExecStart=python3 /home/pi/myscript.py

💡 Hint

Check the correct assignment operator and spacing in systemd unit files.

The correct syntax uses '=' without spaces around it. Other options use invalid characters or spacing.

🚀 Application

expert

How to ensure a systemd service restarts automatically on failure?

You want your Raspberry Pi systemd service to restart automatically if the script crashes. Which option correctly adds this behavior?

Raspberry Pi

[Service]
ExecStart=/usr/bin/python3 /home/pi/myscript.py

A Add RestartSec=5 under the [Unit] section

B Add Restart=always under the [Install] section

C Add Restart=on-failure under the [Service] section

D Add Restart=on-abort under the [Service] section

💡 Hint

Restart directives belong in the [Service] section and control restart behavior on failure.

Restart=on-failure in [Service] tells systemd to restart the service if it exits with an error.

Practice

1. What is the main purpose of creating a systemd service on a Raspberry Pi?

easy

A. To update the Raspberry Pi operating system

B. To manually run a program only once

C. To make a program start automatically when the Raspberry Pi boots

D. To uninstall software from the Raspberry Pi

Solution

1. Step 1: Understand systemd service purpose

   A systemd service is designed to manage programs and make them start automatically during boot.

2. Step 2: Identify the correct use case

   Starting a program automatically on boot matches the purpose of systemd services.

3. Final Answer:

   To make a program start automatically when the Raspberry Pi boots -> Option C

4. Quick Check:

   systemd service = auto-start program [OK]

Hint: Remember: systemd services auto-start programs on boot [OK]

Common Mistakes:

• Confusing systemd with manual program execution
• Thinking systemd updates the OS
• Believing systemd uninstalls software

2. Which of the following is the correct section header in a systemd service file to define the program to run?

easy

A. [Service]

B. [Unit]

C. [Install]

D. [Program]

Solution

1. Step 1: Recall systemd service file structure

   A systemd service file has three main sections: [Unit], [Service], and [Install].

2. Step 2: Identify where the program command goes

   The program to run is specified under the [Service] section using ExecStart.

3. Final Answer:

   [Service] -> Option A

4. Quick Check:

   Program command in [Service] section [OK]

Hint: Program command is always under [Service] section [OK]

Common Mistakes:

• Using [Unit] or [Install] for program commands
• Assuming [Program] is a valid section
• Confusing section headers

3. Given this systemd service file snippet:

[Unit]
Description=My Script

[Service]
ExecStart=/home/pi/myscript.sh

[Install]
WantedBy=multi-user.target

What command should you run to make this service start automatically on boot?

medium

A. sudo systemctl start myscript.service

B. sudo systemctl enable myscript.service

C. sudo systemctl reload myscript.service

D. sudo systemctl stop myscript.service

Solution

1. Step 1: Understand difference between start and enable

   Starting runs the service now; enabling sets it to run on boot.

2. Step 2: Identify command to auto-start on boot

   Use sudo systemctl enable myscript.service to enable auto-start.

3. Final Answer:

   sudo systemctl enable myscript.service -> Option B

4. Quick Check:

   Enable = auto-start on boot [OK]

Hint: Enable service to auto-start, start to run now [OK]

Common Mistakes:

• Using start instead of enable for auto-start
• Confusing reload with enable
• Stopping service instead of enabling

4. You created a systemd service file but after reboot, the program does not start. Which of these is the most likely mistake?

medium

A. You named the service file with a .txt extension

B. You used sudo systemctl start instead of enable

C. You put the program command under the [Unit] section

D. You forgot to run sudo systemctl daemon-reload after creating the service file

Solution

1. Step 1: Understand systemd reload requirement

   After creating or changing service files, systemd must reload to recognize changes.

2. Step 2: Identify the missing reload command

   Forgetting sudo systemctl daemon-reload means systemd ignores new service files.

3. Final Answer:

   You forgot to run sudo systemctl daemon-reload after creating the service file -> Option D

4. Quick Check:

   daemon-reload needed after service file changes [OK]

Hint: Always run daemon-reload after editing service files [OK]

Common Mistakes:

• Skipping daemon-reload after file changes
• Confusing start and enable commands
• Placing ExecStart in wrong section
• Wrong file extension for service files

5. You want your Raspberry Pi to run a Python script at boot, but only after the network is ready. Which systemd service file snippet correctly ensures this?

hard

A. [Unit]\nDescription=Run Python Script\nAfter=network-online.target\nWants=network-online.target\n\n[Service]\nExecStart=/usr/bin/python3 /home/pi/script.py\n\n[Install]\nWantedBy=multi-user.target

B. [Unit]\nDescription=Run Python Script\nRequires=network.target\n\n[Service]\nExecStart=/usr/bin/python3 /home/pi/script.py\n\n[Install]\nWantedBy=multi-user.target

C. [Unit]\nDescription=Run Python Script\nBefore=network-online.target\n\n[Service]\nExecStart=/usr/bin/python3 /home/pi/script.py\n\n[Install]\nWantedBy=multi-user.target

D. [Unit]\nDescription=Run Python Script\nAfter=multi-user.target\n\n[Service]\nExecStart=/usr/bin/python3 /home/pi/script.py\n\n[Install]\nWantedBy=network-online.target

Solution

1. Step 1: Understand network dependency in systemd

   To run after network is ready, use After=network-online.target and Wants=network-online.target.

2. Step 2: Check each option's unit section

   [Unit]\nDescription=Run Python Script\nAfter=network-online.target\nWants=network-online.target\n\n[Service]\nExecStart=/usr/bin/python3 /home/pi/script.py\n\n[Install]\nWantedBy=multi-user.target correctly uses both directives to wait for network online before starting.

3. Final Answer:

   After=network-online.target and Wants=network-online.target -> Option A

4. Quick Check:

   Use After and Wants with network-online.target for network wait [OK]

Hint: Use After=network-online.target and Wants=network-online.target [OK]

Common Mistakes:

• Using network.target instead of network-online.target
• Placing Before=network-online.target instead of After
• Wrong WantedBy target
• Missing Wants directive