Page 1 of 1

Startup/shutdown question

PostPosted: Tue Feb 10, 2026 9:07 am
by Scofflaw
Hi,
I installed serviio successfully on my RaspberryPi model 2B.
Data location is on a nfs mounted share on a NAS. Everything works well, even media access over the internet as well as administration using ServiiDroid on my Android based smartphone.

Unfortunately the NAS does not go into sleep mode any more, since > 2 weeks meanwhile. Serviio is set up to refresh the data every 24 hours. I would expect this refresh to take a few minutes, as long as nothing has changed meanwhile. But as I said: NAS is accessed permanently, so that it can't go to sleep mode any more.

To fix this issue I'm thinking about shutdown serviio remotely as long as I don't need it and start it up in same way as soon as I'd like to access my media. It is not so handy to open a Linux console on an Android smartphone and remotely log in to the RaspberryPi from anywhere, so I'm looking for an alternative solution. Ideally I would simply have an icon on the smartphone which would (maybe password protected) startup or shutdown Serviio on the RaspberryPi. Does anyone know how to realize this, or is an alternative solution for the described issue possible?

Re: Startup/shutdown question

PostPosted: Tue Feb 10, 2026 11:53 pm
by atc98092
I could see having a script on a local network computer to stop/start Serviio on a different machine, but accessing from outside the firewall seems to be too much of a security hole for someone to attempt to exploit. It is possible to open a port on the firewall to reach the Serviio console and stop the server (but the base Serviio process remains running, which might not allow the NAS to sleep) but because the console has no security at all (not even a basic password) it's really not a good idea.

Of course, my personal opinion is there's no issue with a NAS running full time. I have all of my PCs set to never sleep, and they use much more power than a NAS. But that's a personal decision for someone to make.

Re: Startup/shutdown question

PostPosted: Thu Feb 19, 2026 7:36 pm
by cmakula
I know this is kind of late, but if you haven't found a solution maybe I can help.

If you use the server only at certain times (for example, not in the middle of the night or not on work days), you can turn serviio on and off completely under Linux (including Raspbian) using a cron job.

Google "cron jobs" or "crontab" for a quick tutorial...

"systemctl start serviio" is the command to start Serviio if it is set up as a service. "/opt/serviio/bin/serviio.sh" is the command if started from a terminal or in the rc.local.
"systemctl stop serviio" is the command to stop Serviio if it is set up as a service. "/opt/serviio/bin/serviio.sh -stop" is the command to stop Serviio if started from a terminal or in the rc.local

If you set up the systemd script in the Ubuntu wiki Serviio will be a service...

Re: Startup/shutdown question

PostPosted: Sun Feb 22, 2026 5:42 am
by rendyorton
Hello, According to my experience, you don’t need to log in manually each time. Since you’re running Serviio on a Raspberry Pi 2B, the easiest solution is to control the service remotely via a small web interface or automation tool.

One practical option is installing a lightweight home automation platform like Home Assistant on your Raspberry Pi. It allows you to create a simple dashboard button to start or stop the Serviio service using system commands. You can secure it with authentication and access it directly from your smartphone browser like an app.

Alternatively, you could set up SSH key-based login and use an Android app such as Tasker or other trusted app to trigger a script remotely with one tap.

Before implementing this, also check Serviio’s library monitoring settings. Disabling automatic refresh and switching to manual scan might already solve the NAS sleep issue without needing frequent shutdowns.

Hope it helps.