1 |
On 9 May 2014 at 11:15, Michael Orlitzky wrote: |
2 |
|
3 |
> > [Fri May 9 11:00:42 2014] PAX: refcount overflow detected in: syslog-ng:21823, uid/euid: 0/0 |
4 |
|
5 |
this is the key message, the REFCOUNT feature triggered as it detected |
6 |
an overflow somewhere. |
7 |
|
8 |
> > [Fri May 9 11:00:42 2014] CPU: 2 PID: 21823 Comm: syslog-ng Not tainted 3.11.7-hardened-r1 #1 |
9 |
|
10 |
as a sidenote, this is a very old kernel and it's quite possible that |
11 |
it's a false positive that we fixed since. |
12 |
|
13 |
> > [Fri May 9 11:00:42 2014] Call Trace: |
14 |
> > [Fri May 9 11:00:42 2014] [<ffffffff81052750>] ? 0xffffffff81052750 |
15 |
> > [Fri May 9 11:00:42 2014] [<ffffffff81036e10>] ? 0xffffffff81036e10 |
16 |
> > [Fri May 9 11:00:42 2014] [<ffffffff810371e8>] ? 0xffffffff810371e8 |
17 |
> > [Fri May 9 11:00:42 2014] [<ffffffff810449cc>] ? 0xffffffff810449cc |
18 |
> > [Fri May 9 11:00:42 2014] [<ffffffff8100241f>] ? 0xffffffff8100241f |
19 |
> > [Fri May 9 11:00:42 2014] [<ffffffff81002a89>] ? 0xffffffff81002a89 |
20 |
> > [Fri May 9 11:00:42 2014] [<ffffffff8137c212>] ? 0xffffffff8137c212 |
21 |
|
22 |
unfortunately the backtrace is not usable as is due to lack of symbols. |
23 |
if you still have the original vmlinux around (or can reproduce it with |
24 |
all the debug symbols) then i can take a look and perhaps figure out |
25 |
where the refcount overflow was detected (and whether it was a false |
26 |
positive or not). |
27 |
|
28 |
> If it's not hardware (two different machines...), does this look like a |
29 |
> kernel bug? Should I upgrade over the weekend and pray? |
30 |
|
31 |
it's not a hardware issue (at least not directly) but a software one and |
32 |
regardless of it being perhaps a false positive you should be using a newer |
33 |
kernel that we support ;). |