Henning, how can I configure Kamailio to use some other path to find modules? i should make modules differently as well, right?
I'll copy back the list so anyone can answer that.
Rgds, Uriel
On Wed, Jul 1, 2009 at 9:35 AM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Mittwoch, 1. Juli 2009, you wrote:
It's a CentOS 5.3 i386.
# gcc --version gcc (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
# uname -a Linux sbci1pri.cpsnet.com.ar 2.6.18-92.1.18.el5 #1 SMP Wed Nov 12
09:30:27
EST 2008 i686 i686 i386 GNU/Linux
Hi Uriel,
thanks, but this is all fairly common, so i doubt your environment is guilty here.
Do you have some guidelines to erase all Kamailio files from the system? I'm sure its a build problem.
Sorry, this depends where you installed the server, you basically need to track all files that were installed. I missed the "make uninstall" also a few times. :/
But you could just try to install the new version in another directory, like /tmp/kamailio or something like this. If you then configure the server to only use modules from this dir it should be not conflict with the old installation.
Henning
Hello,
Henning, how can I configure Kamailio to use some other path to find modules? i should make modules differently as well, right?
Use mpath="/your_modules_path" before loadmodule.
Saludos JesusR.
On Wed, Jul 1, 2009 at 9:35 AM, Henning Westerholt <henning.westerholt@1und1.de
wrote:
On Mittwoch, 1. Juli 2009, you wrote:
It's a CentOS 5.3 i386.
# gcc --version gcc (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions.
There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
# uname -a Linux sbci1pri.cpsnet.com.ar 2.6.18-92.1.18.el5 #1 SMP Wed Nov 12
09:30:27
EST 2008 i686 i686 i386 GNU/Linux
Hi Uriel,
thanks, but this is all fairly common, so i doubt your environment is guilty here.
Do you have some guidelines to erase all Kamailio files from the
system?
I'm sure its a build problem.
Sorry, this depends where you installed the server, you basically need to track all files that were installed. I missed the "make uninstall" also a few times. :/
But you could just try to install the new version in another directory, like /tmp/kamailio or something like this. If you then configure the server to only use modules from this dir it should be not conflict with the old installation.
Henning
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Saludos JesusR.
------------------------------------ Jesus Rodriguez VozTelecom Sistemas, S.L. jesusr@voztele.com http://www.voztele.com Tel. 902360305 -------------------------------------
Hi,
And how can I make modules on that location as well? So i don´t have to copy them from default location.
Saludos, Uriel
On Thu, Jul 2, 2009 at 9:19 AM, Jesus Rodriguez jesusr@voztele.com wrote:
Hello,
Henning, how can I configure Kamailio to use some other path to find
modules? i should make modules differently as well, right?
Use mpath="/your_modules_path" before loadmodule.
Saludos JesusR.
On Wed, Jul 1, 2009 at 9:35 AM, Henning Westerholt <
henning.westerholt@1und1.de> wrote: On Mittwoch, 1. Juli 2009, you wrote:
It's a CentOS 5.3 i386.
# gcc --version gcc (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
# uname -a Linux sbci1pri.cpsnet.com.ar 2.6.18-92.1.18.el5 #1 SMP Wed Nov 12
09:30:27
EST 2008 i686 i686 i386 GNU/Linux
Hi Uriel,
thanks, but this is all fairly common, so i doubt your environment is guilty here.
Do you have some guidelines to erase all Kamailio files from the system? I'm sure its a build problem.
Sorry, this depends where you installed the server, you basically need to track all files that were installed. I missed the "make uninstall" also a few times. :/
But you could just try to install the new version in another directory, like /tmp/kamailio or something like this. If you then configure the server to only use modules from this dir it should be not conflict with the old installation.
Henning
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Saludos JesusR.
Jesus Rodriguez VozTelecom Sistemas, S.L. jesusr@voztele.com http://www.voztele.com Tel. 902360305
On Donnerstag, 2. Juli 2009, you wrote:
And how can I make modules on that location as well? So i don´t have to copy them from default location.
Hi Uriel,
make prefix=/tmp/foobar make prefix=/tmp/foobar modules make prefix=/tmp/foobar install
To be save do a make distclean before building with a different prefix.
Cheers,
Henning
Henning,
I created a new directory and ran the following: make distclean make prefix=/opt/kamailio/ make prefix=/opt/kamailio/ modules make prefix=/opt/kamailio/ install
Then I tried to run kamailio and still get the same error: ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version")
Something else is messing with the code; anyway that we should be able to workaround.
Let me know if you think about something. Uriel
On Thu, Jul 2, 2009 at 10:14 AM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Donnerstag, 2. Juli 2009, you wrote:
And how can I make modules on that location as well? So i don´t have to copy them from default location.
Hi Uriel,
make prefix=/tmp/foobar make prefix=/tmp/foobar modules make prefix=/tmp/foobar install
To be save do a make distclean before building with a different prefix.
Cheers,
Henning
You are using an old version of the DB...
If it's possible, create a new DB to use in Your tests, if not, to work, You will have to migrate actual DB schema to the new one.
Edson.
Uriel Rozenbaum escreveu:
Henning,
I created a new directory and ran the following: make distclean make prefix=/opt/kamailio/ make prefix=/opt/kamailio/ modules make prefix=/opt/kamailio/ install
Then I tried to run kamailio and still get the same error: ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version")
Something else is messing with the code; anyway that we should be able to workaround.
Let me know if you think about something. Uriel
On Thu, Jul 2, 2009 at 10:14 AM, Henning Westerholt <henning.westerholt@1und1.de mailto:henning.westerholt@1und1.de> wrote:
On Donnerstag, 2. Juli 2009, you wrote: > And how can I make modules on that location as well? So i don´t have to > copy them from default location. Hi Uriel, make prefix=/tmp/foobar make prefix=/tmp/foobar modules make prefix=/tmp/foobar install To be save do a make distclean before building with a different prefix. Cheers, Henning
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Hi Edson,
I already generated a new DB (with the kam script) and migrated the data and am trying to make it work with that.
I obviously did not change anything on the version table so the versions match.
Regards, Uriel
On Thu, Jul 2, 2009 at 3:33 PM, Edson - Lists 4lists@gmail.com wrote:
You are using an old version of the DB...
If it's possible, create a new DB to use in Your tests, if not, to work, You will have to migrate actual DB schema to the new one.
Edson.
Uriel Rozenbaum escreveu:
Henning,
I created a new directory and ran the following: make distclean make prefix=/opt/kamailio/ make prefix=/opt/kamailio/ modules make prefix=/opt/kamailio/ install
Then I tried to run kamailio and still get the same error: ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version")
Something else is messing with the code; anyway that we should be able to workaround.
Let me know if you think about something. Uriel
On Thu, Jul 2, 2009 at 10:14 AM, Henning Westerholt < henning.westerholt@1und1.de mailto:henning.westerholt@1und1.de> wrote:
On Donnerstag, 2. Juli 2009, you wrote: > And how can I make modules on that location as well? So i don´t have to > copy them from default location.
Hi Uriel,
make prefix=/tmp/foobar make prefix=/tmp/foobar modules make prefix=/tmp/foobar install
To be save do a make distclean before building with a different prefix.
Cheers,
Henning
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Donnerstag, 2. Juli 2009, you wrote:
[..] Then I tried to run kamailio and still get the same error: ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version")
Something else is messing with the code; anyway that we should be able to workaround.
Hi Uriel,
with help from the binary build and the sample configuration you provided me i was able to find the problem. It turned out to be a rather simple error in the DB connection code, only the error messages were really misleading. :-/
I've commited a fix to the branch 1.5, thanks a lot for your help in debugging this problem!
Henning
Great Henning!
How can i get the binaries for that branch? :)
On Mon, Jul 6, 2009 at 12:27 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Donnerstag, 2. Juli 2009, you wrote:
[..] Then I tried to run kamailio and still get the same error: ERROR:core:db_check_table_version: invalid version 2 for table carrierfailureroute found, expected 3 (check table structure and table "version")
Something else is messing with the code; anyway that we should be able to workaround.
Hi Uriel,
with help from the binary build and the sample configuration you provided me i was able to find the problem. It turned out to be a rather simple error in the DB connection code, only the error messages were really misleading. :-/
I've commited a fix to the branch 1.5, thanks a lot for your help in debugging this problem!
Henning
On Montag, 6. Juli 2009, Uriel Rozenbaum wrote:
How can i get the binaries for that branch? :)
Just checkout from svn, with
svn checkout http://devel.kamailio.org/svn/branches/1.5
Then you can build as usual. The soon to be released 1.5.2 will of course also contain this fix.
Henning
-
Edson - Lists -
Henning Westerholt -
Jesus Rodriguez -
Uriel Rozenbaum