Ytuner on PI Zero 2 W does not start after reboot

[Wakebored]

Hi all,

I have installed Raspberry Pi OS Bookworm (tried both 64 and 32 bit variants, no desktop) onto my Pi zero 2 W. I then did the following:

• Set the IP address to 192.168.1.2
• On my Yamaha receiver, set the DNS server to 192.168.1.2
• install SQLite (sudo apt-get install sqlite3
• run the install script (chmod +x install-ytuner-1.2.6-linux.sh followed by sudo ./install-ytuner-1.2.6-linux.sh)

After everything installs, I can see that my Yamaha receiver picks up YTuner, and I can browse stations, listen to music, etc. Everything seems to work. If I do a sudo-reboot, ytuner no longer works and my receiver is stuck at "Please wait". Manually trying to start ytuner (sudo /opt/ytuner/ytuner) comes back with error messages saying it can't bind to port 80 and 53 (presumably because it's already running on reboot).

Any ideas on what could be wrong? I can ssh into the pi after reboot, so I know it's working, and I can ping it. Using a web browser and trying to go to http://192.168.1.2 returns an immediate 404 (which tells me the port is open on the pi). The pi has a static address (192.168.1.2)

[TheBossME]

@Wakebored read here:

#123

This script do the job !

You need ytuner.service !!!

Regards Beatrice

[Wakebored]

Thanks for the reply, but I did run that script. And it does work perfectly until I reboot the Pi zero 2. Then my receiver can't see it. If I reformat the SD card and repeat the steps/script I outlined above, it starts working again until I do a power cycle or reboot

Can you expand on what you mean by ytuner.service? It seems to me that it's running in that port 80 and 53 are being used on reboot. And the script does the systemctl commands to set ytuner.service to be set up already for that

[TheBossME]

can't get you. Mmmhh 😟

• ytuner.service is created while running that script.

• check it while typing: systemctl status ytuner.service

output should look like:

● ytuner.service - ytuner radio service
Loaded: loaded (/etc/systemd/system/ytuner.service; enabled; preset: enabled)
Active: active (running) since Sat 2025-05-24 15:07:41 CEST; 17h ago
TriggeredBy: ● ytuner.timer
Main PID: 180 (ytuner)
Tasks: 4 (limit: 75678)
Memory: 87.8M
CPU: 39.565s
CGroup: /system.slice/ytuner.service
└─180 /opt/ytuner/ytuner

Mai 24 15:07:41 ytuner01 systemd[1]: Started ytuner.service - ytuner radio service.

• also you should type: cat /var/log/ytuner.log

output should look like:

