Expected Behaviour:
The DNS service should run
Actual Behaviour:
[✗] DNS service is not running
/edited by mod: set debug log to hidden
Your debug log didn't return/show any in formation for port 53
What is the output of sudo lsof -i :53 +c 0
and sudo systemctl status pihole-FTL.service
root @ VM-ec4b4811-f7dc-4eae- 8d89-a5c6afdfbb04: ~ # sudo lsof -i: 53 + c 0
sudo: no se puede resolver el host VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04
root @ VM-ec4b4811-f7dc-dc 4eae- 8d89-a5c6afdfbb04: ~ # lsof -i: 53 + c 0
root @ VM-ec4b4811-f7dc-4eae- 8d89-a5c6afdfbb04: ~ # lsof -i: 53 + c 0
root @ VM-ec4b4811-f7dc-4eae- 8d89-a5c6afdfbb04: ~ # lsof -i: 53 + c 0
root @ VM-ec4b4811-f7dc-4eae- 8d89-a5c6afdfbb04: ~ # sudo lsof -i: 53 + c 0
sudo: no se puede resolver el host VM-ec4b4811-f7dc -4eae-8d89- a5c6afdfbb04
root @ VM-ec4b4811-f7dc-4eae- 8d89-a5c6afdfbb04: ~ #
root @ VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04: ~ # systemctl status pihole-FTL.serv ice
● pihole-FTL.service - LSB: daemon pihole-FTL
Cargado: cargado (/etc/init.d/pihole-FTL; generado; preajuste del proveedor: habilitado)
Activo : activo (salido) desde el martes 2020-02-18 04:03:14 CST; Hace 16
horas Docs: man: systemd-sysv-generator (8)
Proceso: 3153 ExecStop = / etc / init.d / pihole- FTL stop (código = salido, estado = 0 /
Proceso SUCC : 3157 ExecStart = / etc / init. d / pihole- FTL start (código = salido, estado = 0 / SU
Tareas: 0 (límite: 6144)
CGroup: /system.slice/pihole-FTL. service
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae -8d89- a5c6afdfbb04 systemd [1]: LSB detenido:
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 systemd [1]: Iniciando LSB
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 pihole-FTL [3157]: No es
el 18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 su [3186]: Exitoso su
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 su [3186]: + ??? raíz: pih
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 su [3186]: pam_unix (su: se
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 pihole -FTL [3157]: dnsmas
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 systemd [1]: LSB iniciado:
líneas 1-17 / 17 (FIN) ... omitiendo ...
● pihole-FTL.service - LSB: demonio pihole-FTL
Cargado: cargado (/etc/init.d/pihole-FTL; generado; preajuste del proveedor: habilitado)
Activo: activo (salido) desde el martes 2020-02-18 04:03:14 CST; Hace 16
horas Documentos: man: systemd-sysv-generator (8)
Proceso: 3153 ExecStop = / etc / init.d / pihole- FTL stop (código = salido, estado = 0 / ÉXITO)
Proceso: 3157 ExecStart = / etc / init .d / pihole- FTL start (código = salido, estado = 0 / ÉXITO)
Tareas: 0 (límite: 6144)
CGroup: /system.slice/pihole-FTL. servicio
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 systemd [1]: LSB detenido: demonio pihole-FTL.
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 systemd [1]: Iniciando LSB: demonio pihole-FTL ...
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 pihole-FTL [3157]: No se ejecuta
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 su [3186]: Su éxito para pihole por root
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 su [3186]: + ??? root: pihole
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 su [3186]: pam_unix (su: sesión): sesión abierta para usuarios por (uid = 0)
18 de febrero 04:03: 14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 pihole-FTL [3157]: dnsmasq: palabra clave repetida ilegal en la línea 34 de /etc/dnsmasq.d/01-pihole.conf. guardar
18 de febrero 04:03:14 VM-ec4b4811-f7dc-4eae-8d89- a5c6afdfbb04 systemd [1]: Iniciado LSB: demonio pihole-FTL.
líneas 1-17 / 17 (FIN)
.0.0: 587 0.0.0.0:* ESCUCHAR 0 15256 1140 / stunnel4
tcp 0 0 0.0.0.0:80 0.0.0.0:* ESCUCHAR 0 22656 2781 / lighttpd
tcp 0 0 0.0.0.0:115 0.0.0.0:* ESCUCHAR 0 15164 1108 / dropbear
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 16540 1281 / sshd
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 15541 1157 / openvpn
tcp 0 0 127.0.0.1:443 127.0 .0.1: 57464 ESTABLECIDO 65534 16662 1157 / openvpn
tcp 0 480 191.96.70.225:115 181.119.112.158:42222 ESTABLECIDO 0 64461 17065 / dropbear
tcp 0 0 127.0.0.1:57464 127.0.0.1:443 ESTABLECIDO 0 16661 1140 / stunnel67
19.2.9 tc. : 587181.9.153.164 : 9262 ESTABLECIDO 0 16558 1140 / stunnel4
tcp6 0 0 ::: 80 ::: * LISTEN 0 22657 2781 / lighttpd
tcp6 0 0 ::: 8080 ::: * LISTEN 0 15458 700 / (squid-1 )
tcp6 0 0 ::: 115 ::: * ESCUCHAR 0 15165 1108 /
dropbear tcp6 0 0 ::: 22
root@VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04:~# sudo lsof -i :53 +c 0
sudo: unable to resolve host VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04
root@VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04:~# lsof -i :53 +c 0
root@VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04:~# lsof -i :53 +c 0
root@VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04:~# lsof -i :53 +c 0
root@VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04:~# sudo lsof -i :53 +c 0
sudo: unable to resolve host VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04
root@VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04:~#
root@VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04:~# systemctl status pihole-FTL.serv ice
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Tue 2020-02-18 04:03:14 CST; 16h ago
Docs: man:systemd-sysv-generator(8)
Process: 3153 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCC
Process: 3157 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SU
Tasks: 0 (limit: 6144)
CGroup: /system.slice/pihole-FTL.service
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 systemd[1]: Stopped LSB:
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 systemd[1]: Starting LSB
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 pihole-FTL[3157]: Not ru
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 su[3186]: Successful su
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 su[3186]: + ??? root:pih
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 su[3186]: pam_unix(su:se
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 pihole-FTL[3157]: dnsmas
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 systemd[1]: Started LSB:
lines 1-17/17 (END)...skipping...
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Tue 2020-02-18 04:03:14 CST; 16h ago
Docs: man:systemd-sysv-generator(8)
Process: 3153 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 3157 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 6144)
CGroup: /system.slice/pihole-FTL.service
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 systemd[1]: Stopped LSB: pihole-FTL daemon.
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 systemd[1]: Starting LSB: pihole-FTL daemon...
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 pihole-FTL[3157]: Not running
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 su[3186]: Successful su for pihole by root
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 su[3186]: + ??? root:pihole
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 su[3186]: pam_unix(su:session): session opened for user pihole by (uid=0)
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 pihole-FTL[3157]: dnsmasq: illegal repeated keyword at line 34 of /etc/dnsmasq.d/01-pihole.conf.save
Feb 18 04:03:14 VM-ec4b4811-f7dc-4eae-8d89-a5c6afdfbb04 systemd[1]: Started LSB: pihole-FTL daemon.
You seem to have a file here that has errors (and shouldn’t be here in the first place).
I’m assuming you wanted to edit that file and something happened as it left a trace behind.
Issue
sudo rm -f /etc/dnsmasq.d/01-pihole.conf.save
And
sudo systemctl restart pihole-FTL.service
If you didn’t poke at the original config file, it should start. Otherwise, you will have to look into the error that prevents piholeFTL from starting.
1 Like
Thank you thank you thank you!!
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.