Cannot install error, lighttpd might cause problems

[aerlux]

Expected Behaviour:
Hi there! I am trying to install pi-hole on a debian server but cant seem to get it going continusly just ending mid install.

Actual Behaviour:
not installing or run

Debug Token:
9uvzbqdj1k

[jfb]

Let's reset the nameserver for the Pi and then repair:

sudo nano /etc/resolv.conf

edit nameserver 127.0.0.1 to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run pihole -r and select repair.

[aerlux]

did not work
Here is the config file:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)

#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver fe80::ea94:f6ff:fee2:e7fc%enp3s0
nameserver 9.9.9.9
search lan

[jfb]

What did not work? Were you not able to complete a repair? If so, what was the output of the repair command?

[aerlux]

Ends with this

[✓] man pages installed and database updated
[i] Testing if systemd-resolved is enabled
[i] Systemd-resolved does not need to be restarted
[i] Restarting lighttpd service...

[jfb]

What are the outputs of the following:

sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'

sudo service lighttpd status

[aerlux]

> Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
> tcp        0      0 127.0.0.1:4711          0.0.0.0:*               LISTEN      26990/pihole-FTL    
> tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      26990/pihole-FTL    
> tcp6       0      0 ::1:4711                :::*                    LISTEN      26990/pihole-FTL    
> tcp6       0      0 :::53                   :::*                    LISTEN      26990/pihole-FTL    
> udp        0      0 0.0.0.0:53              0.0.0.0:*                           26990/pihole-FTL    
> udp        0      0 127.0.0.53:53           0.0.0.0:*                           25737/systemd-resol 
> udp6       0      0 :::53                   :::*                                26990/pihole-FTL   

> ● lighttpd.service - Lighttpd Daemon
>    Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
>    Active: failed (Result: exit-code) since Tue 2019-02-12 18:11:43 CET; 7min ago
>   Process: 2798 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)
>  Main PID: 12738 (code=exited, status=0/SUCCESS)
> 
> Feb 12 18:11:42 Oklahoma systemd[1]: lighttpd.service: Control process exited, code=exited status=255
> Feb 12 18:11:42 Oklahoma systemd[1]: Failed to start Lighttpd Daemon.
> Feb 12 18:11:42 Oklahoma systemd[1]: lighttpd.service: Unit entered failed state.
> Feb 12 18:11:42 Oklahoma systemd[1]: lighttpd.service: Failed with result 'exit-code'.
> Feb 12 18:11:43 Oklahoma systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
> Feb 12 18:11:43 Oklahoma systemd[1]: Stopped Lighttpd Daemon.
> Feb 12 18:11:43 Oklahoma systemd[1]: lighttpd.service: Start request repeated too quickly.
> Feb 12 18:11:43 Oklahoma systemd[1]: Failed to start Lighttpd Daemon.
> Feb 12 18:11:43 Oklahoma systemd[1]: lighttpd.service: Unit entered failed state.
> Feb 12 18:11:43 Oklahoma systemd[1]: lighttpd.service: Failed with result 'exit-code'.

[jfb]

This thread may have a solution to your problem:

Pi-hole no web interface access and lighttpd.service failed to start

Please follow the below template, it will help us to help you! Hi, thanks for being part of this great project. I would need help as my friend google can not help me anymore Expected Behaviour: Access to web interface Actual Behaviour: after a power outage the web interface is not accessible anymore. lighttpd refuses to start, blocking and dns over http works Debug Token: k999znraw2 what I did: pihole -r didn't help ~$ systemctl status lighttpd.service ● lighttpd.service - Lighttpd D…

[aerlux]

Did not work even with chown 777