YTuner v1.2.6 Copyright (c) 2024 Greg P. (https://github.com/coffeegreg)
24-5-25 15:07:41 : Inf : Translator: loaded.
24-5-25 15:07:41 : Inf : Starting services...
24-5-25 15:07:41 : Inf : Successfully loaded 852 my stations.
24-5-25 15:07:41 : Inf : Check21-5-25 14:05:26 : Inf : Checking local database.
21-5-25 14:05:26 : Inf : Preparing local database This may take a while...
21-5-25 14:06:19 : Inf : Local database is ready.
22-5-25 14:05:26 : Inf : Checking local database.
23-5-25 14:05:26 : Inf : Checking local database.
23-5-25 14:05:26 : Inf : Preparing local database This may take a while...
23-5-25 14:06:19 : Inf : Local database is ready.
database.

• Type: ip a: you should see your ip address of your Raspberry Pi. The IP should be set to static or reserved on your dhcp server.

• set your NetRadio in network settings properly. The netRadio will not see the ytuner.service automaticall.

Generally a static setup is needed, so please change from dhcp to static, while changing the 2 dns entries to the ip address of the pi. That's it.

[Wakebored]

This is what I see when I type in the commands:

pi@raspberrypi:~ $ systemctl status ytuner.service
● ytuner.service - YTuner Service
Loaded: loaded (/etc/systemd/system/ytuner.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-05-25 21:20:25 CDT; 3min 55s ago
Main PID: 529 (ytuner)
Tasks: 4 (limit: 171)
CPU: 737ms
CGroup: /system.slice/ytuner.service
└─529 /opt/ytuner/ytuner

May 25 21:20:25 raspberrypi systemd[1]: Started ytuner.service - YTuner Service.

For the log I get:

pi@raspberrypi:~ $ cat /var/log/ytuner.log
YTuner v1.2.6 Copyright (c) 2024 Greg P. (https://github.com/coffeegreg)
25-5-25 21:20:26 : Err : No entries on IP List.
25-5-25 21:20:26 : Err : No entries on IP List.
25-5-25 21:20:26 : Err : No entries on IP List.
25-5-25 21:20:26 : Inf : Starting services...
25-5-25 21:20:26 : Inf : Successfully loaded 10 my stations.
25-5-25 21:20:26 : Inf : Loading RB UUIDs cache file.
25-5-25 21:20:26 : Inf : Successfully loaded 55392 RB UUIDs from cache file.
25-5-25 21:20:26 : Inf : DNS Service: listening on: :53.
25-5-25 21:20:40 : Dbg : DNS Query intercept : radioyamaha.vtuner.com.
25-5-25 21:20:41 : Dbg : DNS Query intercept : radioyamaha2.vtuner.com.
25-5-25 21:20:51 : Dbg : DNS Query intercept : radioyamaha.vtuner.com.

On my receiver (Yamaha) I am on the NET RADIO mode and I just have the message PLEASE WAIT.

I see that the first 3 entries in the log are "No entries on IP List". I'm not sure what that means. It looks like it's capturing the requests from the receiver though (by the DNS query intercepts.

Again, this is a clean install of Bookworm with all the updates/upgrade and nothing else installed but ytuner and sqlite3

[TheBossME]

@Wakebored i think there is no need to go to the code,and analyze there.

generally use the latest Debian release (actually bookworm)

• Do apt update && apt upgrade

• Type ip a

• cat /var/log/ytuner.log (post result here)

• type ss -tulpn

Do reboot and type ss -tulpn again.. port 80 should be used by ytuner and port 53 UDP.

Additional: are you using 64 Bit Debian lite ?. it should run on that processor. I can't test, while haven't that device.

Change ytuner.service with:

• sudo systemctl edit ytuner

- [Unit]
After=network-online.target
Wants=network-online.target

[Service]
ExecStartPre=/bin/sleep 10

Type=oneshot
ExecStart=/bin/bash -c 'until ping -c1 192.168.1.1; do sleep 1; done'
RemainAfterExit=yes

[TheBossME]

@Wakebored please try this massive modified ytuner.service for,your Pi 2W, sorry descriptions are in german language

[Unit]
Description=ytuner Radio Service
Documentation=man:ytuner(1)
# Erweiterte Netzwerk-Abhängigkeiten für stabiles Timing
Wants=network-online.target network.target
After=network-online.target network.target xvfb.service systemd-networkd-wait-online.service
Requires=xvfb.service
# Verhindert Start wenn Netzwerk nicht verfügbar
ConditionPathExists=/sys/class/net/wlan0
ConditionPathExists=!/var/run/ytuner.disabled
StopWhenUnneeded=true

[Service]
Type=simple
User=root
Group=root

# Pre-Start Checks und Netzwerk-Validierung
ExecStartPre=/bin/bash -c 'echo "$(date): Starting ytuner pre-checks" >> /var/log/ytuner_startup.log'
ExecStartPre=/bin/bash -c 'ip addr show >> /var/log/ytuner_startup.log 2>&1'
ExecStartPre=/bin/bash -c 'until ping -c1 -W2 192.168.1.1 >/dev/null 2>&1; do echo "$(date): Waiting for gateway..." >> /var/log/ytuner_startup.log; sleep 2; done'
ExecStartPre=/bin/bash -c 'until ip route get 8.8.8.8 >/dev/null 2>&1; do echo "$(date): Waiting for routing..." >> /var/log/ytuner_startup.log; sleep 1; done'
ExecStartPre=/bin/bash -c 'sleep 3'
ExecStartPre=/bin/bash -c 'echo "$(date): Network ready, starting ytuner" >> /var/log/ytuner_startup.log'

# Hauptprozess mit erweiterten Umgebungsvariablen
ExecStart=/opt/ytuner/ytuner
WorkingDirectory=/opt/ytuner

# Erweiterte Umgebungsvariablen
Environment="HOME=/root"
Environment="USER=root"
Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
# IndySockets Debug (falls unterstützt)
Environment="INDY_DEBUG=1"
Environment="INDY_LOG_LEVEL=DEBUG"

# Logging-Konfiguration
StandardOutput=append:/var/log/ytuner_output.log
StandardError=append:/var/log/ytuner_error.log
SyslogIdentifier=ytuner
LogLevelMax=debug

# Erweiterte Neustart-Strategie mit Backoff
Restart=always
RestartSec=10
StartLimitInterval=300
StartLimitBurst=5
RestartPreventExitStatus=2

# Sichere Stopp-Prozedur
TimeoutStopSec=30
KillMode=mixed
KillSignal=SIGTERM
FinalKillSignal=SIGKILL
ExecStop=/bin/bash -c 'echo "$(date): Stopping ytuner gracefully" >> /var/log/ytuner_startup.log'
ExecStop=/bin/kill -SIGTERM $MAINPID
ExecStopPost=/bin/bash -c 'echo "$(date): ytuner stopped" >> /var/log/ytuner_startup.log'

# Ressourcen-Management für Pi Zero 2W
Nice=-5
IOSchedulingClass=1
IOSchedulingPriority=4
CPUSchedulingPolicy=1
CPUSchedulingPriority=50

# Sicherheits- und Isolations-Einstellungen
PrivateDevices=false
PrivateTmp=true
ProtectHome=true
ProtectSystem=strict
ReadWritePaths=/var/log /opt/ytuner /tmp
NoNewPrivileges=false
# Netzwerk-Zugriff erforderlich
PrivateNetwork=false

# Watchdog für Deadlock-Erkennung
WatchdogSec=60
NotifyAccess=exec

[Install]
WantedBy=multi-user.target
Alias=ytuner.service

[landolfi-us]

I don't know whether @TheBossME's last post solved the issue, but as a now-unsupported M$ Windoze user I am interested in implementing a dedicated low-power YTuner server like the Pi Zero 2 W. I am curious whether there is an issue with the Pi Zero 2 W and and/or Bookworm generally or a configuration issue specific to this particular user. @Wakebored, did this get resolved?

[TheBossME]

There is no answer from @Wakebored

@landolfi-us did you know about the SaaS Ip address ? You can use it without the need for a local installation

#108 (comment)

[landolfi-us]

I have been using 1.2.4 on Windows and it has been working great, I just dropped by to see what's new and was disappointed to see Windows will not be supported in the future. I will reread the SaaS documentation, I thought there was some question whether it would support local favorites (per user).

Thanks also for your excellent support!

[coffeegreg]

I have been using 1.2.4 on Windows and it has been working great, I just dropped by to see what's new and was disappointed to see Windows will not be supported in the future.

@landolfi-us
You can try this:
https://github.com/coffeegreg/YTuner/pull/130/files

[landolfi-us]

Thanks! I'm familiar with WSL and have it running on the PC I'm using now. But 1.2.4 has been running great for me since late last year, is there any reason I should upgrade?

Part of the reason for my interest in this Pi Zero 2 W topic is I really like the idea of a $15 computer reliably running YTuner. :)