asterisk users - Jun 2020 - CDR mysql: timeout when remote database unavailable

> On 2020-06-06 10:38, Antony Stone wrote:
> On Saturday 06 June 2020 at 09:18:11, Fourhundred Thecat wrote:
>
>> In a situation when I start asterisk, and the remote database is
>> unreachable, asterisk waits for several minutes before it actually
>> starts (before it loads sip module, etc).
>>
>> And when database is unreachable during operation, when call happens,
>> sometimes the call is connected, other times it waits for mysql and
call
>> times out.
>
>> or what would be the best solution in my case ?
>
> I would install a local copy of MySQL (to the same machine as Asterisk) so
> that it is definitely available, tell Asterisk to write to that, and then
set
> up replication to the remote MySQL instance which is sometimes unavailable.
That is an interesting suggestion, which I'll consider.

But I would still like to know where the Aterisk mysql timeout duration
comes from, and whether it can be configured.

thanks,

Isn't the MySQL stuff deprecated in favor of odbc?  You may be barking up
the wrong tree if you plan to make source changes.

j

On Sun, Jun 7, 2020, 1:55 AM Fourhundred Thecat <400thecat at gmx.ch>
wrote:
>  > On 2020-06-06 10:38, Antony Stone wrote:
> > On Saturday 06 June 2020 at 09:18:11, Fourhundred Thecat wrote:
> >
> >> In a situation when I start asterisk, and the remote database is
> >> unreachable, asterisk waits for several minutes before it actually
> >> starts (before it loads sip module, etc).
> >>
> >> And when database is unreachable during operation, when call
happens,
> >> sometimes the call is connected, other times it waits for mysql
and call
> >> times out.
> >
> >> or what would be the best solution in my case ?
> >
> > I would install a local copy of MySQL (to the same machine as
Asterisk)
> so
> > that it is definitely available, tell Asterisk to write to that, and
> then set
> > up replication to the remote MySQL instance which is sometimes
> unavailable.
>
> That is an interesting suggestion, which I'll consider.
>
> But I would still like to know where the Aterisk mysql timeout duration
> comes from, and whether it can be configured.
>
> thanks,
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200607/a9426571/attachment.html>

On 6/7/2020 2:54 AM, Fourhundred Thecat wrote:
> I would still like to know where the Aterisk mysql timeout duration
> comes from, and whether it can be configured.
In the case of cdr_mysql, the connect timeout is configurable by putting 
the following in cdr_mysql.conf:

[global]
timeout = 5 ; Set connect timeout to 5 seconds

For app_mysql, setting the connection timeout is shown in the documentation:

*CLI> core show application MYSQL

Kind regards,
Sean

> On 2020-06-08 16:37, Sean Bright wrote:
>
> In the case of cdr_mysql, the connect timeout is configurable by putting
> the following in cdr_mysql.conf:
>
> [global]
> timeout = 5 ; Set connect timeout to 5 seconds
OK, so i changed the timeout to 2 sec, but it does not have the desired
effect. I expected, if mysql cannot be reached, after 2 seconds the call
will progress normally.

Instead, the call still terminates if mysql cannot be reached.

Is it possible to set in asterisk, if mysql is unreachable then skip the
step and simply ignore mysql logging ?