Missing Sonarr Link in Dashboard + All "Red" in Service Control Center

Just installed Quickbox on Debian 8 and ran into an issue when installing Sonarr.

Sonarr itself installed fine, but the link for Sonarr doesn’t show up in the “Main Menu” list of the dashboard. Can anyone tell me how to fix that or add the link for Sonarr manually?

Thanks for Quickbox, such a great script! I’m recommending it to all my friends.

Is sonarr running?

<?php if (processExists("nzbdrone",$username) && file_exists('/install/.sonarr.lock')) { ?>
   <li><a class="grayscale" href="<?php echo "$sonarrURL"; ?>" target="_blank"><img src="img/brands/sonarr.png" class="brand-ico"> <span>Sonarr</span></a></li>
<?php } ?>

Yes, sonarr is running and it’s working. Just missing the link in the dashboard for some reason.

Where do I add that line of code?


The line is located at /srv/rutorrent/home/inc/panel.menu.php You’ll find it at Line #100. However, it shows on the menu if the process is running as the user… so this anomaly doesn’t entirely add up.

Can you also check to see if the lock exists: find /install -name "*.lock"

Yeah, strange. Yup the lock file is there:

find /install -name “*.lock”


ps aux | grep NzbDrone

root 4738 0.0 0.0 13204 984 pts/2 S+ 23:56 0:00 grep NzbDrone
toer 9421 0.0 0.0 26276 1388 ? Ss Aug23 0:00 /usr/bin/SCREEN -f -a -d -m -S nzbdrone mono /opt/NzbDrone/NzbDrone.exe
toer 9422 0.1 1.0 1611708 171504 pts/4 Ssl+ Aug23 5:41 mono /opt/NzbDrone/NzbDrone.exe

I edited the /srv/rutorrent/home/inc/panel.menu.php file and removed the process check portion:

(processExists(“nzbdrone”,$username) &&

Sonarr link pops up now. Strange, wasn’t detecting the process for whatever reason.

What does systemctl status [email protected] show?

systemctl status [email protected]

[email protected] - nzbdrone
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: active (running) since Tue 2016-08-23 22:10:11 CEST; 2 days ago
Main PID: 9421 (screen)
CGroup: /system.slice/system-sonarr.slice/[email protected]
├─9421 /usr/bin/SCREEN -f -a -d -m -S nzbdrone mono /opt/NzbDrone/NzbDrone.exe
└─9422 mono /opt/NzbDrone/NzbDrone.exe

Aug 23 22:10:11 jumbo.clips.com systemd[1]: Started nzbdrone.

Interesting, and you can confirm that the line does in fact exists in your /srv/rutorrent/home/inc/panel.menu.php file?

I am wondering if perhaps this is something to do with caching. Have you tried to do Ctrl+f5 on your keyboard to do a hard refresh?

You may also type sudo service apache2 restart and see if for some reason server cache is the culprit.

I will fire up a Debian machine here momentarily and test this on my end. This is the first report of this being an issue.

Thanks for the help.

Yes, I can confirm that the line does exist in panel.menu.php. I tried restarting apache and hard refresh.

It seems to be an issue with the processExists function, perhaps with Debian 8?

Now that I look at it, there’s an issue with Deluge-Web not showing up in the main menu as well. It also has the processExists check.

<?php if (processExists("deluge-web",$username) && file_exists('/install/.deluge.lock')) { ?>

This may or may not be related.

In the Dashboard, under “Server Control Center”, all services have the “Red” icon, even though the services are indeed running and working. I’m wondering if they are using the “processExists” function as well.

Ah, ok… I just installed this on a Debian 8 machine and there are zero issues.

However, reading this:

Tells me there is something amiss with systemd on your system. What version of QuickBox are you currently running?

I’m using QuickBox v2.4.6

Strange, wonder what went wrong or if it’s user error? It’s a fresh install.

All services are red?

grsec. You’ll need to install the distro kernel – we’ve just recently hammered down the function that will detect this on the installer as of yesterday, so there are a few installs lingering with it.

Could you PM server credentials and I can login and take a look directly? I understand if you don’t want to do this… if not, I will try to troubleshoot this as best I can … but it will be a lot of guess work.

I was thinking that too.

check uname -a @madferret


Linux 3.14.32-xxxx-grs-ipv6-64 #7 SMP Wed Jan 27 18:05:09 CET 2016 x86_64 GNU/Linux

this is the default Debian 8 install from a kimsufi server. Would it be easier just to use a different distro?

Shoot me a PM and I will update your kernel for you.

1 Like

This is actually OVHs default kernel. You need to specify during installation if you wan to use the original kernel. If you don’t feel like giving us your info you can just run this snippet of code from the installer. Throw it in a file on your server and run it as root:

  grsec=$(uname -a | grep -i grs)
  DISTRO=$(lsb_release -is)
  if [[ -n $grsec ]]; then
    echo -e "Your server is currently running with kernel version: $(uname -r)"
    echo -e "Kernels with ${bold}grsec${normal} are not supported"
    echo -ne "${bold}${yellow}Would you like QuickBox to install the distribution kernel?${normal} (Default: ${green}${bold}Y${normal}) "; read input
      case $input in
        [yY] | [yY][Ee][Ss] | "" ) kernel=yes; echo "Your distribution's default kernel will be installed. A reboot will be ${bold}required${normal}."  ;;
        [nN] | [nN][Oo] ) echo "Installer will not continue. Exiting ... "; exit 0 ;;
      *) kernel=yes; echo "Your distribution's default kernel will be installed. A reboot will be ${bold}required${normal}."  ;;
      if [[ $kernel == yes ]]; then
        if [[ $DISTRO == Ubuntu ]]; then
          apt-get install -q -y linux-image-generic >>"${OUTTO}" 2>&1
        elif [[ $DISTRO == Debian ]]; then
          arch=$(uname -m)
          if [[ $arch =~ ("i686"|"i386") ]]; then
            apt-get install -q -y linux-image-686 >>"${OUTTO}" 2>&1
          elif [[ $arch == x86_64 ]]; then
            apt-get install -q -y linux-image-amd64 >>"${OUTTO}" 2>&1
        mv /etc/grub.d/06_OVHkernel /etc/grub.d/25_OVHkernel
        update-grub >>"${OUTTO}" 2>&1
1 Like

Thanks JMSolo and liara, appreciate it. Seems grsec was the culprit. Ran the script to change the kernel and it fixed the problem.


Might make a “If you´re OVH read this first!” post - so future users/visitors know this :slight_smile:

There is. It’s in the Readme posted as the first thing. However, this will not matter so much anymore as the update has been published that will resolve this automagically for OVH kernels.

1 Like

Yeah last I tried it warns you of the GRS Kernel and prompts you to install the distro Kernel instead.