Your database odbc links may or may not provide fallback options, but (I'm
just thinking out loud here) the odbc connection entity should be pointing
to something that can handle the failover.
On Wed, Apr 24, 2013 at 10:56 AM, Cyrille Bollu <cyrille.bo...@belnet.be>wrote:
> Hi list,
>
> I'm trying to find out how I could setup OTRS to use a redundant ODBC
> backend for CustomerUser objects.
>
> I initially thought I could setup 2 backends pointing to 2 mirrored mysql
> servers. But, it seems that OTRS' code dies with a nice HTTP 500 error when
> a backend isn't available.
>
> Has anyone already worked on such a setup?
>
> I remember doing such a setup for agents authentication with an LDAP
> backend using the following in config.pm:
>
> # LDAP agent backend
> my @ldaphosts = ('ldap2','ldap1');
> $Self->{'AuthModule'} = 'Kernel::System::Auth::LDAP';
> $Self->{'AuthModule::LDAP::**Host'} = \@ldaphosts;
> ...
>
> And it seem to work fine at that time.
>
> Now, is there an easy solution for ODBC backends?
>
> Best regards,
>
> Cyrille
> ------------------------------**------------------------------**---------
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive:
> http://lists.otrs.org/**pipermail/otrs<http://lists.otrs.org/pipermail/otrs>
> To unsubscribe:
> http://lists.otrs.org/cgi-bin/**listinfo/otrs<http://lists.otrs.org/cgi-bin/listinfo/otrs>
>
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
