public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: Possible Issue
Date: Tue, 01 Dec 2015 22:40:35 -0600	[thread overview]
Message-ID: <565E7643.8030808@dailydata.net> (raw)
In-Reply-To: <1449009593.31655.35.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2522 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I tried to reproduce it, but was not successful. I saw no correlation
between the two times it happened. If it breaks again, I'll see if I
can create a conditions list, however.

My office firewall is set to always run the testing tree, so as soon
as 96 goes into beta, it will automatically upgrade (I keep a very,
very old router around in case I completely mess it up with the upgrade!
).

I really hate giving a report that says "this broke." I know you need
more information than that.

Rod

On 12/01/2015 04:39 PM, Michael Tremer wrote:
> Hi,
> 
> yes, dnsmasq has some stability issues. This has become way better 
> since a few releases, but it is still not at the level where it
> should be.
> 
> Have you any information about how to reproduce the crash? I 
> experienced them for a time, but they were all random and I could
> not debug this a lot.
> 
> I just merged a patch with some fixes. Maybe it has been fixed in 
> there. Please test Core Update 96 as soon as it becomes available
> for testing.
> 
> Best, -Michael
> 
> On Fri, 2015-11-27 at 16:32 -0600, R. W. Rodolico wrote:
>> I am running 95 and have had two times in the past couple of
>> weeks where dnsmasq has died on me. I have been able to fix the
>> problem by starting it up again and it works just fine.
>> 
>> The error appears to be associated with these log entries:
>> 
>> Nov 24 13:38:26 dd-router kernel: dnsmasq[2789]: segfault at 0
>> ip 0805daaf sp 5af771e0 error 4 in dnsmasq[8048000+32000] Nov 24
>> 13:38:26 dd-router kernel: grsec: Segmentation fault occurred at 
>> (nil) in /usr/sbin/dnsmasq[dnsmasq:2789] uid/euid:99/99 
>> gid/egid:40/40, parent /sbin/init[init:1] uid/euid:0/0
>> gid/egid:0/0 Nov 24 13:38:26 dd-router kernel: grsec: bruteforce
>> prevention initiated due to crash of /usr/sbin/dnsmasq against
>> uid 99, banning suid/sgid execs for 15 minutes.  Please
>> investigate the crash report for /usr/sbin/dnsmasq[dnsmasq:2789]
>> uid/euid:99/99 gid/egid:40/40, parent /sbin/init[init:1]
>> uid/euid:0/0 gid/egid:0/0
>> 
>> this is a fresh install of IPFire 94, then upgrade to 95. Please
>> let me know what I can do to further troubleshoot this.
>> 
>> Rod

- -- 
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlZedkMACgkQuVY3UpYMlTQx5ACfXg3jKXY5uFssp5ehner2pyh6
SdYAn31mLQVfCjPNiUib9f4f74hcN3fs
=D74o
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-12-02  4:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 22:32 R. W. Rodolico
2015-12-01 22:39 ` Michael Tremer
2015-12-02  4:40   ` R. W. Rodolico [this message]
2015-12-05  4:19     ` R. W. Rodolico
2015-12-05 11:06       ` Matthias Fischer
2015-12-05 11:15       ` Matthias Fischer
2015-12-10 17:41         ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=565E7643.8030808@dailydata.net \
    --to=rodo@dailydata.net \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox