pfSense

There was nothing remarkable in the resolver log. The line

kernel: pid 28880 (dnsmasq), uid 65534: exited on signal 11

Was the only apparently relevant entry in the system log.

It reoccurred. dnsmasq would exit almost immediately after starting normally. The problem survived a reboot.

I've had to switch to unbound for now, but it's not a long term solution. This is our main router so I will have to wait for a quite period to try again. But I will capture more log output.

Same thing happened to my pfS 2.2.4 box today.
The only log entry I found was:
kernel: pid 6932 (dnsmasq), uid 65534: exited on signal 11

I started dnsmasq from Status/Services and it has not dropped out again......yet

What does it log in the resolver log?

Nothing found in resolver log

Anything relevant in the system log?

kernel: pid 6932 (dnsmasq), uid 65534: exited on signal 11

Did it just happen once, or is recurring?

once

This happend to me 2 times the last few days.

Both times, the log entry at my side was:
kernel: pid 42153 (dnsmasq), uid 65534: exited on signal 11

Only the pid was different (of course).

Nothing special in the resolver log, the last log message there is 3 minutes before.

It happended again yesterday.
Same log entry.

Just chiming in to report the same problem overhere.

Dec 17 23:00:38 pfsense kernel: pid 27577 (dnsmasq), uid 65534: exited on signal 11

Dec 20 17:29:55 pfsense kernel: pid 28499 (dnsmasq), uid 65534: exited on signal 11

Jan 6 22:59:59 pfsense kernel: pid 25319 (dnsmasq), uid 65534: exited on signal 11

I rebooted the box the first 2 times, and got back to normal after that, but the third time I noticed the dnsmasq service being down, and started that without a problem. It was however done about 7 hours after the crash.

I forgot to mention that I'm updating my pfsense box within a few days of new releases, running only the stable versions.

I think this may be attributable to a regression in dnsmasq 2.75. There is a recent dnsmasq 2.76test build available that one person has reported to solve the problem they were seeing. Info in this post:
https://forum.pfsense.org/index.php?topic=103714.msg580900#msg580900

If anyone else can try that and report back, additional feedback would be appreciated.

I switched 2.3 to dnsmasq-devel for now to get more testing on 2.76test.