Service pihole-FTL active (exited)

Help
1

Expected Behaviour:

active (running)

Actual Behaviour:

Although I dont have any problems its kinda weird and I wonder if I have to worry about the exited FTL service.

pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

systemctl status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Tue 2018-03-27 13:19:34 CEST; 6h ago
Docs: man:systemd-sysv-generator(8)
Process: 4876 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 4923 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/pihole-FTL.service

Debug Token:

igwvjdtyq0

//edit: The only issue I'm having is that pihole -up always tells me there is an update for FTL but after updating the update is available again and again and ...

pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] FTL: update available

[i] FTL out of date

[i] FTL Checks...
[✓] Detected x86_64 architecture
[i] Checking for existing FTL binary...
[✓] Downloading and Installing FTL

[i] Web Interface: up to date

[i] FTL version is now at
[✓] Starting pihole-FTL service
[✓] Enabling pihole-FTL service to start on reboot

Thanks

2

Confirmed.

For our developers:

Confirmed.

3

I agree, due to historical reasons, we are using an init.d script. We could look into changing it to systemd, but this may lead to additional problems. @DanSchaper would our lowest supported OS be fine with us switching to a systemd unit file?

1 Like
4

at least for me init.d is also fine but im getting:

/etc/init.d/pihole-FTL status
/etc/init.d/pihole-FTL: line 78: status: command not found

5

Can you make the file and see if it works then?

https://github.com/pi-hole/pi-hole/blob/master/advanced/pihole-FTL.service

6

Directly supported, they pretty much are all on Systemd. But there are a number of heavily used, but user supported installations that run in chroot jails and those tend to be sysvinit still. So we could try to detect the running init system and install the correct scripts, but I can see that getting pretty messy to handle.

1 Like
7

sysvinit still works fine. I'm a fan of systemd but I agree there is a large section of the community that may make things more difficult for.

8

This problem should be resolved by

https://github.com/pi-hole/pi-hole/pull/2112

2 Likes
9

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