> ● lighttpd.service - Lighttpd Daemon
>    Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
>    Active: failed (Result: exit-code) since Tue 2019-02-12 18:54:25 CET; 380ms ago
>   Process: 5220 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)
>  Main PID: 12738 (code=exited, status=0/SUCCESS)
> 
> Feb 12 18:54:25 Oklahoma systemd[1]: lighttpd.service: Unit entered failed state.
> Feb 12 18:54:25 Oklahoma systemd[1]: lighttpd.service: Failed with result 'exit-code'.
> Feb 12 18:54:25 Oklahoma systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
> Feb 12 18:54:25 Oklahoma systemd[1]: Stopped Lighttpd Daemon.
> Feb 12 18:54:25 Oklahoma systemd[1]: lighttpd.service: Start request repeated too quickly.
> Feb 12 18:54:25 Oklahoma systemd[1]: Failed to start Lighttpd Daemon.
> Feb 12 18:54:25 Oklahoma systemd[1]: lighttpd.service: Unit entered failed state.
> Feb 12 18:54:25 Oklahoma systemd[1]: lighttpd.service: Failed with result 'exit-code'.

[jfb]

What is the output of journalctl -u lighttpd -l

[aerlux]

This is it

> -- Logs begin at Tue 2019-02-12 15:32:21 CET, end at Wed 2019-02-13 00:28:07 CET. --
> Feb 12 17:30:37 Oklahoma systemd[1]: Starting Lighttpd Daemon...
> Feb 12 17:30:37 Oklahoma systemd[1]: Started Lighttpd Daemon.
> Feb 12 17:30:59 Oklahoma systemd[1]: Stopping Lighttpd Daemon...
> Feb 12 17:30:59 Oklahoma systemd[1]: Stopped Lighttpd Daemon.
> Feb 12 17:30:59 Oklahoma systemd[1]: Starting Lighttpd Daemon...
> Feb 12 17:30:59 Oklahoma lighttpd[19640]: /bin/sh: 1: /usr/share/lighttpd/create-mime.assign.pl: not found
> Feb 12 17:30:59 Oklahoma lighttpd[19640]: 2019-02-12 17:30:59: (configfile.c.1461) command "/usr/share/lighttpd/create-mime.assign.pl" exited no
> Feb 12 17:30:59 Oklahoma lighttpd[19640]: 2019-02-12 17:30:59: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 53 pos: 14 parser f
> Feb 12 17:30:59 Oklahoma systemd[1]: lighttpd.service: Control process exited, code=exited status=255
> Feb 12 17:30:59 Oklahoma systemd[1]: Failed to start Lighttpd Daemon.
> Feb 12 17:30:59 Oklahoma systemd[1]: lighttpd.service: Unit entered failed state.
> Feb 12 17:30:59 Oklahoma systemd[1]: lighttpd.service: Failed with result 'exit-code'.
> Feb 12 17:31:00 Oklahoma systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
> Feb 12 17:31:00 Oklahoma systemd[1]: Stopped Lighttpd Daemon.
> Feb 12 17:31:00 Oklahoma systemd[1]: Starting Lighttpd Daemon...
> Feb 12 17:31:00 Oklahoma lighttpd[19648]: /bin/sh: 1: /usr/share/lighttpd/create-mime.assign.pl: not found
> Feb 12 17:31:00 Oklahoma lighttpd[19648]: 2019-02-12 17:31:00: (configfile.c.1461) command "/usr/share/lighttpd/create-mime.assign.pl" exited no
> Feb 12 17:31:00 Oklahoma lighttpd[19648]: 2019-02-12 17:31:00: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 53 pos: 14 parser f
> Feb 12 17:31:00 Oklahoma systemd[1]: lighttpd.service: Control process exited, code=exited status=255
> Feb 12 17:31:00 Oklahoma systemd[1]: Failed to start Lighttpd Daemon.
> Feb 12 17:31:00 Oklahoma systemd[1]: lighttpd.service: Unit entered failed state.
> Feb 12 17:31:00 Oklahoma systemd[1]: lighttpd.service: Failed with result 'exit-code'.

[Mcat12]

Have you modified /etc/lighttpd/lighttpd.conf? Also, the output you shared cuts off some lines, please share the full lines.