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
>