Project

General

Profile

Bug #5341

dnsmasq 2.75 exits with signal 11

Added by Nei Ka almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
DNS Forwarder
Target version:
Start date:
10/24/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.2.4
Affected Architecture:

Description

Several users have seen frequent dnsmasq crashes since upgrading to versions with dnsmasq 2.75. dnsmasq 2.76test binary made available to those users has been confirmed to fix it.

For 2.3, we either need to bump to dnsmasq 2.76 once released, or switch to dnsmasq-devel to get the latest 2.76test version.

History

#1 Updated by Chris Buechler almost 4 years ago

  • Category set to DNS Forwarder
  • Status changed from New to Feedback

What does it log in the resolver log?
Anything relevant in the system log?
Did it just happen once, or is recurring?

#2 Updated by Nei Ka almost 4 years ago

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.

#3 Updated by Dave Davis over 3 years ago

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

#4 Updated by Frank Thole over 3 years ago

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.

#5 Updated by Frank Thole over 3 years ago

It happended again yesterday.
Same log entry.

#6 Updated by Henrik John over 3 years ago

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.

#7 Updated by Henrik John over 3 years ago

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

#8 Updated by Chris Buechler over 3 years ago

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.

#9 Updated by Chris Buechler over 3 years ago

  • Subject changed from dnsmasq exits with signal 11 to dnsmasq 2.75 exits with signal 11
  • Description updated (diff)
  • Status changed from Feedback to Confirmed
  • Target version set to 2.3

updated original post with root issue and resolution

#10 Updated by Chris Buechler over 3 years ago

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

#11 Updated by Chris Buechler over 3 years ago

  • Status changed from Confirmed to Feedback

not something I've been able to replicate, we'll have to await feedback from those who encounter it.

#12 Updated by Jim Thompson over 3 years ago

  • Assignee set to Chris Buechler

needs to be found/fixed by 2/15.

#13 Updated by Chris Buechler over 3 years ago

  • Status changed from Feedback to Resolved

this is fixed by the switch to dnsmasq-devel, and that change hasn't caused any regressions. We'll just have to switch it back whenever 2.76 is released.

Also available in: Atom PDF