Yeah maybe.
I dont want to fiddle too much with your setup as the @devs might have questions first.
But reading out some status shouldnt harm 
What does does below say ?
sudo service pihole-FTL restart
sudo service pihole-FTL status
sudo journalctl --no-pager -u pihole-FTL
file /usr/bin/pihole-FTL
no text
> pi@raspberrypi:~ $ sudo service pihole-FTL status
> ● pihole-FTL.service - LSB: pihole-FTL daemon
> Loaded: loaded (/etc/init.d/pihole-FTL; generated)
> Active: active (exited) since Mon 2019-12-02 15:54:37 EST; 3min 11s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 3438 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SU
>
> Dec 02 15:54:35 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
> Dec 02 15:54:36 raspberrypi pihole-FTL[3438]: Not running
> Dec 02 15:54:36 raspberrypi su[3467]: (to pihole) root on none
> Dec 02 15:54:36 raspberrypi su[3467]: pam_unix(su:session): session opened for u
> Dec 02 15:54:37 raspberrypi pihole-FTL[3438]: Illegal instruction
> Dec 02 15:54:37 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon
.
> pi@raspberrypi:~ $ sudo journalctl --no-pager -u pihole-FTL
> -- Logs begin at Mon 2019-12-02 14:17:02 EST, end at Mon 2019-12-02 15:59:31 EST. --
> Dec 02 15:09:10 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
> Dec 02 15:09:11 raspberrypi pihole-FTL[303]: Not running
> Dec 02 15:09:24 raspberrypi su[459]: (to pihole) root on none
> Dec 02 15:09:24 raspberrypi su[459]: pam_unix(su:session): session opened for user pihole by (uid=0)
> Dec 02 15:09:26 raspberrypi pihole-FTL[303]: Illegal instruction
> Dec 02 15:09:26 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
> Dec 02 15:38:41 raspberrypi systemd[1]: Stopping LSB: pihole-FTL daemon...
> Dec 02 15:38:41 raspberrypi pihole-FTL[1434]: Not running
> Dec 02 15:38:41 raspberrypi systemd[1]: pihole-FTL.service: Succeeded.
> Dec 02 15:38:41 raspberrypi systemd[1]: Stopped LSB: pihole-FTL daemon.
> Dec 02 15:38:41 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
> Dec 02 15:38:41 raspberrypi pihole-FTL[1439]: Not running
> Dec 02 15:38:42 raspberrypi su[1468]: (to pihole) root on none
> Dec 02 15:38:42 raspberrypi su[1468]: pam_unix(su:session): session opened for user pihole by (uid=0)
> Dec 02 15:38:43 raspberrypi pihole-FTL[1439]: Illegal instruction
> Dec 02 15:38:43 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
> Dec 02 15:38:45 raspberrypi systemd[1]: Stopping LSB: pihole-FTL daemon...
> Dec 02 15:38:45 raspberrypi pihole-FTL[1510]: Not running
> Dec 02 15:38:45 raspberrypi systemd[1]: pihole-FTL.service: Succeeded.
> Dec 02 15:38:45 raspberrypi systemd[1]: Stopped LSB: pihole-FTL daemon.
> Dec 02 15:38:45 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
> Dec 02 15:38:45 raspberrypi pihole-FTL[1515]: Not running
> Dec 02 15:38:45 raspberrypi su[1544]: (to pihole) root on none
> Dec 02 15:38:45 raspberrypi su[1544]: pam_unix(su:session): session opened for user pihole by (uid=0)
> Dec 02 15:38:46 raspberrypi pihole-FTL[1515]: Illegal instruction
> Dec 02 15:38:46 raspberrypi su[1544]: pam_unix(su:session): session closed for user pihole
> Dec 02 15:38:46 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
> Dec 02 15:54:35 raspberrypi systemd[1]: Stopping LSB: pihole-FTL daemon...
> Dec 02 15:54:35 raspberrypi pihole-FTL[3433]: Not running
> Dec 02 15:54:35 raspberrypi systemd[1]: pihole-FTL.service: Succeeded.
> Dec 02 15:54:35 raspberrypi systemd[1]: Stopped LSB: pihole-FTL daemon.
> Dec 02 15:54:35 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
> Dec 02 15:54:36 raspberrypi pihole-FTL[3438]: Not running
> Dec 02 15:54:36 raspberrypi su[3467]: (to pihole) root on none
> Dec 02 15:54:36 raspberrypi su[3467]: pam_unix(su:session): session opened for user pihole by (uid=0)
> Dec 02 15:54:37 raspberrypi pihole-FTL[3438]: Illegal instruction
> Dec 02 15:54:37 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
/usr/bin/pihole-FTL: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=7899c81bd4b2c8b052e1c34ebfd3fb59ab57bf97, with debug_info, not stripped
i prepared a new SD with fresh so i can try and work on it without breaking what we have done here. because i feel like you guys made progress on me !
It does. Clean install of Buster on a Zero W and it's there.
for today purpose i'm installing lite, could that be not include in this version ?
Weird.
I found this one bout Illegal instruction:
I dont understand what your asking but yes, Buster lite is preferred choice at the moment.
i meant maybe lite version dont have systemd-timesyncd, but i did a refresh install on other SD card and its there. i also redid the whole process but i downloaded the FTL first before any installation of the pihole. same thing happen ( DND server is not running when i use command pihole status )but right now on this new try the systemd-timesyncd is active and working.
Edit :
I have access now to web pannel. From the pannel, i see FTL offline and DNS service not running and Lost connection to API in the 4 colored square.
the enable button seems to work but after a refresh is doesnt
Please generate a debug log, upload it and post the token here. You will need to reset the nameserver first to upload it.
Is this a fresh debug log? The time does not appear correct if you are in Eastern time zone.
*** [ INITIALIZING ]
[i] 2019-12-02:15:24:05 debug log has been initialized.
Your post three hours ago showed almost this time:
Mon Dec 2 15:10:43 EST 2019
i unplugged and replugged, there is a difference from last time but it should be because i did the command at the time you ask with the nameserver bypass for upload
the timesync fixed it self
timedatectl
pi@raspberrypi:~ $ timedatectl
Local time: Mon 2019-12-02 18:23:21 EST
Universal time: Mon 2019-12-02 23:23:21 UTC
RTC time: n/a
Time zone: America/Montreal (EST, -0500)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
otherwise i didnt changed anything i've been waiting
@jfb
i remade a new one and checked the initializing time. now it fit my clock.
Outputs of the following please:
pihole-FTL dnsmasq-test
sudo service pihole-FTL status
sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:8953 \|:67 \|:80 \|:471'
pihole-FTL dnsmasq-test
> pi@raspberrypi:~ $ pihole-FTL dnsmasq-test
> Illegal instruction
sudo service pihole-FTL status
> pi@raspberrypi:~ $ sudo service pihole-FTL status
> ● pihole-FTL.service - LSB: pihole-FTL daemon
> Loaded: loaded (/etc/init.d/pihole-FTL; generated)
> Active: active (exited) since Mon 2019-12-02 18:16:49 EST; 19min ago
> Docs: man:systemd-sysv-generator(8)
> Process: 3931 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
>
> Dec 02 18:16:47 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
> Dec 02 18:16:47 raspberrypi pihole-FTL[3931]: Not running
> Dec 02 18:16:47 raspberrypi su[3960]: (to pihole) root on none
> Dec 02 18:16:47 raspberrypi su[3960]: pam_unix(su:session): session opened for user pihole by (uid=0)
> Dec 02 18:16:48 raspberrypi pihole-FTL[3931]: Illegal instruction
> Dec 02 18:16:49 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
sudo netstat -nltup | grep 'Proto|:53 |:5053 |:5353 |:8953 |:67 |:80 |:471'
> pi@raspberrypi:~ $ sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:8953 \|:67 \|:80 \|:471'
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 371/lighttpd
> tcp6 0 0 :::80 :::* LISTEN 371/lighttpd
> udp 0 0 0.0.0.0:5353 0.0.0.0:* 260/avahi-daemon: r
> udp6 0 0 :::5353 :::* 260/avahi-daemon: r
Outputs of the following please:
file /usr/bin/pihole-FTL
arch
dpkg --print-architecture
file /usr/bin/pihole-FTL
/usr/bin/pihole-FTL: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=7899c81bd4b2c8b052e1c34ebfd3fb59ab57bf97, with debug_info, not stripped
arch
armv6l
dpkg --print-architecture
armhf
What does readelf -A /usr/bin/pihole-FTL show?
readelf -A /usr/bin/pihole-FTL
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "7-A"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_FP_arch: VFPv3-D16
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_rounding: Needed
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_VFP_args: VFP registers
Tag_CPU_unaligned_access: v6
That's the wrong binary. Are you just running the automated installer or are you manually downloading the FTL binary?
its first, with @jfb, we tryed automatic installer. installer bugged and stop at FTL installation. we then DL manually FTL because reinstalling we now bugged because of the nameserver. after that i finaly had access to pihole command and we started debugging more.
we made a mistake by downlaoding the wrong FTL binary but we fixed it and i try on another blank SD card with the new ftl binary and same thing happen ( right now we are on the first SD card