The Raspberry Pi is probably the best solution. The web is full of users looking for advice on the best cheap device to use as a Plex media server in hotels and offices. However, the Raspberry Pi also has some massive upsides, the most notable of which is portability. That's well short of Plex's recommended requirements for the Media Server app: an Intel Core i3 processor and at least 2GB of RAM. The Raspberry Pi 3 uses a 1.2GHz ARM Cortex-A53 CPU and 1GB of RAM. The Raspberry Pi 2 has a 900 MHz quad-core Cortex-A7 CPU along with 1GB of RAM. The most notable downside is the lack of CPU power. I've read that there is a possibility that the crontab entry may not persist through a reboot, but I've not tested that Pi devices have some very unique advantages and disadvantages when you're using them with the Plex Media Server app. */5 * * * * /share/homes/admin/PMS_cron.sh > /share/homes/admin/PMS_cron_output.txt

I may eventually just remove the logging output, but for now is good for at least the initial time I'm monitoring it. That runs the above script every 5 minutes, and logs the output to a file called PMS_cron_output.txt. I then added this crontab entry using sudo vim /etc/config/crontab Notice_log_tool -a 'Plex Server restarted by cron' -t 7 PID_FILE='$')Įcho -e '$(date) Stopping our awesome Plex Media Server'Įcho -e '$(date) Restarting our awesome Plex Media Server' QPKG_SHELL=$(getcfg -f $CONF $QPKG_NAME Shell) QPKG_DIR=$(getcfg -f $CONF $QPKG_NAME Install_path) # Grab Plex Media Server install directory, regardless of disk layout. # Name of Plex Media Server install directory. # Plex Media Server kill and restart script # There is also a command at the bottom that causes an alert to show in the QTS gui. I created a script called PMS_cron.sh that runs every 5 minutes that checks for the pid (process ID) and if it's not found, restarts the service.

Restart plex media server in qnap