Hi all, as mentioned in http://wiki.freeswitch.org/wiki/Using_ODBC_in_the_core#PostgreSQL_8.4_on_Deb... seem to be some stability issues with the unixODBC package coming with Debian. I heard this is still valid for Wheezy too so I was just contacting the package maintainer who was quite surprised to hear about this issue. Obviously nobody told him before which is why Wheezy still uses unixODBC version 2.2. Now that we have a freeze for Wheezy to prepare for the official release unixODBC 2.3 can't be included anymore. However version 2.2 could get a patch if we are able to provide enough information about the root cause. So this is a chance for FreeSwitch's own packages to work really smooth with Debian without any manual correction needed ;-) Would anybody be able to provide more advanced information, for instance a backtrace and instructions on how to reproduce the issue? Cheers, Julian
The link has Postgres in the hashtag. Does that mean you're specifically interested in postgres? If so, that's now accessible directly via freeswitch without odbc middleware. -Avi On Wed, Jan 23, 2013 at 8:19 PM, Julian Pawlowski < julian.pawlowski@gmail.com> wrote:
Hi all,
as mentioned in http://wiki.freeswitch.org/wiki/Using_ODBC_in_the_core#PostgreSQL_8.4_on_Deb... seem to be some stability issues with the unixODBC package coming with Debian.
I heard this is still valid for Wheezy too so I was just contacting the package maintainer who was quite surprised to hear about this issue. Obviously nobody told him before which is why Wheezy still uses unixODBC version 2.2.
Now that we have a freeze for Wheezy to prepare for the official release unixODBC 2.3 can't be included anymore. However version 2.2 could get a patch if we are able to provide enough information about the root cause. So this is a chance for FreeSwitch's own packages to work really smooth with Debian without any manual correction needed ;-)
Would anybody be able to provide more advanced information, for instance a backtrace and instructions on how to reproduce the issue?
Cheers, Julian
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi Avi, On Wed, Jan 23, 2013 at 7:57 PM, Avi Marcus <avi@avimarcus.net> wrote:
The link has Postgres in the hashtag. Does that mean you're specifically interested in postgres?
No. Postgres is only an example (in fact we are using MySQL as of now).
If so, that's now accessible directly via freeswitch without odbc middleware.
I know. My email is not regarding to to run FreeSwitch with a database directly or via ODBC middleware, it's about the bug that was noted there: "*We've experienced some major stability issues with the unixODBC-debian-package 2.2.14p2-1 from the repository. FreeSWITCH would die anywhere between a few days to weeks. Upgrading to a manually compiled unixODBC 2.3.0-pre fixed this problem and has been tested stable for the last 2 months. --Peletiah <http://wiki.freeswitch.org/wiki/User:Peletiah> 13:04, 4 February 2012 (UTC)"* Now re-read my message with new glases :-) Cheers, Julian
I had stability issues with unixODBC-2.2.14-12 on CentOS 6. Adding Threading = 0 to my /etc/odbcinst.ini fixed the issues I was having. Colin From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Julian Pawlowski Sent: Wednesday, January 23, 2013 3:08 PM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Debian unixODBC issues Hi Avi, On Wed, Jan 23, 2013 at 7:57 PM, Avi Marcus <avi@avimarcus.net<mailto:avi@avimarcus.net>> wrote: The link has Postgres in the hashtag. Does that mean you're specifically interested in postgres? No. Postgres is only an example (in fact we are using MySQL as of now). If so, that's now accessible directly via freeswitch without odbc middleware. I know. My email is not regarding to to run FreeSwitch with a database directly or via ODBC middleware, it's about the bug that was noted there: "We've experienced some major stability issues with the unixODBC-debian-package 2.2.14p2-1 from the repository. FreeSWITCH would die anywhere between a few days to weeks. Upgrading to a manually compiled unixODBC 2.3.0-pre fixed this problem and has been tested stable for the last 2 months. --Peletiah<http://wiki.freeswitch.org/wiki/User:Peletiah> 13:04, 4 February 2012 (UTC)" Now re-read my message with new glases :-) Cheers, Julian
Hi Colin, On Wed, Jan 23, 2013 at 9:14 PM, Colin Mason <cmason@frontiernetworks.ca>wrote:
I had stability issues with unixODBC-2.2.14-12 on CentOS 6. Adding Threading = 0 to my /etc/odbcinst.ini fixed the issues I was having.
Thanks a lot for the hint! We haven't tried this yet but it sounds promising after reading http://wiki.freeswitch.org/wiki/Using_ODBC_in_the_core#.2Fetc.2Fodbcinst.ini... "Also note, (see bug below on bottom of page); If you are using the FreeSWITCH pooled resources, then you definitely need Threading = 0 for high call volume. What this does is it "disables a global mutex in the ODBC core that only allows 1 concurrent operation per process regardless of the concurrent connections." (i.e. It slows down when you have too many connections trying at one time)" Let's see if this actually helps. It could be that Threading=0 is default in unixODBC version 2.3 and that is why changing to that version resolved that issue. Br Julian
Personally I'm using FS + unixODBC + myODBC for MySQL with no stability issues. It should be fine. If you do get issues report them on the Debian BTS - I'm sure they'd get it fixed, either by an updated package or backporting a fix to the current version. Bugs only get fixed if they're reported to the correct place people! The only time I have had problems was last week - it turned out I had a Percona APT repository installed and accidentally had installed a different libmysqlclient18 from the one that myodbc was compiled against (that one connected fine but did a segfault on any query). Perhaps Peletiah had some such problem, or was using a driver other than myODBC. In any case I don't think you'll find problems with myODBC, but obviously test before rolling into production. Wheezy is still 'testing' and shouldn't be on a production machine yet anyway, if you need newer packages check squeeze-backports ( http://backports.debian.org/) first. -Steve On 23 January 2013 20:08, Julian Pawlowski <mail@loredo.me> wrote:
Hi Avi,
On Wed, Jan 23, 2013 at 7:57 PM, Avi Marcus <avi@avimarcus.net> wrote:
The link has Postgres in the hashtag. Does that mean you're specifically interested in postgres?
No. Postgres is only an example (in fact we are using MySQL as of now).
If so, that's now accessible directly via freeswitch without odbc middleware.
I know. My email is not regarding to to run FreeSwitch with a database directly or via ODBC middleware, it's about the bug that was noted there: "*We've experienced some major stability issues with the unixODBC-debian-package 2.2.14p2-1 from the repository. FreeSWITCH would die anywhere between a few days to weeks. Upgrading to a manually compiled unixODBC 2.3.0-pre fixed this problem and has been tested stable for the last 2 months. --Peletiah <http://wiki.freeswitch.org/wiki/User:Peletiah> 13:04, 4 February 2012 (UTC)"*
Now re-read my message with new glases :-)
Cheers, Julian
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi Steve, On Wed, Jan 23, 2013 at 9:20 PM, Steven Ayre <steveayre@gmail.com> wrote:
Personally I'm using FS + unixODBC + myODBC for MySQL with no stability issues. It should be fine.
The issue occurs under higher loads or peaks, nothing you will notice in any small business or home environments.
If you do get issues report them on the Debian BTS - I'm sure they'd get it fixed, either by an updated package or backporting a fix to the current version. Bugs only get fixed if they're reported to the correct place people!
Actually this is nearly what I did already, you should have read my first message more carefully. It is about requesting more information about the issue if anybody has those, not about asking for support to resolve the issue. We know that this is caused by unixODBC already but not exactly at which point and why it helps to install an newer version. The maintainer of the Debian package asked me to provide more information so that he can understand the issue in detail to create a patch for the package in Wheezy.
In any case I don't think you'll find problems with myODBC, but obviously test before rolling into production.
As said, the issue is with unixODBC, not the myODBC connector which is a different thing.
Wheezy is still 'testing' and shouldn't be on a production machine yet anyway, if you need newer packages check squeeze-backports ( http://backports.debian.org/) first.
I know. However, Wheezy in currently preparing go-live and becoming the stable stamp. We are currently doing systems integration for the Gemeinschaft PBX appliance which is going to use Wheezy as a standard in the near future. Regards, Julian
On 23 January 2013 20:33, Julian Pawlowski <mail@loredo.me> wrote:
On Wed, Jan 23, 2013 at 9:20 PM, Steven Ayre <steveayre@gmail.com> wrote:
Personally I'm using FS + unixODBC + myODBC for MySQL with no stability issues. It should be fine.
The issue occurs under higher loads or peaks, nothing you will notice in any small business or home environments.
UP 0 years, 126 days, 19 hours, 37 minutes, 42 seconds, 994 milliseconds, 957 microseconds FreeSWITCH is ready 42124396 session(s) since startup If you do get issues report them on the Debian BTS - I'm sure they'd get
it fixed, either by an updated package or backporting a fix to the current version. Bugs only get fixed if they're reported to the correct place people!
Actually this is nearly what I did already, you should have read my first message more carefully. It is about requesting more information about the issue if anybody has those, not about asking for support to resolve the issue. We know that this is caused by unixODBC already but not exactly at which point and why it helps to install an newer version.
I actually intended that about whoever added the note to the Wiki since the debian maintainer obviously hadn't heard from them. If the note on the Wiki is from you, apologies. The maintainer of the Debian package asked me to provide more information
so that he can understand the issue in detail to create a patch for the package in Wheezy.
If FS coredumps within unixODBC try: http://wiki.freeswitch.org/wiki/Reporting_Bugs#Creating_A_Backtrace_With_gdb... If a simple program can be written that demonstrates the same instability, then even better since the backtrace then might be more readable. If it's only under high load then it could be thread related so you'd need to reproduce that. In any case I don't think you'll find problems with myODBC, but obviously
test before rolling into production.
As said, the issue is with unixODBC, not the myODBC connector which is a different thing.
I said myODBC since I haven't used unixODBC with any of the other connectors personally. Even if the crash appears to be in unixODBC it could still be in the connector used too since that code is called from unixODBC and could be some mismatch between what they're doing. -Steve
participants (5)
-
Avi Marcus
-
Colin Mason
-
Julian Pawlowski
-
Julian Pawlowski
-
Steven Ayre