Issue with Dnsamasq when adding a static lease



  • Hi All

    I am getting this error when adding a new static lease

    dhcpleases		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
    

    Running version 2.3.2

    the pid file does exist and contains a process id

    -rw-r--r--  1 root  wheel       5 Aug 27 16:31 dnsmasq.pid
    

    The new static lease is not recognised meaning the new device does not get an IP (as only listed devices get IPs)

    Any help appreciated

    Duncan


  • Rebel Alliance Global Moderator

    @dcolhoun said in Issue with Dnsamasq when adding a static lease:

    2.3.2

    Upgrade to current.



  • I have upgraded to current and the issue persists. Any other suggestions?



  • Sure.

    Start by detailing your setup.
    pfSEnse, by default, uses the Resolver (unbound). Not the Forwarder (dnsmasq).
    What are you using ?

    When you add a static lease, are you doing this here : Services => DHCP Server => LAN

    Sorry for the silly questions, I'm trying to do what you do.
    I just witched to the Forwarder, DNS, checked that it worked = resolved, and added a static lease. Didn't saw any errors.
    So, what else did you take from default ? ;)



  • Hi

    Thanks for the reply.

    Current Base System 2.4.3_1

    Using Dnsmasq as the forwarder - not using a DNS resolver

    To add a static lease Service -> DHCP server -> LAN

    Add all necessary details and then apply changes. When I look at system logs I get errors mentioned above

    Since my upgrade to current release there are a few more messages

    Sep 4 10:49:22	dhcpleases		kqueue error: unkown
    Sep 4 10:49:21	check_reload_status		Reloading filter
    Sep 4 10:49:20	dhcpleases		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
    Sep 4 10:49:20	dhcpleases		kqueue error: unkown
    Sep 4 10:49:20	dhcpleases		Could not deliver signal HUP to process because its pidfile (/var/run/dnsmasq.pid) does not exist, No such process.
    Sep 4 10:49:20	dhcpleases		/etc/hosts changed size from original!
    

    Thanks



  • Did you accessed the console and checked :
    /var/run/dnsmasq.pid does not exist ?

    Also : while you're in console mode, run a
    ps ax | grep "dnsmasq"
    (or whatever the process name of dnsmasq is.

    It should run, because : if not, no more DNS ....

    Btw : why the Forwarder ?
    And, because it takes 1 minute to activate the Resolver : less problems / more problems ?



  • @dcolhoun said in Issue with Dnsamasq when adding a static lease:

    /var/run/dnsmasq.pid

    Yes file exists and process id matches Dnsmasq

    [2.4.3-RELEASE][admin@gw.genepool.private]/var/run: cat dnsmasq.pid 
    94419
    [2.4.3-RELEASE][admin@gw.genepool.private]/var/run: ps ax|grep dnsmasq
    94419  -  S        0:25.69 /usr/local/sbin/dnsmasq --all-servers -C /dev/null -
    16940  1  S+       0:00.00 grep dnsmasq
    
    

    We have a corporate DNS server, so don't wish to resolve addresses (or block any) just forward them on.

    This setup has been running for some time like this, however errors are new.



  • The issue existed .... a long time ago (Google and forum.netgate.com are my sources).
    You restarted pfSense after upgrading ?

    I'm using the Forwarder right now and leave it there for a moment. Didn't see any "pid" errors ... yet.

    Btw : the error (see your first post) might be correct : check with the logs Status => System Logs => System => DNS Resolver if dnsmasq wasn't restarting at that very moment.



  • Now when I restart dnsmasq I get

    /services_dhcp_edit.php: The command '/usr/sbin/arp -d '192.168.170.239'' returned exit code '1', the output was 'arp: writing to routing socket: No such file or directory'
    
    

    I actually opened a separate ticket about this - but obviously they are connected