Properly autostart Kraken on boot?

I have a bare-metal Ubuntu ×64 installation, and I wanted to fire up the KrakenDOA on boot but ran into issues.

I’ve swapped line 3 in ./kraken_doa_start.sh for the source version, then created a simple systemd service unit

[Unit]
Description=Fire up KrakenDOA after boot
After=network.target network-online.target
StartLimitIntervalSec=1
StartLimitBurst=5
StartLimitIntervalSec=10

[Service]
Type=simple
User=root
Group=root
Restart=always
RestartSec=1
WorkingDirectory=/home/%redacted%/krakensdr_doa
ExecStart=/bin/bash /home/%redacted%/krakensdr_doa/kraken_doa_start.sh

[Install]
WantedBy=default.target

By checking the processes and the system load average, I see that the DAQ chain is working, but both the 8080 and 8081 port connections are refused, so the web part is not running. ui.log is blank, and I’m having difficulty tracing the problem further.

How did you solve the unattended startup? :pray:

It may be an issue with starting directories, or the target.

On the Pi the service looks like:


[Unit]
Description=Start KrakenSDR Code
After=multi-user.target

[Service]
Type=forking
Workingdirectory=/home/krakenrf/krakensdr_doa
ExecStart=/usr/bin/sh /home/krakenrf/start.sh

[Install]
WantedBy=multi-user.target
nano start.sh
#!/bin/bash

# This script is run on startup by a systemd service at /lib/systemd/system/krakensdr.service
cd /home/krakenrf/krakensdr_doa
./kraken_doa_start.sh

kraken_doa_start note:

We must use “source /home/krakenrf/miniforge3/etc/profile.d/conda.sh” instead of eval to activate conda. Also don’t forget #!/bin/bash

(Make sure you change your home directory /home/krakenrf/ as required for your own system.

1 Like

The reference PI script did the trick, thanks. Not doing a cd was the issue, thank you, Carl!