FTL on XBian Pi

General
21

Not sure whats happening.
Running update-rc.d , which is intended for the sysv init system, used to be enough when I tested this.
I had a bunch of those messages but they were related to a missing proper upstart job so upstart conditions the sysv init.d script to be used for the upstart init system.
I moved my Pi-hole to a dedicated Pi1 with regular Raspbian in the mean time so its a bit hard to test for me currently.

Without the cron job, what were the outputs for the other two (ps -e & netstat) ?
And try 'sudo status pihole-FTL' ?
And did the update-rc.d command create the necessary old style sysv symlinks in below folder ?

ls -al /etc/rc2.d/

Ohw and upstart creates logs in the folder '/var/log/upstart/'.
you can check if pihole-FTL logs are created in that folder and you can view them with the 'zcat' command.

22

So, I removed the entry from my crontab where I started the service on boot and rebooted my xbian to check the output of the commands you asking for.
The good news are that now when I visit the admin panel of pihole it works and the status is Active.
The strange thing is the output of the above commands:

  • $ ps -e | grep 'PID|pihole-FTL'
    PID TTY TIME CMD
    2525 ? 00:00:04 pihole-FTL

  • $ sudo netstat -nltp | grep 'Prot|pihole-FTL'
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

  • $ sudo service pihole-FTL status
    status: Unknown job: pihole-FTL

  • $ sudo update-rc.d pihole-FTL defaults
    initctl: Unknown job: K01nfs-commonThe script you are attempting to invoke h - Pastebin.com

  • $ ls -al /etc/rc2.d/
    -rw-r--r-- 1 root root 677 Feb 12 2017 README
    lrwxrwxrwx 1 root root 26 Oct 20 16:01 S01console-setup.sh -> ../init.d/console-setup.sh
    lrwxrwxrwx 1 root root 13 Oct 20 16:02 S02atd -> ../init.d/atd
    lrwxrwxrwx 1 root root 19 Oct 20 16:10 S02bluetooth -> ../init.d/bluetooth
    lrwxrwxrwx 1 root root 19 Oct 20 16:01 S02cgmanager -> ../init.d/cgmanager
    lrwxrwxrwx 1 root root 14 Oct 20 16:01 S02dbus -> ../init.d/dbus
    lrwxrwxrwx 1 root root 16 Feb 21 13:12 S02dhcpcd -> ../init.d/dhcpcd
    lrwxrwxrwx 1 root root 17 Feb 21 14:01 S02dnsmasq -> ../init.d/dnsmasq
    lrwxrwxrwx 1 root root 18 Feb 21 14:00 S02lighttpd -> ../init.d/lighttpd
    lrwxrwxrwx 1 root root 14 Oct 20 16:01 S02nmbd -> ../init.d/nmbd
    lrwxrwxrwx 1 root root 20 Feb 21 15:20 S02pihole-FTL -> ../init.d/pihole-FTL
    lrwxrwxrwx 1 root root 21 Oct 20 16:01 S02samba-ad-dc -> ../init.d/samba-ad-dc
    lrwxrwxrwx 1 root root 29 Oct 25 19:33 S02transmission-daemon -> ../init.d/transmission-daemon
    lrwxrwxrwx 1 root root 29 Oct 20 16:02 S02unattended-upgrades -> ../init.d/unattended-upgrades
    lrwxrwxrwx 1 root root 17 Oct 20 16:01 S03cgproxy -> ../init.d/cgproxy
    lrwxrwxrwx 1 root root 14 Oct 20 16:01 S03smbd -> ../init.d/smbd
    lrwxrwxrwx 1 root root 18 Oct 20 16:01 S04rc.local -> ../init.d/rc.local

Oh, and there is no logfile for pihole in folder /var/log/upstart/

23

Thats indeed strange if admin page and ps -e says its running.
You could check without the grep ?

sudo netstat -nltp

The service command is just a wrapper for upstarts initctl command:

man service

man initctl

Try upstarts own tool (is symlink to initctl) :

sudo status pihole-FTL

Those messages are all warnings and I dont see any errors.

Symlink looks good.

Yeah maybe only true upstart jobs get logged ... not sure.
At least you got FTL running now without the extra CRON dependency.

1 Like
24

It gives me
status: Unknown job: pihole-FTL

Gives me the below, which is good cause piholeFTL is indeed running

tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 4526/pihole-FTL

1 Like