| Summary: | ASTERISK-08537: Latest SVN crashes asterisk with SIP registion and res_config_pgsql.(pgsql) | ||
| Reporter: | raiden (raiden) | Labels: | |
| Date Opened: | 2007-01-09 21:44:38.000-0600 | Date Closed: | 2007-02-19 09:12:49.000-0600 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Registration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Something within the last week with Asterisk latest trunk(SVN) is now segfaulting asterisk using postgres (8.2.1) database support through res_config_pgsql. I have my regular database setup (same as before as it is working with older versions of asterisk). chan_sip.so => (Session Initiation Protocol (SIP)) Asterisk Ready. *CLI> *CLI> [Jan 9 21:32:38] WARNING[2051]: res_config_pgsql.c:99 realtime_pgsql: Postgresql RealTime: Realtime retrieval requires at least 1 parameter and 1 value to search on. [Jan 9 21:32:38] NOTICE[2051]: chan_sip.c:14621 handle_request_register: Registration from 'sip:2152@192.168.0.1' failed for '192.168.0.254' - No matching peer found Segmentation fault and just crashes there. Because it crashes, I can see any log data in /var/log/asterisk/messages. (empty). I am able to do any cli commands but once that first registration hits the system, thats when it segfaults. Not sure if any changes in the latest postgres (8.2.1) stable release causes problems with asterisk? Any help fixing it in trunk/1.4 would be greatly appreciated. | ||
| Comments: | By: Serge Vecher (serge-v) 2007-01-10 09:03:44.000-0600 We need to see a backtrace to fix the crash. Also, please always specify the revision in use. 1. Enable DONT_OPTIMIZE flag in menuselect under Compiler Options. 2. Rebuild Asterisk 3. Start Asterisk with '-g' option 4. When crash occurs, perform 'bt' on the core file. Then 'thread apply all bt full' Let's see the new output. Thanks. By: raiden (raiden) 2007-01-11 22:07:45.000-0600 Is it possible from the configure command line parameters to set the DONT_OPTIMIZE *instead* of having to set it in menuselect? By: deti (deti) 2007-01-12 15:56:09.000-0600 most probably related to / caused by Bug 8803 By: Serge Vecher (serge-v) 2007-01-15 09:27:23.000-0600 raiden, please confirm deti's findings by checking out first revision prior to 50784. I'm not aware of a command line parameter for dont_optimize setting -- just use menuselect. By: Olle Johansson (oej) 2007-02-15 15:33:12.000-0600 ...waiting for the backtrace. Can't do anything without it, since we have no idea on where your crash happens. By: Serge Vecher (serge-v) 2007-02-19 09:12:49.000-0600 no response from reporter. Please reopen if still reproducible with latest trunk and debugging information is available as requested. | ||