=== jrib is now known as Guest10239
[06:48] <Donkersgoed> hi
[06:48] <Donkersgoed> I have a kernel panic using ipvs on the latest kernel
[06:48] <Donkersgoed> is this the right place to ask for support?
[07:04] <jibel> Donkersgoed, people on #ubuntu-kernel will know more about kernel panics
[07:04] <Donkersgoed> nice, thanks
[07:05] <jibel> Donkersgoed, also https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies contains useful information on reporting kernel bugs
[07:06] <Donkersgoed> thank you!
=== Nigel_ is now known as G
=== Guest10239 is now known as jrib
[15:45] <hggdh> TheLordOfTime: what's about crash bugs?
=== om26er is now known as om26er|food
=== om26er|food is now known as om27er
=== om27er is now known as om26er
[16:59] <s9iper1> :D
[17:00] <TheLordOfTime> hggdh: nevermind, figured out
[17:00] <TheLordOfTime> hggdh: there was an nginx crash bug and the retracer wasn't clearly displaying the stacktrace, turns out it was my internet breaking that wasn't displauing the stacktrace
[17:58] <hggdh> TheLordOfTime: ah, cool
[17:59] <TheLordOfTime> hggdh: of course the stacktrace doesn't help much :P
[17:59] <hggdh> LOL. Incomplete resolution?
[17:59] <TheLordOfTime> and they weren't actually using the repository's software when the error triggered...
[17:59] <TheLordOfTime> hggdh: haven't touched it yet
[17:59] <TheLordOfTime> too busy yelling at idiots on twitter
[18:00] <hggdh> well, difficult to solve on software built elsewhere...
[18:00] <TheLordOfTime> well... it's in a PPA
[18:00] <TheLordOfTime> it's nginx :/
[18:00] <hggdh> ugh. At least do they have the .dbg packages?
[18:00] <TheLordOfTime> nope
[18:00] <TheLordOfTime> which therein lies a problem
[18:00] <TheLordOfTime> https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1238307  <--
[18:00] <ubot2> TheLordOfTime: Error: launchpad bug 1238307 not found
[18:00] <TheLordOfTime> if you care
[18:00] <TheLordOfTime> yes, we know, ubot2, it's a bloody crash bug, be quiet
[18:01]  * TheLordOfTime slaps ubot2 with a rotting trout
[18:01] <TheLordOfTime> hggdh: my problem is that they upgraded to the nginx mainline in the PPA...
[18:01] <TheLordOfTime> then downgraded
[18:01] <TheLordOfTime> and then therein lies the crash
[18:01] <TheLordOfTime> no clue how to handle it, this is the first nginx crash bug i've seen that wasn't related to a CVE
[18:04] <hggdh> TheLordOfTime: it did not happen while in with the PPA code?
[18:04] <TheLordOfTime> oh, and it's 13.10 so... i don't exactly trust that to be entirely "stable"
[18:04] <TheLordOfTime> hggdh: read comment 6
[18:04] <TheLordOfTime> it seems to be triggered because of the PPA, but...
[18:04] <TheLordOfTime> IDK
[18:05] <TheLordOfTime> looks like it happens in both the PPA and Saucy
[18:05] <TheLordOfTime> but they said it was working in Saucy before, so...
[18:05] <TheLordOfTime> maybe their upgrading to 1.5.6 introduced rogue stuff, but, if that's the case they should copy out their configs, purge the packages related to nginx completely, remove the ppa, reinstall nginx from repos only
[18:06]  * TheLordOfTime isn't sure what ppa-purge does nor does he knwo if that introduced the issue
[18:07] <hggdh> it depends if the PPA forces updates of other packages. The ./debian/control should list it
[18:07] <hggdh> but I do not see a segv indicated in the trace; and the trace has two more frames over the one that is (theoretically) the one that segv-ed)
[18:09] <hggdh> ah, libc
[18:11] <TheLordOfTime> see, you at least know how to interpret crash bugs better than I :/
[18:12] <hggdh> heh
[18:12] <TheLordOfTime> i don't like reading the stacktrace, i never have
[18:12] <TheLordOfTime> even when my own programs crash :/
[18:13] <hggdh> well, the stacktrace is fully resolved, so I am guessing thissegv happened with the official packages
[18:15] <TheLordOfTime> i think so
[18:15] <TheLordOfTime> the key operative buzzword is the word "downgraded"
[18:15] <TheLordOfTime> which means they returned to Saucy's stuff
[18:15] <hggdh> TheLordOfTime: now it is (mostly) backtracking -- ngx_conf_file.c @305 is probably calling on strcmp. YOu would need to find out what was being compared, and find out why one of the addresses was invalid
[18:15] <hggdh> :-)
[18:16] <TheLordOfTime> urgh
[18:16] <TheLordOfTime> i've got better things to do
[18:16] <TheLordOfTime> :P
[18:16] <hggdh> :-)
[18:16] <hggdh> and I never dealt with ngix...
[18:16] <TheLordOfTime> like... SRU verifications for the nginx package in precise...
[18:17] <TheLordOfTime> and SRU prep for nginx 1.1.19-1ubuntu0.5
[18:17] <TheLordOfTime> for precise
[18:17] <hggdh> yeah, these are more important
[18:18] <TheLordOfTime> well... maybe I shouldn't SRU verify something I personally prepared... but meh
[18:19] <TheLordOfTime> i need that to go through (it fixes a configuration purging problem!) so that i can get the other bug SRU ready to enable the naxsi_stub_status module in nginx
[18:19] <TheLordOfTime> (very tiny fix in the package, just add a line to the rules file)
[18:21] <TheLordOfTime> then after that I have to figure out how to gain the courage to tell this girl who's a friend of mine that I like her... and then actually follow through with that... (personal issues take priority over all else!)
[18:21] <TheLordOfTime> anyways, i digress, thanks for the assistance, hggdh
[18:26] <hggdh> yw