Hi henning,
I'm happy you enjoyed the beer. ;-)
I'm attaching some back traces from the core dump. I don't know C programming so I can't go further than that :-(
I will try also the odbc driver.
Thank you for the help
Best wishes for 2010
Alex
On Thu, December 31, 2009 10:55 am, alex pappas wrote:
> [..]
Hey Alex,
the restaurant was nice, the beer is indeed good there. :-)
Good that you managed to find the correct syntax.
> I just manage to connect with oracle with the following URL :
>
> modparam("sqlops","sqlcon","ca=>oracle://user:pass@alex.gr/cid_name.alex.gr
> ")
This is probably caused from a segfault which caused a core dump. :-(
> Now I run into other problems. The same query that from ./kamailio_orasel
> give me result, when I try that from kamailio.cfg I get an error and
> after that the system is getting very high load.
After this the system is busy to write the core file with the memory dump
to the disk, which can get really huge depending on the process number and
shared memory size. Do you managed to find some core dump? They should
located in the working directory of the server.
The oracle module is probably one of the DB modules which has got the
> The error is :
>
> kernel: kamailio[12442]: segfault at 0000000000000010 rip 00002b1b42952764
> rsp 00007fff6b144d30 error 4
>
> Does anyone had the same issue ?
least testing, due its dependencies. But i think they are some people
which successful using it. The next step would be to investigate the
backtrace from the core dump.
Another option would be to setup an unixodbc connection on the DB side and
then connect which the db_unixodbc module instead.
Regards,
Henning