Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start dnsmasq after reboot #740

Open
4 tasks done
DavideVito opened this issue Dec 28, 2020 · 1 comment
Open
4 tasks done

Cannot start dnsmasq after reboot #740

DavideVito opened this issue Dec 28, 2020 · 1 comment

Comments

@DavideVito
Copy link

DavideVito commented Dec 28, 2020

  • This is a bug report
  • I searched existing issues before opening this one
  • I checked the FAQ before creating this issue
  • I have read and understand the issue reporting guidelines

Describe the bug
I rebooted the raspberry, then my phone cannot connect to the wifi, checking in the web-gui the dnsmasq service is stopped, and I cannot restart it.

Doing sudo service dnsmasq status I get:
illegal repeated keyword at line 6 of /etc/dnsmasq.d/090_raspap.conf

and in the these are the contents of: /etc/dnsmasq.d/090_raspap.conf

interface=wlan0
dhcp-range=10.3.141.50,10.3.141.255,255.255.255.0,12h
log-dhcp
log-queries
dhcp-option=6,1.1.1.1,8.8.8.8
log-facility=/tmp/dnsmasq.log
conf-dir=/etc/dnsmasq.d

Your environment

  • Raspberry Pi hardware Pi 3 Model B+
  • Raspbian version (Raspian)
  • Followed the project prerequisites? Yes
  • Checked the project FAQ? Yes
  • RaspAP Quick Install.
  • Using default configuration? No, I've changed the php root folder.
  • Simultaneous AP and managed mode? (Y/N)
  • Onboard wireless chipset.
  • Other software or services running with RaspAP? Docker and PiHole (Stopped).

Steps to reproduce
I've just rebooted the raspberry using the web-gui

Expected behavior
To reboot and just working.

Actual behavior
Cannot start dnsmasq

Screenshots
image

@billz
Copy link
Member

billz commented Dec 29, 2020

This is a consequence of installing Pi-Hole alongside RaspAP. The error thrown by dnsmasq is your answer: the log-facility option is used in another config. Check the files in /etc/dnsmasq.d/. It does not matter if Pi-Hole is stopped; a conflicting directive like this will prevent dnsmasq from starting.

The FAQ offers numerous solutions to this.

@RaspAP RaspAP locked as resolved and limited conversation to collaborators Dec 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants