From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Qos - crash (imq0)
Date: Fri, 23 Mar 2018 19:15:18 +0100 [thread overview]
Message-ID: <0465bd5a-9f21-89b8-8ef0-3b3bfe17d22a@ipfire.org> (raw)
In-Reply-To: <1521824272.556038.22.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
Hi,
Added as #11687 (https://bugzilla.ipfire.org/show_bug.cgi?id=11687).
Best,
Matthias
On 23.03.2018 17:57, Michael Tremer wrote:
> Hello,
>
> this is a bug for a very long time that qosd crashes sometimes. However, nobody
> caught this in the logs and the "Bus Error" doesn't help much either. Basically
> means that memory was inaccessible.
>
> Please create a ticket and if you can, please add more information and let's see
> if we can get to the bottom of this.
>
> However, this only affects the graphs and qosd does not need to run for the QoS
> to be fully operational.
>
> Best,
> -Michael
>
> On Thu, 2018-03-22 at 21:01 +0100, Matthias Fischer wrote:
>> Hi,
>>
>> I'm playing with QoS since a few weeks on a Duo Box with (4 GB RAM), running
>> smoothly.
>>
>> Now it happened twice - once two weeks ago, once yesterday - that QoS crashed
>> with the following kernel messages:
>>
>> ***SNIP***
>> ...
>> 04:50:35 kernel: grsec: Invalid alignment/Bus error occurred at b1928000 in
>> /usr/local/bin/qosd[qosd:3695] uid/euid:0/0 gid/egid:0/0, parent
>> /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0
>> 04:50:35 kernel: grsec: denied resource overstep by requesting 4096 for
>> RLIMIT_CORE against limit 0 for /usr/local/bin/qosd[qosd:3695] uid/euid:0/0
>> gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0
>> ...
>> ***SNAP***
>>
>> System was still running without problems, but 'imq0'-QoS-graph was empty,
>> only showing "-nan"-rates. 'red0'-graph was ok.
>>
>> Can someone explain what happened here and perhaps how to fix this? Shall I
>> open a ticket at Bugzilla?
>>
>> Best,
>> Matthias
>
prev parent reply other threads:[~2018-03-23 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 20:01 Matthias Fischer
2018-03-23 16:57 ` Michael Tremer
2018-03-23 18:15 ` Matthias Fischer [this message]
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=0465bd5a-9f21-89b8-8ef0-3b3bfe17d22a@ipfire.org \
--to=matthias.fischer@ipfire.org \
--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