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 | [EM
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, lo
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
be
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 f
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
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 t
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 d
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 t
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
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
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
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
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/li
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 i
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 m
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 h
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
17 matches
Mail list logo