|Summary:||ASTERISK-11410: res_snmp.so hangs asterisk at startup|
|Reporter:||Anthony Messina (amessina)||Labels:|
|Date Opened:||2008-02-09 10:53:02.000-0600||Date Closed:||2008-04-03 13:39:39|
|Description:||Running Asterisk-1.4.18 (from ATrpms.net) on Fedora 8 x86_64, I see the following issue:|
At bootup or when I issue a "service asterisk restart" (init.d), Asterisk hangs when loading res_snmp.so and Asterisk must be killed with -s 9
However, if i add a "noload => res_snmp.so" to modules.conf, let Asterisk startup and then do "asterisk -rx"module load res_snmp.so"", it works just fine, loads and connects to snmpd.
I have the agent configured as a sub agent and run asterisk as user and group "asterisk".
subagent = yes
enabled = yes
I used to see this issue occur randomly on a separate, but identically configured i386 machine. Now, the i386 machine has no problem loading res_snmp.so at startup, but the x86_64 does.
I do not get any useful info from debug: the last line before I must kill asterisk is always:
DEBUG config.c: Parsing /etc/asterisk/res_snmp.conf
|Comments:||By: Anthony Messina (amessina) 2008-02-09 13:56:35.000-0600|
This issue also occurs using 1.4.17 on x86_64, but NOT i386.
By: Joshua C. Colp (jcolp) 2008-02-11 09:01:54.000-0600
We need an Asterisk compiled with DONT_OPTIMIZE and a backtrace so we can see where it is hanging. You can grab it by doing gdb asterisk --pid=<pid of the running Asterisk> and typing thread apply all bt and uploading it as a separate attachment.
By: Anthony Messina (amessina) 2008-02-13 03:43:18.000-0600
Since I am using RPMs from ATrpms.net, I don't have things set up to build myself at this time. I will try to work on a way to get the requested information.
By: Donny Kavanagh (donnyk) 2008-03-13 00:06:01
If you can please build from source (latest 1.4 or trunk) and confirm you are able to re-create the issue. If so, compile as file mentioned with DONT_OPTIMIZE (accessible in make menuconfig) and then we can work from there. Without any more information we cannot proceed.
By: Anthony Messina (amessina) 2008-03-13 00:26:44
I currently have two systems, and i386 and an x86_64, both in production. I do not have a test environment. Unfortuntely, I've had enough problems with the DTMF changes, that are reported to be set fixed in what will be zaptel 1.4.10.
Those issues are keeping me using asterisk 1.4.17 on x86_64 and asterisk 1.4.18 on i386.
I am not able to do any testing or re-compiling at this time. My current workaround is to have a noload => res_snmp.so then manually issue a module load res_snmp.so after asterisk is started (which works perfectly, though is obviously less than optimal).
I wish I could be more help at this time, but I'll have to wait to stabilize and update these systems prior to messing with this.
I am also working to procure a system that I can use for testing.
By: Anthony Messina (amessina) 2008-04-03 12:49:13
I do not have this issue with 126.96.36.199, using Fedora 8 RPMs from fedoraproject.org
By: Mark Michelson (mmichelson) 2008-04-03 13:39:38
Closing based on the last bug note here.