Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
On Fri, Jan 27, 2006 at 04:03:23PM -0600, Joseph Tanner wrote: > Quick and dirty solution: > > mv /usr/lib/asterisk/modules /usr/lib/asterisk/modules.bak And just as a reminder: those are basically exactly the problems package management systems are here to solve. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il | | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | | friend ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
On Fri, Jan 27, 2006 at 03:20:16PM -0600, Dan Littlejohn wrote: > I was confused about the modules. > > Got this warning when upgrading to 1.2.3 even when using the most > current asterisk-addons and even svn asterisk-addons. > > WARNING WARNING WARNING > > Your Asterisk modules directory, located at > /usr/lib/asterisk/modules > contains modules that were not installed by this > version of Asterisk. Please ensure that these > modules are compatible with this version before > attempting to run Asterisk. > [ order of modules changed a bit, if you don't mind ] >app_addon_sql_mysql.so >cdr_addon_mysql.so >res_config_mysql.so >format_mp3.so Those are from asterisk-addons . >app_rxfax.so >app_txfax.so Those are from the apps of >app_saycountpl.so >app_striplsd.so >app_substring.so Standard asterisk modules, IIRC. See note below. >chan_modem_aopen.so >chan_modem_bestdata.so >chan_modem_i4l.so >chan_modem.so chan_modem* may be leftovers from older asterisk 1.0.x ? They are now not built by defaults. Look at the dates. > > WARNING WARNING WARNING > > Do not understand how to fix this? Do not know if that would also be > related to the ops crashing. Remove modules you don't need anymore and try again :-) Theoretically you should not be required to rebuild modules on a minor upgrade (that is: as long as it remains 1.2). But if there are older leftovers, they need removing. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il | | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | | friend ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
On Jan 29, 2006, at 1:24 PM, Michiel van Baak wrote: On 13:09, Sun 29 Jan 06, Martin Joseph wrote: I removed the following to get it starting up again: app_enumlookup.so app_groupcount.so app_md5.so app_txtcidname.so func_cut.so Both the README and the UPGRADE listed that those functions became obsolete and were replaced by dialplan functions. It got me too the first time, but after reading some more docs and the release messages all got clear to me. Now everytime I upgrade I first move away the module/app/func dir just to be sure. Thanks, duh! I guess RTFM is the answer... Marty ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
On 13:09, Sun 29 Jan 06, Martin Joseph wrote: > I removed the following to get it starting up again: > > app_enumlookup.so > app_groupcount.so > app_md5.so > app_txtcidname.so > func_cut.so Both the README and the UPGRADE listed that those functions became obsolete and were replaced by dialplan functions. It got me too the first time, but after reading some more docs and the release messages all got clear to me. Now everytime I upgrade I first move away the module/app/func dir just to be sure. -- Michiel van Baak http://michiel.vanbaak.info [EMAIL PROTECTED] GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7E0B9A2D "Why is it drug addicts and computer afficionados are both called users?" ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
On Jan 29, 2006, at 10:30 AM, Warren Burstein wrote: I took a look at the asterisk-1.2.3 Makefile, seems to me that the WARNING is just a list of all the .so files found in the modules directory that aren't also found in a subdirectory, it isn't checking that they were built with the current version. So it's going to complain about the modules that come from asterisk-addons every time "make install" is run in asterisk, no matter what. Not a big problem once you learn to ignore the message, but people are probably going to keep asking what it means. Actually in this case, it means it! I updated from 1.21 to current as of yesterday, and my * wouldn't start as it complained about the modules it couldn't load. I removed the following to get it starting up again: app_enumlookup.so app_groupcount.so app_md5.so app_txtcidname.so func_cut.so This seems to be ok, but I wonder if I have broken anything with this approach? I didn't understand that removing all the modules and doing a make install would replace the needed ones? What about the g729 codecs aren't those stored here too? Thanks, Marty ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
I took a look at the asterisk-1.2.3 Makefile, seems to me that the WARNING is just a list of all the .so files found in the modules directory that aren't also found in a subdirectory, it isn't checking that they were built with the current version. So it's going to complain about the modules that come from asterisk-addons every time "make install" is run in asterisk, no matter what. Not a big problem once you learn to ignore the message, but people are probably going to keep asking what it means. Julian Lyndon-Smith wrote: Warren, You may only use cdr_addon_mysql.so, but I believe that * normally automatically loads all modules it finds (see modules.conf for autoload=yes). The following modules were found in your modules directory, and 1.2.3 of * did not like them, because you got a warning after compile. In the case of app_rxfax.so and app_txfax.so these must of been compiled with a previous version of *, otherwise it would not have complained about them (I know this, because I had a similar issue). If you have kept the previous version of *, check your makefile for app_txfax and app_rxfax, make the same mods to your 1.2.3 makefile and recompile. * will then not complain about the *fax* modules. You may also need to recompile the asterisk-addons, simply because header files and or libraries may have changed in the core asterisk files. I guess what I am saying is that 1.2.3 of * may work with 1.2.1 of asterisk-addons (that is the latest version as you say), but asterisk-addons would need recompiling as well. If you make cleam;make and make install the asterisk-addons, do you get the same error when you make install asterisk ? Julian. app_addon_sql_mysql.so app_rxfax.so app_saycountpl.so app_striplsd.so app_substring.so app_txfax.so cdr_addon_mysql.so chan_modem_aopen.so chan_modem_bestdata.so chan_modem_i4l.so chan_modem.so format_mp3.so res_config_mysql.so Warren Burstein wrote: Julian Lyndon-Smith wrote: These modules are not part of the standard 1.2.3 release - did you also install the 1.2.3 release of the asterisk-addons package ? The lastest asterisk-addons I found at http://ftp.digium.com/pub/asterisk/ is 1.2.1. The only module I use is cdr_addon_mysql.so. I've been using it with 1.2.2 and 1.2.3 without any problem other than the message during "make install", which I just ignore. Is there a need for an update to asterisk-addons? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
It looks like my modules are all up to date - they are all dated the 25th Jan - aka "Black Wednesday". What really bugs me about this is the lack of useful info from any logs. The last call to take place, the call that gets distorted, has no entry. This has to indicate something, no? >Hmm - I'd do as others have suggested and move the /usr/lib/asterisk/modules directory to another, and do a make clean;make;make install >If you have app_rxfax.so installed then you must have customised your original makefile, and not the 1.2.3 makefile, which would suggest that these modules are from a previous asterisk version. >Let us know how you get on. >Julian. >Dan Littlejohn wrote: >> On 1/27/06, Julian Lyndon-Smith <[EMAIL PROTECTED]> wrote: >>> These modules are not part of the standard 1.2.3 release - did you >>> also install the 1.2.3 release of the asterisk-addons package ? >>> >>> If * is loading older modules (which it probably is because of your >>> config files) then it may cause grief ;) >>> >>> My .2p worth. Probably not helpful, but maybe, just maybe >>> >>> Julian >>> >>> Dan Littlejohn wrote: On 1/27/06, Noah Miller <[EMAIL PROTECTED]> wrote: > Hi Brent - Sincerely, Brent A. Torrenga [EMAIL PROTECTED] Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 219.836.8918x325 Voice 219.836.1138 Facsimile www.torrenga.com ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
Warren, You may only use cdr_addon_mysql.so, but I believe that * normally automatically loads all modules it finds (see modules.conf for autoload=yes). The following modules were found in your modules directory, and 1.2.3 of * did not like them, because you got a warning after compile. In the case of app_rxfax.so and app_txfax.so these must of been compiled with a previous version of *, otherwise it would not have complained about them (I know this, because I had a similar issue). If you have kept the previous version of *, check your makefile for app_txfax and app_rxfax, make the same mods to your 1.2.3 makefile and recompile. * will then not complain about the *fax* modules. You may also need to recompile the asterisk-addons, simply because header files and or libraries may have changed in the core asterisk files. I guess what I am saying is that 1.2.3 of * may work with 1.2.1 of asterisk-addons (that is the latest version as you say), but asterisk-addons would need recompiling as well. If you make cleam;make and make install the asterisk-addons, do you get the same error when you make install asterisk ? Julian. app_addon_sql_mysql.so app_rxfax.so app_saycountpl.so app_striplsd.so app_substring.so app_txfax.so cdr_addon_mysql.so chan_modem_aopen.so chan_modem_bestdata.so chan_modem_i4l.so chan_modem.so format_mp3.so res_config_mysql.so Warren Burstein wrote: Julian Lyndon-Smith wrote: These modules are not part of the standard 1.2.3 release - did you also install the 1.2.3 release of the asterisk-addons package ? The lastest asterisk-addons I found at http://ftp.digium.com/pub/asterisk/ is 1.2.1. The only module I use is cdr_addon_mysql.so. I've been using it with 1.2.2 and 1.2.3 without any problem other than the message during "make install", which I just ignore. Is there a need for an update to asterisk-addons? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
Julian Lyndon-Smith wrote: These modules are not part of the standard 1.2.3 release - did you also install the 1.2.3 release of the asterisk-addons package ? The lastest asterisk-addons I found at http://ftp.digium.com/pub/asterisk/ is 1.2.1. The only module I use is cdr_addon_mysql.so. I've been using it with 1.2.2 and 1.2.3 without any problem other than the message during "make install", which I just ignore. Is there a need for an update to asterisk-addons? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
Alternatively you can issue the following command (which deletes all
the .so modules excluding the g729 codec module) prior to make install
find /usr/lib/asterisk/modules/ -name "*.so" -a ! -name
"codec_g729a.so" -exec rm -f {} \;
On 1/28/06, Julian Lyndon-Smith <[EMAIL PROTECTED]> wrote:
> Hmm - I'd do as others have suggested and move the
> /usr/lib/asterisk/modules directory to another, and do a make
> clean;make;make install
>
> If you have app_rxfax.so installed then you must have customised your
> original makefile, and not the 1.2.3 makefile, which would suggest that
> these modules are from a previous asterisk version.
>
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
Hmm - I'd do as others have suggested and move the /usr/lib/asterisk/modules directory to another, and do a make clean;make;make install If you have app_rxfax.so installed then you must have customised your original makefile, and not the 1.2.3 makefile, which would suggest that these modules are from a previous asterisk version. Let us know how you get on. Julian. Dan Littlejohn wrote: On 1/27/06, Julian Lyndon-Smith <[EMAIL PROTECTED]> wrote: These modules are not part of the standard 1.2.3 release - did you also install the 1.2.3 release of the asterisk-addons package ? If * is loading older modules (which it probably is because of your config files) then it may cause grief ;) My .2p worth. Probably not helpful, but maybe, just maybe Julian Dan Littlejohn wrote: On 1/27/06, Noah Miller <[EMAIL PROTECTED]> wrote: Hi Brent - Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course had the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for 24 hours or so. Since upgrading to 1.2.3, though, the whole system has locked up twice. Once on Thursday, and then about a half hour ago. The server would reply to a ping, but no ssh login, no local console login - just locked up. This ain't good for business. We've been doing fine with 1.2.3 so far. No problems reported, though I only have it deployed in a small office. Definitely no lock-ups. On the asterisk side, just a basic question - did you make sure to remove the old modules so the new 1.2.3 versions got installed? As far as the lockups, maybe it is coincidental? I've never had asterisk (even the crazy CVS versions) lock a whole OS like that. I have had machines running asterisk lock up, but it always turned out to be caused by something else like bad hardware, or unrelated network problems. - Noah ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users I was confused about the modules. Got this warning when upgrading to 1.2.3 even when using the most current asterisk-addons and even svn asterisk-addons. WARNING WARNING WARNING Your Asterisk modules directory, located at /usr/lib/asterisk/modules contains modules that were not installed by this version of Asterisk. Please ensure that these modules are compatible with this version before attempting to run Asterisk. app_addon_sql_mysql.so app_rxfax.so app_saycountpl.so app_striplsd.so app_substring.so app_txfax.so cdr_addon_mysql.so chan_modem_aopen.so chan_modem_bestdata.so chan_modem_i4l.so chan_modem.so format_mp3.so res_config_mysql.so WARNING WARNING WARNING Do not understand how to fix this? Do not know if that would also be related to the ops crashing. Dan ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users There is no asterisk-addons 1.2.3. Only 1.2.1 and I tried that and svn and still get this warning? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
On 1/27/06, Julian Lyndon-Smith <[EMAIL PROTECTED]> wrote: > These modules are not part of the standard 1.2.3 release - did you also > install the 1.2.3 release of the asterisk-addons package ? > > If * is loading older modules (which it probably is because of your > config files) then it may cause grief ;) > > My .2p worth. Probably not helpful, but maybe, just maybe > > Julian > > Dan Littlejohn wrote: > > On 1/27/06, Noah Miller <[EMAIL PROTECTED]> wrote: > >> Hi Brent - > >> > >>> Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course had > >>> the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for 24 > >>> hours or so. > >>> > >>> Since upgrading to 1.2.3, though, the whole system has locked up twice. > >>> Once > >>> on Thursday, and then about a half hour ago. The server would reply to a > >>> ping, but no ssh login, no local console login - just locked up. This > >>> ain't > >>> good for business. > >> > >> We've been doing fine with 1.2.3 so far. No problems reported, though I > >> only have it deployed in a small office. Definitely no lock-ups. > >> > >> On the asterisk side, just a basic question - did you make sure to remove > >> the old modules so the new 1.2.3 versions got installed? > >> > >> As far as the lockups, maybe it is coincidental? I've never had asterisk > >> (even the crazy CVS versions) lock a whole OS like that. I have had > >> machines running asterisk lock up, but it always turned out to be caused by > >> something else like bad hardware, or unrelated network problems. > >> > >> - Noah > >> > >> ___ > >> --Bandwidth and Colocation provided by Easynews.com -- > >> > >> Asterisk-Users mailing list > >> To UNSUBSCRIBE or update options visit: > >>http://lists.digium.com/mailman/listinfo/asterisk-users > >> > > > > > > I was confused about the modules. > > > > Got this warning when upgrading to 1.2.3 even when using the most > > current asterisk-addons and even svn asterisk-addons. > > > > WARNING WARNING WARNING > > > > Your Asterisk modules directory, located at > > /usr/lib/asterisk/modules > > contains modules that were not installed by this > > version of Asterisk. Please ensure that these > > modules are compatible with this version before > > attempting to run Asterisk. > > > >app_addon_sql_mysql.so > >app_rxfax.so > >app_saycountpl.so > >app_striplsd.so > >app_substring.so > >app_txfax.so > >cdr_addon_mysql.so > >chan_modem_aopen.so > >chan_modem_bestdata.so > >chan_modem_i4l.so > >chan_modem.so > >format_mp3.so > >res_config_mysql.so > > > > WARNING WARNING WARNING > > > > Do not understand how to fix this? Do not know if that would also be > > related to the ops crashing. > > > > Dan > > ___ > > --Bandwidth and Colocation provided by Easynews.com -- > > > > Asterisk-Users mailing list > > To UNSUBSCRIBE or update options visit: > >http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > > ___ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > There is no asterisk-addons 1.2.3. Only 1.2.1 and I tried that and svn and still get this warning? ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
Got my commands mixed up. The last should be "cp -r /usr/lib/asterisk/modules.bak /usr/lib/asterisk/modules", it shouldn't be /usr/lib/modules. Sorry bout that, wasn't thinking clearly. Joseph Tanner On 1/27/06, Joseph Tanner <[EMAIL PROTECTED]> wrote: > Quick and dirty solution: > > mv /usr/lib/asterisk/modules /usr/lib/asterisk/modules.bak > > Then go into the asterisk source directory (in my case, > /usr/src/asterisk) and do a make install. Might as well re-install > the asterisk-addons too, if you need anything there. Try running > asterisk now and put it through its paces. If you're missing any > functionality, try to put it back in (probably a module included in > asterisk-addons). If you can't get it working and time is critical, > just stop asterisk, do a "mv /usr/lib/asterisk/modules > /usr/lib/asterisk/modules.new" and then a "cp -r > /usr/lib/asterisk/modules.bak /usr/lib/modules" and restart asterisk > and try to figure out what went wrong. The modules.new directory has > all the new modules, modules.bak still has the old ones. > > Joseph Tanner > > On 1/27/06, Dan Littlejohn <[EMAIL PROTECTED]> wrote: > > On 1/27/06, Noah Miller <[EMAIL PROTECTED]> wrote: > > > Hi Brent - > > > > > > > Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course > > > > had > > > > the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for > > > > 24 > > > > hours or so. > > > > > > > > Since upgrading to 1.2.3, though, the whole system has locked up twice. > > > > Once > > > > on Thursday, and then about a half hour ago. The server would reply to a > > > > ping, but no ssh login, no local console login - just locked up. This > > > > ain't > > > > good for business. > > > > > > > > > We've been doing fine with 1.2.3 so far. No problems reported, though I > > > only have it deployed in a small office. Definitely no lock-ups. > > > > > > On the asterisk side, just a basic question - did you make sure to remove > > > the old modules so the new 1.2.3 versions got installed? > > > > > > As far as the lockups, maybe it is coincidental? I've never had asterisk > > > (even the crazy CVS versions) lock a whole OS like that. I have had > > > machines running asterisk lock up, but it always turned out to be caused > > > by > > > something else like bad hardware, or unrelated network problems. > > > > > > - Noah > > > > > > ___ > > > --Bandwidth and Colocation provided by Easynews.com -- > > > > > > Asterisk-Users mailing list > > > To UNSUBSCRIBE or update options visit: > > >http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > > > > > I was confused about the modules. > > > > Got this warning when upgrading to 1.2.3 even when using the most > > current asterisk-addons and even svn asterisk-addons. > > > > WARNING WARNING WARNING > > > > Your Asterisk modules directory, located at > > /usr/lib/asterisk/modules > > contains modules that were not installed by this > > version of Asterisk. Please ensure that these > > modules are compatible with this version before > > attempting to run Asterisk. > > > >app_addon_sql_mysql.so > >app_rxfax.so > >app_saycountpl.so > >app_striplsd.so > >app_substring.so > >app_txfax.so > >cdr_addon_mysql.so > >chan_modem_aopen.so > >chan_modem_bestdata.so > >chan_modem_i4l.so > >chan_modem.so > >format_mp3.so > >res_config_mysql.so > > > > WARNING WARNING WARNING > > > > Do not understand how to fix this? Do not know if that would also be > > related to the ops crashing. > > > > Dan > > ___ > > --Bandwidth and Colocation provided by Easynews.com -- > > > > Asterisk-Users mailing list > > To UNSUBSCRIBE or update options visit: > >http://lists.digium.com/mailman/listinfo/asterisk-users > > > ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
Quick and dirty solution: mv /usr/lib/asterisk/modules /usr/lib/asterisk/modules.bak Then go into the asterisk source directory (in my case, /usr/src/asterisk) and do a make install. Might as well re-install the asterisk-addons too, if you need anything there. Try running asterisk now and put it through its paces. If you're missing any functionality, try to put it back in (probably a module included in asterisk-addons). If you can't get it working and time is critical, just stop asterisk, do a "mv /usr/lib/asterisk/modules /usr/lib/asterisk/modules.new" and then a "cp -r /usr/lib/asterisk/modules.bak /usr/lib/modules" and restart asterisk and try to figure out what went wrong. The modules.new directory has all the new modules, modules.bak still has the old ones. Joseph Tanner On 1/27/06, Dan Littlejohn <[EMAIL PROTECTED]> wrote: > On 1/27/06, Noah Miller <[EMAIL PROTECTED]> wrote: > > Hi Brent - > > > > > Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course had > > > the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for 24 > > > hours or so. > > > > > > Since upgrading to 1.2.3, though, the whole system has locked up twice. > > > Once > > > on Thursday, and then about a half hour ago. The server would reply to a > > > ping, but no ssh login, no local console login - just locked up. This > > > ain't > > > good for business. > > > > > > We've been doing fine with 1.2.3 so far. No problems reported, though I > > only have it deployed in a small office. Definitely no lock-ups. > > > > On the asterisk side, just a basic question - did you make sure to remove > > the old modules so the new 1.2.3 versions got installed? > > > > As far as the lockups, maybe it is coincidental? I've never had asterisk > > (even the crazy CVS versions) lock a whole OS like that. I have had > > machines running asterisk lock up, but it always turned out to be caused by > > something else like bad hardware, or unrelated network problems. > > > > - Noah > > > > ___ > > --Bandwidth and Colocation provided by Easynews.com -- > > > > Asterisk-Users mailing list > > To UNSUBSCRIBE or update options visit: > >http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > I was confused about the modules. > > Got this warning when upgrading to 1.2.3 even when using the most > current asterisk-addons and even svn asterisk-addons. > > WARNING WARNING WARNING > > Your Asterisk modules directory, located at > /usr/lib/asterisk/modules > contains modules that were not installed by this > version of Asterisk. Please ensure that these > modules are compatible with this version before > attempting to run Asterisk. > >app_addon_sql_mysql.so >app_rxfax.so >app_saycountpl.so >app_striplsd.so >app_substring.so >app_txfax.so >cdr_addon_mysql.so >chan_modem_aopen.so >chan_modem_bestdata.so >chan_modem_i4l.so >chan_modem.so >format_mp3.so >res_config_mysql.so > > WARNING WARNING WARNING > > Do not understand how to fix this? Do not know if that would also be > related to the ops crashing. > > Dan > ___ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
These modules are not part of the standard 1.2.3 release - did you also install the 1.2.3 release of the asterisk-addons package ? If * is loading older modules (which it probably is because of your config files) then it may cause grief ;) My .2p worth. Probably not helpful, but maybe, just maybe Julian Dan Littlejohn wrote: On 1/27/06, Noah Miller <[EMAIL PROTECTED]> wrote: Hi Brent - Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course had the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for 24 hours or so. Since upgrading to 1.2.3, though, the whole system has locked up twice. Once on Thursday, and then about a half hour ago. The server would reply to a ping, but no ssh login, no local console login - just locked up. This ain't good for business. We've been doing fine with 1.2.3 so far. No problems reported, though I only have it deployed in a small office. Definitely no lock-ups. On the asterisk side, just a basic question - did you make sure to remove the old modules so the new 1.2.3 versions got installed? As far as the lockups, maybe it is coincidental? I've never had asterisk (even the crazy CVS versions) lock a whole OS like that. I have had machines running asterisk lock up, but it always turned out to be caused by something else like bad hardware, or unrelated network problems. - Noah ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users I was confused about the modules. Got this warning when upgrading to 1.2.3 even when using the most current asterisk-addons and even svn asterisk-addons. WARNING WARNING WARNING Your Asterisk modules directory, located at /usr/lib/asterisk/modules contains modules that were not installed by this version of Asterisk. Please ensure that these modules are compatible with this version before attempting to run Asterisk. app_addon_sql_mysql.so app_rxfax.so app_saycountpl.so app_striplsd.so app_substring.so app_txfax.so cdr_addon_mysql.so chan_modem_aopen.so chan_modem_bestdata.so chan_modem_i4l.so chan_modem.so format_mp3.so res_config_mysql.so WARNING WARNING WARNING Do not understand how to fix this? Do not know if that would also be related to the ops crashing. Dan ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
On 1/27/06, Noah Miller <[EMAIL PROTECTED]> wrote: > Hi Brent - > > > Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course had > > the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for 24 > > hours or so. > > > > Since upgrading to 1.2.3, though, the whole system has locked up twice. Once > > on Thursday, and then about a half hour ago. The server would reply to a > > ping, but no ssh login, no local console login - just locked up. This ain't > > good for business. > > > We've been doing fine with 1.2.3 so far. No problems reported, though I > only have it deployed in a small office. Definitely no lock-ups. > > On the asterisk side, just a basic question - did you make sure to remove > the old modules so the new 1.2.3 versions got installed? > > As far as the lockups, maybe it is coincidental? I've never had asterisk > (even the crazy CVS versions) lock a whole OS like that. I have had > machines running asterisk lock up, but it always turned out to be caused by > something else like bad hardware, or unrelated network problems. > > - Noah > > ___ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > I was confused about the modules. Got this warning when upgrading to 1.2.3 even when using the most current asterisk-addons and even svn asterisk-addons. WARNING WARNING WARNING Your Asterisk modules directory, located at /usr/lib/asterisk/modules contains modules that were not installed by this version of Asterisk. Please ensure that these modules are compatible with this version before attempting to run Asterisk. app_addon_sql_mysql.so app_rxfax.so app_saycountpl.so app_striplsd.so app_substring.so app_txfax.so cdr_addon_mysql.so chan_modem_aopen.so chan_modem_bestdata.so chan_modem_i4l.so chan_modem.so format_mp3.so res_config_mysql.so WARNING WARNING WARNING Do not understand how to fix this? Do not know if that would also be related to the ops crashing. Dan ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Re: Lockups since upgrade 1.2.3 - anyone else? Any ideas?
Hi Brent - > Boy oh boy. This blows. I upgraded to 1.2.2 from 1.0.9, and of course had > the timebomb bug. Immediately after upgrading to 1.2.3 we were ok, for 24 > hours or so. > > Since upgrading to 1.2.3, though, the whole system has locked up twice. Once > on Thursday, and then about a half hour ago. The server would reply to a > ping, but no ssh login, no local console login - just locked up. This ain't > good for business. We've been doing fine with 1.2.3 so far. No problems reported, though I only have it deployed in a small office. Definitely no lock-ups. On the asterisk side, just a basic question - did you make sure to remove the old modules so the new 1.2.3 versions got installed? As far as the lockups, maybe it is coincidental? I've never had asterisk (even the crazy CVS versions) lock a whole OS like that. I have had machines running asterisk lock up, but it always turned out to be caused by something else like bad hardware, or unrelated network problems. - Noah ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
