From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <0465bd5a-9f21-89b8-8ef0-3b3bfe17d22a@ipfire.org>
In-Reply-To: <1521824272.556038.22.camel@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2134781948347547358=="
List-Id: <development.lists.ipfire.org>

--===============2134781948347547358==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Added as #11687 (https://bugzilla.ipfire.org/show_bug.cgi?id=3D11687).

Best,
Matthias

On 23.03.2018 17:57, Michael Tremer wrote:
> Hello,
>=20
> this is a bug for a very long time that qosd crashes sometimes. However, no=
body
> caught this in the logs and the "Bus Error" doesn't help much either. Basic=
ally
> means that memory was inaccessible.
>=20
> 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.
>=20
> However, this only affects the graphs and qosd does not need to run for the=
 QoS
> to be fully operational.
>=20
> Best,
> -Michael
>=20
> On Thu, 2018-03-22 at 21:01 +0100, Matthias Fischer wrote:
>> Hi,
>>=20
>> I'm playing with QoS since a few weeks on a Duo Box with (4 GB RAM), runni=
ng
>> smoothly.
>>=20
>> Now it happened twice - once two weeks ago, once yesterday - that QoS cras=
hed
>> with the following kernel messages:
>>=20
>> ***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***
>>=20
>> System was still running without problems, but 'imq0'-QoS-graph was empty,
>> only showing "-nan"-rates. 'red0'-graph was ok.
>>=20
>> Can someone explain what happened here and perhaps how to fix this? Shall I
>> open a ticket at Bugzilla?
>>=20
>> Best,
>> Matthias
>=20


--===============2134781948347547358==--