12 May
2006
12 May
'06
12:47 p.m.
I just upgraded one of my proxies from SER (0.8.12) and MySQL (4.0.20-0) to
SER (0.9.6-6) and MySQL (4.1.19-0). I have a custom module for ser that I
have rebulit using the 0.9.6 source and can bring up ser, but cannot make
any calls. I can register my UA with ser, but get immediate 404 not found
fast busy when attempting to make a call. I am 99% sure that this is
because my database access is not happening, but am not seeing any messages
in /var/log/messages.
Any suggestions??
12 May
12 May
1:01 p.m.
There are a few points I can suggest
First, your connection info inside ser.cfg must be updated from
sql://ser:heslo@localhost/ser to mysql://ser:heslo@localhost/ser
Second, you'll have to update the database by running ser_mysql.sh scipt.
Best of luck,
Andrey.
On 5/12/06, Stephen Helfen <steve_helfen(a)hotmail.com> wrote:
I just upgraded one of my proxies from SER (0.8.12)
and MySQL (4.0.20-0) to
SER (0.9.6-6) and MySQL (4.1.19-0). I have a custom module for ser that I
have rebulit using the 0.9.6 source and can bring up ser, but cannot make
any calls. I can register my UA with ser, but get immediate 404 not found
fast busy when attempting to make a call. I am 99% sure that this is
because my database access is not happening, but am not seeing any messages
in /var/log/messages.
Any suggestions??
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
1:57 p.m.
I figured out that the ser.cfg file being read was the one created by my
local ser build. The biggest negative effect from this is that my errors
are now no longer being written to /var/log/messages. Where do I need to
look in the source code to find either where the errors are being written,
or to reset ser to write the error messages to /var/log/messages, again.
Thanks in advance.
From: "Andrey Kouprianov"
<andrey.kouprianov(a)gmail.com>
To: serusers(a)lists.iptel.org
Subject: Re: [Serusers] SER cannot connect to MySQL after upgrade
Date: Fri, 12 May 2006 23:01:12 +0700
There are a few points I can suggest
First, your connection info inside ser.cfg must be updated from
sql://ser:heslo@localhost/ser to mysql://ser:heslo@localhost/ser
Second, you'll have to update the database by running ser_mysql.sh scipt.
Best of luck,
Andrey.
On 5/12/06, Stephen Helfen <steve_helfen(a)hotmail.com> wrote:
I just upgraded one of my proxies from SER
(0.8.12) and MySQL (4.0.20-0)
to
SER (0.9.6-6) and MySQL (4.1.19-0). I have a custom module for ser that I
have rebulit using the 0.9.6 source and can bring up ser, but cannot make
any calls. I can register my UA with ser, but get immediate 404 not found
fast busy when attempting to make a call. I am 99% sure that this is
because my database access is not happening, but am not seeing any
messages
in /var/log/messages.
Any suggestions??
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
2:14 p.m.
It should be /var/log/messages anyway, unless there was some special
config that you applied before.
On 5/12/06, Stephen Helfen <steve_helfen(a)hotmail.com> wrote:
I figured out that the ser.cfg file being read was the
one created by my
local ser build. The biggest negative effect from this is that my errors
are now no longer being written to /var/log/messages. Where do I need to
look in the source code to find either where the errors are being written,
or to reset ser to write the error messages to /var/log/messages, again.
Thanks in advance.
From: "Andrey Kouprianov"
<andrey.kouprianov(a)gmail.com>
To: serusers(a)lists.iptel.org
Subject: Re: [Serusers] SER cannot connect to MySQL after upgrade
Date: Fri, 12 May 2006 23:01:12 +0700
There are a few points I can suggest
First, your connection info inside ser.cfg must be updated from
sql://ser:heslo@localhost/ser to mysql://ser:heslo@localhost/ser
Second, you'll have to update the database by running ser_mysql.sh scipt.
Best of luck,
Andrey.
On 5/12/06, Stephen Helfen <steve_helfen(a)hotmail.com> wrote:
I just upgraded one of my proxies from SER
(0.8.12) and MySQL (4.0.20-0)
to
SER (0.9.6-6) and MySQL (4.1.19-0). I have a custom module for ser that I
have rebulit using the 0.9.6 source and can bring up ser, but cannot make
any calls. I can register my UA with ser, but get immediate 404 not found
fast busy when attempting to make a call. I am 99% sure that this is
because my database access is not happening, but am not seeing any
messages
in /var/log/messages.
Any suggestions??
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6704
days inactive
6704
days old
3 comments
2 participants
participants (2)
-
Andrey Kouprianov -
Stephen Helfen