IRC log for #asterisk-bugs on 20071015

02:05.53*** join/#asterisk-bugs jmls (n=jmls@62.49.235.130)
03:10.49*** join/#asterisk-bugs Corydon76-home (i=silver@pdpc/supporter/bronze/Corydon76-home)
03:10.49*** mode/#asterisk-bugs [+o Corydon76-home] by ChanServ
03:11.37*** join/#asterisk-bugs Corydon76-dig (n=tilghman@pdpc/supporter/bronze/Corydon76-home)
03:11.37*** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ
03:38.11*** join/#asterisk-bugs fakhir (n=fakhir@unaffiliated/fakhir)
06:50.31*** join/#asterisk-bugs Corydon76-dig (i=yellow@pdpc/supporter/bronze/Corydon76-home)
06:50.31*** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ
06:50.54*** join/#asterisk-bugs Corydon76-home (n=tilghman@pdpc/supporter/bronze/Corydon76-home)
06:50.54*** mode/#asterisk-bugs [+o Corydon76-home] by ChanServ
10:53.01*** join/#asterisk-bugs caio1982 (i=caio1982@CAcert-br/caio1982)
11:58.40*** join/#asterisk-bugs zerohalo (n=zeroHalo@pool-72-70-79-233.bstnma.east.verizon.net)
12:16.19*** join/#asterisk-bugs blitzrage (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
12:16.19*** mode/#asterisk-bugs [+o blitzrage] by ChanServ
12:44.03*** join/#asterisk-bugs russellb (i=russellb@asterisk/developer-and-stable-maintainer/drumkilla)
12:44.03*** mode/#asterisk-bugs [+o russellb] by ChanServ
13:11.08*** join/#asterisk-bugs jsmith (n=jsmith@h460565e0.area3.spcsdns.net)
13:11.09*** mode/#asterisk-bugs [+o jsmith] by ChanServ
13:36.45*** join/#asterisk-bugs putnopvut (i=putnopvu@nat/digium/x-6d58ec779f1f66c6)
13:36.45*** mode/#asterisk-bugs [+o putnopvut] by ChanServ
14:06.56*** join/#asterisk-bugs wunderkin (n=wunderki@ip72-223-86-126.ph.ph.cox.net)
14:11.25*** join/#asterisk-bugs Corydon76-home (i=indigo@pdpc/supporter/bronze/Corydon76-home)
14:11.25*** mode/#asterisk-bugs [+o Corydon76-home] by ChanServ
14:12.12*** join/#asterisk-bugs Corydon76-dig (n=tilghman@pdpc/supporter/bronze/Corydon76-home)
14:12.12*** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ
14:27.04*** join/#asterisk-bugs jcmoore (n=jcmoore@unaffiliated/tgrman)
14:47.23*** join/#asterisk-bugs fakhir (n=fakhir@unaffiliated/fakhir)
14:50.30*** join/#asterisk-bugs Corydon76-home (i=orange@pdpc/supporter/bronze/Corydon76-home)
14:50.30*** mode/#asterisk-bugs [+o Corydon76-home] by ChanServ
15:20.55*** join/#asterisk-bugs miguel3239 (n=elguerom@h-68-167-124-171.cmbrmaor.covad.net)
15:44.16putnopvutM10885
15:44.17MuffinMan[new] [Asterisk] Applications/app_queue 0010885: Queue recording via monitor-format and monitor-join produces output different from MixMonitor reported by Alric  http://bugs.digium.com/view.php?id=10885
15:44.36putnopvutDoes anyone know of a good reason NOT to deprecate the monitor-join option for queues?
15:45.06*** join/#asterisk-bugs kpfleming (i=kpflemin@nat/digium/x-b73397e31dd926e9)
15:45.06*** mode/#asterisk-bugs [+o kpfleming] by ChanServ
16:32.19*** join/#asterisk-bugs kpfleming (i=kpflemin@nat/digium/x-9fe3bb2753c47c0a)
16:32.19*** mode/#asterisk-bugs [+o kpfleming] by ChanServ
16:48.47*** topic/#asterisk-bugs by file -> Asterisk Bugs Discussion -=- http://bugs.digium.com/ -=- http://asterisk.org/developers/bug-guidelines - Asterisk 1.4.13 has been released (October 10, 2007). -=- If you are not discussing a report already posted to the bugtracker, the discussion probably belongs in #asterisk. -=- Goodbye 1.2. We'll miss you. Maybe. -=- Overall bug count: > 400 :( All hands on deck! CHOP CHOP!
16:49.13Corydon76-vcchfile: overall bug count is 398
16:49.26*** topic/#asterisk-bugs by file -> Asterisk Bugs Discussion -=- http://bugs.digium.com/ -=- http://asterisk.org/developers/bug-guidelines - Asterisk 1.4.13 has been released (October 10, 2007). -=- If you are not discussing a report already posted to the bugtracker, the discussion probably belongs in #asterisk. -=- Goodbye 1.2. We'll miss you. Maybe. -=- Overall bug count: > 390 :( All hands on deck! CHOP CHOP!
16:51.19russellbCHOP CHOP CHOP
16:51.25russellbit was > 410 when i woke up
16:53.10blitzrageeeesh
16:53.31blitzrageif there is anything that needs to get tested, let me know, and I'll try to find some time... although I should probably write docs
16:53.39filerussellb: <3
16:53.48blitzragebut if I get burned out from writing docs, then I'll try something else to rest my brain
16:53.52fileblitzrage: you are excused because of that insanity
16:54.01blitzrageoh joy
16:54.05blitzrageI think I'd rather work on bugs :)
16:54.15blitzragebut alas... I can not
16:54.47russellbgo blitzrage go
16:55.29blitzrageheh... :)
16:55.33blitzrageyay... conference call
16:56.26*** join/#asterisk-bugs fedealves (i=fedealve@97-243.187-72.tampabay.res.rr.com)
16:57.16fedealveshello I need help with nasty crash bug. Corydon76 asked me to come here and request that a bug marshall takes a look, for he does not have the time
16:58.03fedealvesthe bug id is 0010973
16:58.43fedealvesI am ready to give somebody access to my box, all the core dumps are in /tmp and /.
16:58.54Corydon76-vcchI said I couldn't commit to looking at it this week, not that I didn't have the time
16:59.59fedealvessorry for the misuderstanding, I am in production and my box collapses using regular scripts, so the func_odbc is my only way out
17:00.16fedealvesI am facing losing my business on this bug, just you know
17:01.13blitzragefedealves: that might be something you should take to the custom development department at Digium then
17:01.30blitzrageotherwise... it'll be looked at as time allows
17:02.10fedealvesa crash is something that should be handled by this mechanism, notpaying Digium. Besides, the only person who can really fix this is Corydon
17:02.12blitzrageyou could generate the backtrace from the cores by looking at the backtrace.txt file in the /doc/ sub-dir of your asterisk sources, and attach that to the bug as well
17:02.29blitzragefedealves: and it will get fixed -- but probably not in the next 10 mins
17:03.00fedealvesI load the core dump and use bt full, is there anything else that I should be doing??
17:03.17blitzragemake sure that the core was generated with DONT_OPTIMIZE
17:03.39fedealveshow do I change that? do I have to recompile Asterisk??
17:03.41blitzragefedealves: and I was only suggesting the custom development department since you implied this was  urgent
17:04.25blitzrageit's in menuselect under the .... I think 4th last menu (I forget exactly what the option is.... Development Flags or something like that)
17:04.30blitzrageor Compile Options maybe
17:04.54blitzrageif it's not set, then just select it, hit 'x' to save and exit from menuselect, then just run make install
17:05.25blitzragethen get the core again -- because without DONT_OPTIMIZE turned on, the core won't be useful to the developers
17:06.19fedealvesso I don;t need to generate new cores
17:06.19blitzrageyes you do
17:06.19fedealvesthanks god
17:06.19blitzrageif you don't have DONT_OPTIMIZE
17:06.19fedealvesthat means putting the box in production again
17:06.22blitzrageif you have DONT_OPTIMIZE, then you should be fine
17:19.29mvanbaaksorry to be of such less help
17:19.45mvanbaakI'm trying to get my serverfarm back up and running
17:20.47filemvanbaak: that's fine, you volunteer your time :D
17:20.58mvanbaak:)
17:21.14mvanbaakthought I should notify you guys about my leave-of-absence
17:21.31mvanbaakmy 2 main servers are giving segfaults on even the most basic sh scripts
17:21.36mvanbaak#!/bin/sh
17:21.40mvanbaakecho "hello world"
17:21.41file...eep
17:21.51mvanbaakSegfault on line 1: #!/bin/sh
17:21.57mvanbaaklike, wtf ?????
17:22.01mvanbaakand it's not all the time
17:22.05mvanbaakit's at random
17:22.11mvanbaakyay for bad ram
17:22.24mvanbaakso I got 2 new boxen
17:22.37mvanbaakand I'm close to done with the move
17:24.34mvanbaak:)
17:24.51mvanbaakactually, when you are browsing my site you will be doing that
17:25.01mvanbaakthe webservers are next to eachother :)
17:25.29fileoic
17:26.34mvanbaakone call to the right webserver, one call to the left webserver
17:26.44mvanbaakgotta love loadbalancing
17:26.53fileI don't *have* to
17:27.25mvanbaaklol
17:27.41mvanbaakwe do
17:27.53mvanbaakwe host a CRM application
17:28.00mvanbaakone box just cannot handle the load
17:28.08mvanbaakthose are not the ones with bad ram btw
17:28.27mvanbaakif one gets bad ram I simply pull it out and replace it with a spare part
17:28.41mvanbaakloadbalancer will handle the traffic without clients noticing
17:29.47mvanbaakok, back to my own servers
17:29.49mvanbaaklatero all
17:32.13*** join/#asterisk-bugs d1mas (n=chatzill@ip195.117.adsl.wplus.ru)
17:59.40*** join/#asterisk-bugs matsk (n=mk@host-217-213-131-114.mobileonline.telia.com)
18:05.30fedealvesfor Corydon76 and blitzrage: I just uploaded a bt full trace taken without optimize, please look at it
18:11.34Corydon76-vcchfedealves: are you using pooling=yes in res_odbc.conf ?
18:11.45fedealvesI tried with both
18:11.55fedealvesit blew up in either case
18:12.02fedealvesnow is Not pooling
18:12.05Corydon76-vcchUm, if you're using MS SQL Server, you should NEVER have that option off
18:12.16fedealvesI know, it was on
18:12.23fedealvesbut it blew up anyway
18:12.26fedealveslet me check now
18:12.37Corydon76-vcchDid you reload after changing the option?
18:12.51Corydon76-vcchBecause that would explain it blowing up
18:13.07fedealvesyes
18:13.19fedealvesI just put it back
18:13.31fedealvesit blows up every 2 minutes in production
18:13.42fedealvesdo you want me to test it again??
18:14.19Corydon76-vcchWhat's the limit set to?
18:14.22fedealves1000
18:15.10fedealveslet me know if you need another trace once the pooling is back on
18:15.30Corydon76-vcchYes, please
18:15.34fedealvesok
18:25.09fedealvesit has not blown up yer
18:25.11fedealvesyet
18:25.24fedealvesIf it does I will upload it
18:34.24d1masdoes asterisk code has some facilities to dump stack trace?
18:34.53d1mas(without killing/stoping the server of course)
19:00.00russellbthere is an ast_backtrace() function for use on linux
19:00.03russellbi have never used it though
19:01.08putnopvutI have. It's not very helpful because there's no symbol information from .so files.
19:01.24putnopvutSo you'll have a lot of stack traces with ????? in them.
19:19.49Corydon76-vcchputnopvut: sounds like you didn't compile with DONT_OPTIMIZE when you used it
19:20.17Corydon76-vcchBecause that's exactly what it does without DONT_OPTIMIZE
19:21.19putnopvutI have never compiled without DONT_OPTIMIZE
19:25.24Corydon76-vcchThen it might be that we've failed to turn off some optimization flags in DONT_OPTIMIZE
19:32.45putnopvutHmm, I may be misremembering the ??????'s, but I do seem to recall the backtrace not being very helpful. I'll run a quick test.
19:34.26putnopvutAh, here we go.
19:34.29putnopvuthttp://pastebin.ca/737841
19:35.05putnopvutI put ast_backtrace in a deep queue function, and you can see that all the stack entries from app_queue.so don't have the function name.
19:35.12putnopvutThat's what I was remembering.
19:36.15*** join/#asterisk-bugs Deeewayne (i=dwayne@nat/digium/x-9854a1dd47bd17b2)
19:36.16*** mode/#asterisk-bugs [+o Deeewayne] by ChanServ
20:09.37*** join/#asterisk-bugs mvanbaak (n=mafkees@vanbaak.xs4all.nl)
21:00.48*** topic/#asterisk-bugs by Qwell -> Asterisk Bugs Discussion -=- http://bugs.digium.com/ -=- http://asterisk.org/developers/bug-guidelines - Asterisk 1.4.13 has been released (October 10, 2007). -=- If you are not discussing a report already posted to the bugtracker, the discussion probably belongs in #asterisk. -=- Goodbye 1.2. We'll miss you. Maybe. -=- Overall bug count: <= 390 :( All hands on deck! CHOP CHOP!
21:00.51Qwell!!
21:04.30russellbstarted at 412 :)
21:04.31russellbthat's hot
21:04.38Qwellindeed
21:04.44file<3 all who pitched in
21:05.03russellbi just had a typo on line 666 o.O
21:05.17russellbgcc skar3d me :(
21:05.28fileGCC is a scary beast
21:06.16russellbi knowz
21:35.33*** join/#asterisk-bugs jsmith (n=jsmith@h460565e0.area3.spcsdns.net)
21:35.33*** mode/#asterisk-bugs [+o jsmith] by ChanServ
21:54.12*** topic/#asterisk-bugs by Qwell -> Asterisk Bugs Discussion -=- http://bugs.digium.com/ -=- http://asterisk.org/developers/bug-guidelines - Asterisk 1.4.13 has been released (October 10, 2007). -=- If you are not discussing a report already posted to the bugtracker, the discussion probably belongs in #asterisk. -=- Goodbye 1.2. We'll miss you. Maybe. -=- Overall bug count: < 390 :( All hands on deck! CHOP CHOP!
21:55.31Corydon76-vcchUm, 0 bugs is also < 390...
21:56.07*** part/#asterisk-bugs zerohalo (n=zeroHalo@pool-72-70-79-233.bstnma.east.verizon.net)
21:57.28Qwell0 would be good
21:57.34Qwellwell, sort of
21:57.45jsmithNope... it'd mean we're worthless :-)
21:57.51Qwelljsmith: new features :D
21:57.53Corydon76-vcchOr fast
21:59.38putnopvutEnd of this week, I expect to close out at least 7 or 8 queue issues all at once.
22:00.57jsmithw00t!
22:01.04jsmithPut those queue bugs on hold!
22:04.30fedealvesI uploaded the traces for my bug, from a de-optimized build. it blew up 40 times since two hours ago
22:08.50putnopvutfedealves: which issue is this?
22:13.13fedealves0010973
22:13.54putnopvutM10973
22:13.55MuffinMan[assigned] [Asterisk] CDR/cdr_odbc 0010973: several crashes in Trunk using cdr_odbc and func_odbc with SQL Server. fretds 0.64 (latest) reported by falves11  http://bugs.digium.com/view.php?id=10973
22:14.05fedealvesyes
22:14.50fedealvesI need a super-man to log into my box and find out looking at the dumps what is failing. There must be something simple
22:30.32fedealvesdear corydon76, are you logged?
23:43.09d1masGuys, I run asterisk under valgring and I'm getting flood of output from valgring. Do you normally test * under valgrind?
23:43.45d1masvalgrind
23:50.35d1mascan someone please take a quick look at http://pastebin.org/4935 ? To me first report is some kind of double-freed memory. I'm not sure what to do about rest because they happen in libcrypto, not in asterisk

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.