WebUI reports status active but systemctl reports active (exited)

Help Community Help
1

The issue I am facing:
This is very odd, systemctl status pihole-FTL.service reports status as active (exited). But WebUI reports it as active.

Here's status log:

dez 31 12:21:34 Urubu4 systemd[1]: Starting LSB: pihole-FTL daemon...
dez 31 12:21:34 Urubu4 pihole-FTL[81286]: Not running
dez 31 12:21:34 Urubu4 su[81306]: (to pihole) root on none
dez 31 12:21:34 Urubu4 su[81306]: pam_unix(su:session): session opened for user pihole by (uid=0)
dez 31 12:21:34 Urubu4 su[81306]: pam_unix(su:session): session closed for user pihole
dez 31 12:21:34 Urubu4 systemd[1]: Started LSB: pihole-FTL daemon.

I had done some dig tests on the server and on my PC and both report addresses correctly, including blocked domains. Should I be concerned?

log: https://tricorder.pi-hole.net/k2ax5zkhcr

Details about my system:
Ubuntu 20.04, Intel i5

What I have changed since installing Pi-hole:
I installed Tor and it wasn't starting, so I restored Macrium backup from yesterday. I'm pretty sure pihole was starting fine when the backup was created.

2

You only posted part of the log output. Your full log shows that FTL is running:

*** [ DIAGNOSING ]: Pi-hole-FTL full status
   ā— pihole-FTL.service - LSB: pihole-FTL daemon
     Loaded: loaded (/etc/init.d/pihole-FTL; generated)
     Active: active (exited) since Thu 2020-12-31 12:21:34 -03; 9min ago
       Docs: man:systemd-sysv-generator(8)
    Process: 81286 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

dez 31 12:21:34 Urubu4 systemd[1]: Starting LSB: pihole-FTL daemon...
dez 31 12:21:34 Urubu4 pihole-FTL[81286]: Not running
dez 31 12:21:34 Urubu4 su[81306]: (to pihole) root on none
dez 31 12:21:34 Urubu4 su[81306]: pam_unix(su:session): session opened for user pihole by (uid=0)
dez 31 12:21:34 Urubu4 su[81306]: pam_unix(su:session): session closed for user pihole
dez 31 12:21:34 Urubu4 systemd[1]: Started LSB: pihole-FTL daemon.

For comparison, on a different OS with a properly running FTL, here is the output:

sudo service pihole-FTL status
ā— pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated)
   Active: active (exited) since Thu 2020-12-31 08:43:12 CST; 1h 20min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 31954 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Dec 31 08:43:12 Pi-3B-DEV systemd[1]: Starting LSB: pihole-FTL daemon...
Dec 31 08:43:12 Pi-3B-DEV pihole-FTL[31954]: Not running
Dec 31 08:43:12 Pi-3B-DEV su[31972]: (to pihole) root on none
Dec 31 08:43:12 Pi-3B-DEV su[31972]: pam_unix(su:session): session opened for user pihole by (uid=0)
Dec 31 08:43:12 Pi-3B-DEV pihole-FTL[31954]: FTL started!
Dec 31 08:43:12 Pi-3B-DEV su[31972]: pam_unix(su:session): session closed for user pihole
Dec 31 08:43:12 Pi-3B-DEV systemd[1]: Started LSB: pihole-FTL daemon.

You have actually changed more than that, but the changes have no bearing on what you see in the FTL status:

*** [ DIAGNOSING ]: Web version
[i] Web: v5.2.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Remotes: origin	https://github.com/pi-hole/AdminLTE.git (fetch)
             origin	https://github.com/pi-hole/AdminLTE.git (push)
[i] Branch: master
[i] Commit: v5.2.2-0-g780dff0-dirty
[i] Status:  M scripts/pi-hole/js/index.js
[i] Diff: diff --git a/scripts/pi-hole/js/index.js b/scripts/pi-hole/js/index.js
          index fa15471..e6670cb 100644
          --- a/scripts/pi-hole/js/index.js
          +++ b/scripts/pi-hole/js/index.js
          @@ -348,7 +348,7 @@ function updateQueryTypesPie() {
           }
           
           function updateClientsOverTime() {
          -  $.getJSON("api.php?overTimeDataClients&getClientNames", function (data) {
          +  $.getJSON("api.php?overTimeDataClients&getClientNames=50", function (data) {
               if ("FTLnotrunning" in data) {
                 return;
               }
          @@ -507,7 +507,7 @@ function updateForwardDestinationsPie() {
           }
           
           function updateTopClientsChart() {
          -  $.getJSON("api.php?summaryRaw&getQuerySources&topClientsBlocked", function (data) {
          +  $.getJSON("api.php?summaryRaw&getQuerySources=50&topClientsBlocked=50", function (data) {
               if ("FTLnotrunning" in data) {
                 return;
               }
          @@ -623,7 +623,7 @@ function updateTopClientsChart() {
           }
           
           function updateTopLists() {
          -  $.getJSON("api.php?summaryRaw&topItems", function (data) {
          +  $.getJSON("api.php?summaryRaw&topItems=50", function (data) {
               if ("FTLnotrunning" in data) {
                 return;
               }
1 Like
3

tnx for your time :slight_smile:

I was mistaken then by the session closed for user pihole, pihole-FTL[81286]: Not running and active (exited).

Indeed I had changed index.js to increase lists size, but that's on the WebUI and doesn't change anything on FTL or dnsmasq, so I didn't mention it.

4

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.