Paul,

Noloading modules via modules.conf is a band-aid to your problem. Each time you upgrade to the latest CVS, you are likely to run into similar problems requiring more noloads. I'm assuming that you were upgrading a working installation of Asterisk when this problem occurred (if not, it looks like the Debian package may be broken). If you were upgrading, try this:

First:

cd /usr/lib/asterisk/modules/
rm *.so

Then:

Recompile Asterisk. You may need to recompile anything else that put loadable modules into that directory, such as asterisk-addons, as well.

Does anyone out there know why "make clean" doesn't take care of this task? I spent a few hours dealing with the same situation, assuming something was wrong with my config files or the new CVS release before I stumbled across this simple fix. Some modules would fail with an error message, while others would seg fault.

I hope this was helpful,

Matthew Roth
http://voip-info.org/tiki-index.php?page=Running%20Asterisk%20on%20Debian

PS - To the list: I'm sorry if I've broken etiquette by basically copying and pasting my response to multiple people having similar problems. If there is a better way to address an issue when more than one person is experiencing it, please let me know.

Paul A Brown wrote:


----- Original Message ----- From: "Vladyslav" <[EMAIL PROTECTED]>
To: "Asterisk Users Mailing List - Non-Commercial Discussion" <[email protected]>
Sent: Tuesday, April 19, 2005 9:02 AM
Subject: Re: [Asterisk-Users] Upgraded now Asterisk won't start



U better add line to your /etc/asterisk/modules.conf
noload => chan_phone.so
before [global] section

(of course in case U don't need that module...)
and it will start


Thanks, I managed to work out another I needed to disable and up it came.

Thanks for your help

Paul

_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to