I've got the same problem now die after 2h, before version v2.7.3 it never crashed for me.
[2017-05-19 17:10:12.590] FATAL: FTL received SIGTERM from PID/UID 28982/0, scheduled to exit gracefully
[2017-05-19 17:10:12.590] Shutting down...
[2017-05-19 17:10:12.591] ########## FTL terminated! ##########
Your debug token is : 2txdhtebin
Below one means the process ID that killed FTL is/was 28982
PID=28982
Below one means it was initiated by user id 0 which happens to be the root user:
UID=0
So who killed FTL ?
Lets ask Agatha Christie:
ps -e | grep 28982
I did a sudo service pihole-FTL restart
I'm gonna do the ps -e | grep next time it die.
Yeah good one.
Processes come and go so need to be quick.
And if its an intermediate process that is doing the killing, ps -e is not going to show it might not show it.
It could very well have been service itself (root UID since you used sudo service ...). Since it will immediately be over, there is like zero chance to detect it.
So make note of the pihole-FTL process ID before it crashes ?
ps -e > ~/ps-e-snap
EDIT: naah.
Your right, if its service.