Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-12 Thread Jonathan H 
Or better still, skip straight to the current LTS version 16 which was
release a few days ago, supported right through until 10-2023!

If you're going to do a big upgrade, might as well leap onto the
current release :)

https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
On Fri, 12 Oct 2018 at 09:40, Jonas Kellens  wrote:
>
> Hello
>
> thank you for your answer.
>
> This does not happen all the time. It happens about once every 4 months. I 
> just can not pinpoint WHEN exactly it occurs. I just see in the verbose 
> logfile that it occurs after a MYSQL insert/update/delete statement.
>
> If Asterisk 13 handels MYSQL connections in a better way, then indeed I 
> should look for upgrade.
>
>
>
> Kind regards.
>
>
>
> Op 05-10-18 om 01:25 schreef John Novack:
>
> As others have said, clearly it ISN'T "just working" or you would not have 
> posted the question
>
> To state again, I am using Version 13, though a few minor revisions behind, 
> with MySql, on CentOS 6 and have no rebooting or other MySql related issues
>
> Clearly you need to state in more detail what issues remain, once you migrate 
> to AT LEAST 13.xx, and state your OS after becoming current with Asterisk, 
> MySql and the OS
>
> I use MySql on every incoming call, and also maintain call detail records in 
> MySql for every call, and it just simply works, and has for some time.
>
> Although I may be using it quite differently that you, it simply works.
> Is this a newly developing issue, or has it persisted for some time
> What if any changes have been made to the dialplan etc?
>
> Have you considered a strictly hardware issue? Memory? HD? MB??
>
> The crystal ball is very cloudy on this one!
>
> John Novack
>
>
> Jonas Kellens wrote:
>
> Hello
>
> thank you for your answer.
>
> If I read your (and others) reaction correctly I can conclude that this is an 
> Asterisk problem and not a problem of MySQL or dialplan logic ?
>
>
> You should know that the MySQL database is heavily questioned :
>
>
> mysql> show status like '%onn%';
> +--++
> | Variable_name| Value  |
> +--++
> | Aborted_connects | 469|
> | Connections  | 132762 |
> | Max_used_connections | 8  |
> | Ssl_client_connects  | 0  |
> | Ssl_connect_renegotiates | 0  |
> | Ssl_finished_connects| 0  |
> | Threads_connected| 3  |
> +--++
> 7 rows in set (0.00 sec)
>
>
>
> I stick to 1.8 because it just works. I had some issues with version 11 and 
> 13 in the past.
>
>
> Regards
>
> Jonas.
>
>
> Op 04-10-18 om 17:49 schreef John Novack:
>
> Woefully out of date.
> You really need to put your efforts into at least a modest upgrade
> I use version 13 with MySql queries built into the dialplan on CentOs 6 and 
> have NO such issues, either performance or any restart or reboot. It simply 
> works
>
> I never used either 1.6 or 1.8, going from 1.4 to version 11, which did 
> require some syntax changes to the dialplan.
>
> Given that even version 11 is EOL, you really need to put your efforts into 
> doing the migration rather than tracking this one down
>
> JMO
>
> John Novack
>
>
>
> Jonas Kellens wrote:
>
> Hello
>
> using Asterisk 1.8.32.
>
> I notice that there is a spontaneous reboot of the Asterisk system from time 
> to time.
>
> When I look in the logs (verbose file) I noticed that every time this occurs 
> it's at a moment that there is a MySQL action, be it a lookup or an 
> insert/update/delete.
>
> I must say I do have some MySQL queries that occur in my dialplan when a call 
> comes in, to look up different actions to perform on this call.
>
>
> An idea how to overcome this problem ? Seems a "performance" issue, no ?!
>
> Is it better to have these MySQL queries to be done by an external script 
> (like a php script that I call with the System()-command or a 
> SHELL()-command) ?
>
>
> Here are some examples from the verbose file.
>
>
>
> [Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing 
> [s@sub-GetAlertInfo:3] MYSQL("SIP/SipAgenT01-317d", "Connect connid 
> localhost myuser mypwd myDB") in new stack
> [Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing 
> [s@sub-GetAlertInfo:5] MYSQL("SIP/SipAgenT01-317d", "Query resultid 1 
> SELECT uri, callinfo FROM distringtone WHERE onoff='1'") in new stack
> [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
> '/etc/asterisk/logger.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 
> 22 15:19:18]   == Found
> [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
> '/etc/asterisk/asterisk.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 
> 22 15:19:18]   == Found
> [Aug 22 15:19:18] VERBOSE[3306] manager.c: [Aug 22 15:19:18]   == Manager 
> registered action DataGet
> [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
>

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-12 Thread Antony Stone 
On Friday 12 October 2018 at 10:38:49, Jonas Kellens wrote:

> Hello
> 
> thank you for your answer.
> 
> This does not happen all the time. It happens about once every 4 months.
> I just can not pinpoint WHEN exactly it occurs. I just see in the
> verbose logfile that it occurs after a MYSQL insert/update/delete
> statement.
> 
> If Asterisk 13 handels MYSQL connections in a better way, then indeed I
> should look for upgrade.

More significantly, the ODBC driver is generally commented on as being a better 
connector than the MySQL-specific one; I think that's where you're more likely 
to see the improvement.

Regards,


Antony.

> Op 05-10-18 om 01:25 schreef John Novack:
> > As others have said, clearly it ISN'T "just working" or you would not
> > have posted the question
> > 
> > To state again, I am using Version 13, though a few minor revisions
> > behind, with MySql, on CentOS 6 and have no rebooting or other MySql
> > related issues
> > 
> > Clearly you need to state in more detail what issues remain, once you
> > migrate to AT LEAST 13.xx, and state your OS after becoming current
> > with Asterisk, MySql and the OS
> > 
> > I use MySql on every incoming call, and also maintain call detail
> > records in MySql for every call, and it just simply works, and has for
> > some time.
> > 
> > Although I may be using it quite differently that you, it simply works.
> > Is this a newly developing issue, or has it persisted for some time
> > What if any changes have been made to the dialplan etc?
> > 
> > Have you considered a strictly hardware issue? Memory? HD? MB??
> > 
> > The crystal ball is very cloudy on this one!
> > 
> > John Novack
> > 
> > Jonas Kellens wrote:
> >> Hello
> >> 
> >> thank you for your answer.
> >> 
> >> If I read your (and others) reaction correctly I can conclude that
> >> this is an Asterisk problem and not a problem of MySQL or dialplan
> >> logic ?
> >> 
> >> 
> >> You should know that the MySQL database is heavily questioned :
> >> 
> >> 
> >> mysql> show status like '%onn%';
> >> +--++
> >> 
> >> | Variable_name| Value  |
> >> 
> >> +--++
> >> 
> >> | Aborted_connects | 469|
> >> | Connections  | 132762 |
> >> | Max_used_connections | 8  |
> >> | Ssl_client_connects  | 0  |
> >> | Ssl_connect_renegotiates | 0  |
> >> | Ssl_finished_connects| 0  |
> >> | Threads_connected| 3  |
> >> 
> >> +--++
> >> 7 rows in set (0.00 sec)
> >> 
> >> 
> >> 
> >> I stick to 1.8 because it just works. I had some issues with version
> >> 11 and 13 in the past.
> >> 
> >> 
> >> Regards
> >> 
> >> Jonas.
> >> 
> >> Op 04-10-18 om 17:49 schreef John Novack:
> >>> Woefully out of date.
> >>> You really need to put your efforts into at least a modest upgrade
> >>> I use version 13 with MySql queries built into the dialplan on
> >>> CentOs 6 and have NO such issues, either performance or any restart
> >>> or reboot. It simply works
> >>> 
> >>> I never used either 1.6 or 1.8, going from 1.4 to version 11, which
> >>> did require some syntax changes to the dialplan.
> >>> 
> >>> Given that even version 11 is EOL, you really need to put your
> >>> efforts into doing the migration rather than tracking this one down
> >>> 
> >>> JMO
> >>> 
> >>> John Novack
> >>> 
> >>> Jonas Kellens wrote:
>  Hello
>  
>  using Asterisk 1.8.32.
>  
>  I notice that there is a spontaneous reboot of the Asterisk system
>  from time to time.
>  
>  When I look in the logs (verbose file) I noticed that every time
>  this occurs it's at a moment that there is a MySQL action, be it a
>  lookup or an insert/update/delete.
>  
>  I must say I do have some MySQL queries that occur in my dialplan
>  when a call comes in, to look up different actions to perform on
>  this call.
>  
>  
>  An idea how to overcome this problem ? Seems a "performance" issue,
>  no ?!
>  
>  Is it better to have these MySQL queries to be done by an external
>  script (like a php script that I call with the System()-command or
>  a SHELL()-command) ?

-- 
Users don't know what they want until they see what they get.

   Please reply to the list;
 please *don't* CC me.

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Astricon is coming up October 9-11!  Signup is available at: 
https://www.asterisk.org/community/astricon-user-conference

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:

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-12 Thread Jonas Kellens 

Hello

thank you for your answer.

This does not happen all the time. It happens about once every 4 months. 
I just can not pinpoint WHEN exactly it occurs. I just see in the 
verbose logfile that it occurs after a MYSQL insert/update/delete statement.


If Asterisk 13 handels MYSQL connections in a better way, then indeed I 
should look for upgrade.




Kind regards.



Op 05-10-18 om 01:25 schreef John Novack:
As others have said, clearly it ISN'T "just working" or you would not 
have posted the question


To state again, I am using Version 13, though a few minor revisions 
behind, with MySql, on CentOS 6 and have no rebooting or other MySql 
related issues


Clearly you need to state in more detail what issues remain, once you 
migrate to AT LEAST 13.xx, and state your OS after becoming current 
with Asterisk, MySql and the OS


I use MySql on every incoming call, and also maintain call detail 
records in MySql for every call, and it just simply works, and has for 
some time.


Although I may be using it quite differently that you, it simply works.
Is this a newly developing issue, or has it persisted for some time
What if any changes have been made to the dialplan etc?

Have you considered a strictly hardware issue? Memory? HD? MB??

The crystal ball is very cloudy on this one!

John Novack


Jonas Kellens wrote:


Hello

thank you for your answer.

If I read your (and others) reaction correctly I can conclude that 
this is an Asterisk problem and not a problem of MySQL or dialplan 
logic ?



You should know that the MySQL database is heavily questioned :


mysql> show status like '%onn%';
+--++
| Variable_name    | Value  |
+--++
| Aborted_connects | 469    |
| Connections  | 132762 |
| Max_used_connections | 8  |
| Ssl_client_connects  | 0  |
| Ssl_connect_renegotiates | 0  |
| Ssl_finished_connects    | 0  |
| Threads_connected    | 3  |
+--++
7 rows in set (0.00 sec)



I stick to 1.8 because it just works. I had some issues with version 
11 and 13 in the past.



Regards

Jonas.


Op 04-10-18 om 17:49 schreef John Novack:

Woefully out of date.
You really need to put your efforts into at least a modest upgrade
I use version 13 with MySql queries built into the dialplan on 
CentOs 6 and have NO such issues, either performance or any restart 
or reboot. It simply works


I never used either 1.6 or 1.8, going from 1.4 to version 11, which 
did require some syntax changes to the dialplan.


Given that even version 11 is EOL, you really need to put your 
efforts into doing the migration rather than tracking this one down


JMO

John Novack



Jonas Kellens wrote:


Hello

using Asterisk 1.8.32.

I notice that there is a spontaneous reboot of the Asterisk system 
from time to time.


When I look in the logs (verbose file) I noticed that every time 
this occurs it's at a moment that there is a MySQL action, be it a 
lookup or an insert/update/delete.


I must say I do have some MySQL queries that occur in my dialplan 
when a call comes in, to look up different actions to perform on 
this call.



An idea how to overcome this problem ? Seems a "performance" issue, 
no ?!


Is it better to have these MySQL queries to be done by an external 
script (like a php script that I call with the System()-command or 
a SHELL()-command) ?



Here are some examples from the verbose file.



[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- 
Executing [s@sub-GetAlertInfo:3] MYSQL("SIP/SipAgenT01-317d", 
"Connect connid localhost myuser mypwd myDB") in new stack
[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- 
Executing [s@sub-GetAlertInfo:5] MYSQL("SIP/SipAgenT01-317d", 
"Query resultid 1 SELECT uri, callinfo FROM distringtone WHERE 
onoff='1'") in new stack
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/logger.conf': [Aug 22 15:19:18] 
VERBOSE[3306] config.c: [Aug 22 15:19:18] == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/asterisk.conf': [Aug 22 15:19:18] 
VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] manager.c: [Aug 22 15:19:18]   == 
Manager registered action DataGet
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/codecs.conf': [Aug 22 15:19:18] 
VERBOSE[3306] config.c: [Aug 22 15:19:18] == Found
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18]  
Asterisk Dynamic Loader Starting:
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/modules.conf': [Aug 22 15:19:18] 
VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/res_config_mysql.conf': [Aug 22 15:19:18] 
VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Found
[Aug 22

[asterisk-users] Spontaneous reboot due to MySQL lookups ? (Jonas Kellens)

2018-10-05 Thread Stefan Viljoen 

Hi Jonas

We have more or less this behaviour with 1.8.32.3 when writing CDRs to ODBC on 
Percona 5.6 (MySQL drop-in replacement with some optimisations and extra 
features.)

In our case the system does NOT reboot, but Asterisk itself crashes with a 
segfault inside unixODBC itself.

We're running on Centos 7, so the first thing we tried was to upgrade the ODBC 
drivers to the most recent version, and also use the most recent MySQL ODBC 
connector.

This did not solve the problem, and the spontaneous shutdowns (and then 
restarts via Centos 7 systemd) of the 1.8.32.3 instances continued.

Eventually we traced this to contention on the CDR table itself in the 
associated MySQL / Percona instance. We had a stored procedure running on the 
CDR table at set intervals via a MySQL timed event that was converting the 
Asterisk CDR data into another table we use for our own purposes. This was 
effectively locking the CDR table in ways that wasn't allowing Asterisk 
1.8.32.3 to enter CDRs when it wanted to.

The practical effect in real-world terms was that people could make a call, but 
then NOT do another call on that same extension, for up to five or ten minutes 
at a time. This was because the Asterisk 1.8.32.3 instance was waiting to get 
access to the CDR table to write that extensions most-recent CDR record in, and 
was holding onto the extension to prevent a new call when it hadn't yet managed 
to write into the CDR table for the previous call.

Also, if pushed hard enough with concurrent calls, the Asterisk instance would 
get segfaulted due to a segfault in the ODBC drivers, due to this contention 
and waiting for access to the CDR table.

All I can recommend is to upgrade to, for example, Asterisk 13.22.0 which is 
relatively painless to upgrade to if you're on 1.8.32.3 or the 1.8 series (at 
least in our experience) - OR remove contention on the CDR table.

We eventually removed the extra SP we had running on the MySQL / Percona CDR 
table, as the contention problems persisted with 13.22.0, BUT IT DOES NOT CRASH 
LIKE 1.8.32.3 - while running against the same Percona 5.6 MySQL version, with 
the same level of MySQL DB contention taking place.

E. g. look for contention on the MySQL tables you use, or just SQL contention 
in general - generate enough contention (with tables locked when Asterisk tries 
to write to them) and it does seem that 1.8 series Asterisk instances will 
segfault in the ODBC driver, if the concurrent call count goes high enough.

Or (the better option) upgrade to at least Asterisk 13 (in our experience).

Even with the same contention on MySQL db's accessed with unixODBC 2.3.6, and 
our same table-access killer SP running, Asterisk 13.22.0 doesn't crash at all 
when writing with the same version unixODBC driver to the contentious tables in 
MySQL. (We still had the same problem with people only being capable of making 
one call and then waiting up to five minutes post-hangup before being able to 
make the next call, but we solved that by not running the SP on schedule 
anymore against the CDR and CEL tables.)

E.g. effectively we solved the crashes by upgrading from 1.8.32.3 to 13.22.0 - 
the rest is incidentals unique to our usage case.

Hope this helps.

Date: Thu, 4 Oct 2018 17:10:01 +0200
From: Jonas Kellens 
To: Asterisk Users Mailing List - Non-Commercial Discussion

Subject: [asterisk-users] Spontaneous reboot due to MySQL lookups ?
Message-ID: 
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello

using Asterisk 1.8.32.

I notice that there is a spontaneous reboot of the Asterisk system from time to 
time.

When I look in the logs (verbose file) I noticed that every time this occurs 
it's at a moment that there is a MySQL action, be it a lookup or an 
insert/update/delete.

I must say I do have some MySQL queries that occur in my dialplan when a call 
comes in, to look up different actions to perform on this call.


An idea how to overcome this problem ? Seems a "performance" issue, no ?!

Is it better to have these MySQL queries to be done by an external 
script (like a php script that I call with the System()-command or a 
SHELL()-command) ?


Here are some examples from the verbose file.



[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- 
Executing [s@sub-GetAlertInfo:3] MYSQL("SIP/SipAgenT01-317d", 
"Connect connid localhost myuser mypwd myDB") in new stack
[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- 
Executing [s@sub-GetAlertInfo:5] MYSQL("SIP/SipAgenT01-317d", "Query 
resultid 1 SELECT uri, callinfo FROM distringtone WHERE onoff='1'") in 
new stack
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/logger.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: 
[Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/asterisk.conf': [Aug 22 1

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-04 Thread Nasir Iqbal 
Hi Jonas Kellens,

Like everybody else, I also recommend to upgrade your Asterisk version, and
replace mysql driver with odbc. the one big advantage of odbc driver is its
pooling feature, you can configure odbc to create a reusable pool of active
connections, so Asterisk does't needs to reconnect for each query.

For example with following odbc settings you can achieve 500+ concurrent
channels (approx 2500 queries / minute) without any performance issue.

pooling => yes
limit   => 16
pre-connect => yes

Regards

Nasir Iqbal

ICTBroadcast - an Auto Dialer software for ITSP

SMS, Fax and Voice broadcasting & Inbound / Outbound Campaigns
http://www.ictbroadcast.com/


On Fri, Oct 5, 2018 at 4:26 AM John Novack  wrote:

> As others have said, clearly it ISN'T "just working" or you would not have
> posted the question
>
> To state again, I am using Version 13, though a few minor revisions
> behind, with MySql, on CentOS 6 and have no rebooting or other MySql
> related issues
>
> Clearly you need to state in more detail what issues remain, once you
> migrate to AT LEAST 13.xx, and state your OS after becoming current with
> Asterisk, MySql and the OS
>
> I use MySql on every incoming call, and also maintain call detail records
> in MySql for every call, and it just simply works, and has for some time.
>
> Although I may be using it quite differently that you, it simply works.
> Is this a newly developing issue, or has it persisted for some time
> What if any changes have been made to the dialplan etc?
>
> Have you considered a strictly hardware issue? Memory? HD? MB??
>
> The crystal ball is very cloudy on this one!
>
> John Novack
>
>
> Jonas Kellens wrote:
>
> Hello
>
> thank you for your answer.
>
> If I read your (and others) reaction correctly I can conclude that this is
> an Asterisk problem and not a problem of MySQL or dialplan logic ?
>
>
> You should know that the MySQL database is heavily questioned :
>
>
> mysql> show status like '%onn%';
> +--++
> | Variable_name| Value  |
> +--++
> | Aborted_connects | 469|
> | Connections  | 132762 |
> | Max_used_connections | 8  |
> | Ssl_client_connects  | 0  |
> | Ssl_connect_renegotiates | 0  |
> | Ssl_finished_connects| 0  |
> | Threads_connected| 3  |
> +--++
> 7 rows in set (0.00 sec)
>
>
>
> I stick to 1.8 because it just works. I had some issues with version 11
> and 13 in the past.
>
>
> Regards
>
> Jonas.
>
> Op 04-10-18 om 17:49 schreef John Novack:
>
> Woefully out of date.
> You really need to put your efforts into at least a modest upgrade
> I use version 13 with MySql queries built into the dialplan on CentOs 6
> and have NO such issues, either performance or any restart or reboot. It
> simply works
>
> I never used either 1.6 or 1.8, going from 1.4 to version 11, which did
> require some syntax changes to the dialplan.
>
> Given that even version 11 is EOL, you really need to put your efforts
> into doing the migration rather than tracking this one down
>
> JMO
>
> John Novack
>
>
>
> Jonas Kellens wrote:
>
> Hello
>
> using Asterisk 1.8.32.
>
> I notice that there is a spontaneous reboot of the Asterisk system from
> time to time.
>
> When I look in the logs (verbose file) I noticed that every time this
> occurs it's at a moment that there is a MySQL action, be it a lookup or an
> insert/update/delete.
>
> I must say I do have some MySQL queries that occur in my dialplan when a
> call comes in, to look up different actions to perform on this call.
>
>
> An idea how to overcome this problem ? Seems a "performance" issue, no ?!
>
> Is it better to have these MySQL queries to be done by an external script
> (like a php script that I call with the System()-command or a
> SHELL()-command) ?
>
>
> Here are some examples from the verbose file.
>
>
>
> [Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing
> [s@sub-GetAlertInfo:3] MYSQL("SIP/SipAgenT01-317d", "Connect connid
> localhost myuser mypwd myDB") in new stack
> [Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing
> [s@sub-GetAlertInfo:5] MYSQL("SIP/SipAgenT01-317d", "Query resultid 1
> SELECT uri, callinfo FROM distringtone WHERE onoff='1'") in new stack
> [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing
> '/etc/asterisk/logger.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug
> 22 15:19:18]   == Found
> [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing
> '/etc/asterisk/asterisk.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c:
> [Aug 22 15:19:18]   == Found
> [Aug 22 15:19:18] VERBOSE[3306] manager.c: [Aug 22 15:19:18]   == Manager
> registered action DataGet
> [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-04 Thread John Novack 

As others have said, clearly it ISN'T "just working" or you would not have 
posted the question

To state again, I am using Version 13, though a few minor revisions behind, 
with MySql, on CentOS 6 and have no rebooting or other MySql related issues

Clearly you need to state in more detail what issues remain, once you migrate 
to AT LEAST 13.xx, and state your OS after becoming current with Asterisk, 
MySql and the OS

I use MySql on every incoming call, and also maintain call detail records in 
MySql for every call, and it just simply works, and has for some time.

Although I may be using it quite differently that you, it simply works.
Is this a newly developing issue, or has it persisted for some time
What if any changes have been made to the dialplan etc?

Have you considered a strictly hardware issue? Memory? HD? MB??

The crystal ball is very cloudy on this one!

John Novack


Jonas Kellens wrote:


Hello

thank you for your answer.

If I read your (and others) reaction correctly I can conclude that this is an 
Asterisk problem and not a problem of MySQL or dialplan logic ?


You should know that the MySQL database is heavily questioned :


mysql> show status like '%onn%';
+--++
| Variable_name    | Value  |
+--++
| Aborted_connects | 469    |
| Connections  | 132762 |
| Max_used_connections | 8  |
| Ssl_client_connects  | 0  |
| Ssl_connect_renegotiates | 0  |
| Ssl_finished_connects    | 0  |
| Threads_connected    | 3  |
+--++
7 rows in set (0.00 sec)



I stick to 1.8 because it just works. I had some issues with version 11 and 13 
in the past.


Regards

Jonas.


Op 04-10-18 om 17:49 schreef John Novack:

Woefully out of date.
You really need to put your efforts into at least a modest upgrade
I use version 13 with MySql queries built into the dialplan on CentOs 6 and 
have NO such issues, either performance or any restart or reboot. It simply 
works

I never used either 1.6 or 1.8, going from 1.4 to version 11, which did require 
some syntax changes to the dialplan.

Given that even version 11 is EOL, you really need to put your efforts into 
doing the migration rather than tracking this one down

JMO

John Novack



Jonas Kellens wrote:


Hello

using Asterisk 1.8.32.

I notice that there is a spontaneous reboot of the Asterisk system from time to 
time.

When I look in the logs (verbose file) I noticed that every time this occurs 
it's at a moment that there is a MySQL action, be it a lookup or an 
insert/update/delete.

I must say I do have some MySQL queries that occur in my dialplan when a call 
comes in, to look up different actions to perform on this call.


An idea how to overcome this problem ? Seems a "performance" issue, no ?!

Is it better to have these MySQL queries to be done by an external script (like 
a php script that I call with the System()-command or a SHELL()-command) ?


Here are some examples from the verbose file.



[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing [s@sub-GetAlertInfo:3] 
MYSQL("SIP/SipAgenT01-317d", "Connect connid localhost myuser mypwd myDB") 
in new stack
[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing [s@sub-GetAlertInfo:5] 
MYSQL("SIP/SipAgenT01-317d", "Query resultid 1 SELECT uri, callinfo FROM 
distringtone WHERE onoff='1'") in new stack
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/logger.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 
15:19:18] == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/asterisk.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 
22 15:19:18] == Found
[Aug 22 15:19:18] VERBOSE[3306] manager.c: [Aug 22 15:19:18]   == Manager 
registered action DataGet
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/codecs.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 
15:19:18] == Found
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18]  Asterisk Dynamic 
Loader Starting:
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/modules.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 
15:19:18] == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/res_config_mysql.conf': [Aug 22 15:19:18] VERBOSE[3306] 
config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] res_config_mysql.c: [Aug 22 15:19:18]   == 
MySQL RealTime driver loaded.
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18]  res_config_mysql.so 
=> (MySQL RealTime Configuration Driver)



[Aug 22 16:23:25] VERBOSE[24283] pbx.c: [Aug 22 16:23:25] -- Executing 
[s@sub-GetSipAccountdetails:3] MYSQL("SIP/SipAgenT01-4184", "Connect connid 
localhost myuser mypwd myDB") in new stack
[Aug 22

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-04 Thread Jonathan H 
On Thu, 4 Oct 2018 at 20:36, Jonas Kellens  wrote:

> I stick to 1.8 because it just works.

Well, clearly it doesn't because you're posting here! In a few days time,
the *8-year-old* Asterisk 1.8 line will be *three years past EOL.*
That means End of Life. Do not use. No more support.

Now, if you were to bring yourself onto the current 13.x LTS (or perhaps
better still wait a few days until the 16.x LTS which will be supported
until 2023), then you might get more answers.

> I had some issues with version 11 and 13 in the past.

Especially if you explain what issues you had with version 13 in the past.
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Astricon is coming up October 9-11!  Signup is available at: 
https://www.asterisk.org/community/astricon-user-conference

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

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-04 Thread Jonas Kellens 

Hello

thank you for your answer.

If I read your (and others) reaction correctly I can conclude that this 
is an Asterisk problem and not a problem of MySQL or dialplan logic ?



You should know that the MySQL database is heavily questioned :


mysql> show status like '%onn%';
+--++
| Variable_name    | Value  |
+--++
| Aborted_connects | 469    |
| Connections  | 132762 |
| Max_used_connections | 8  |
| Ssl_client_connects  | 0  |
| Ssl_connect_renegotiates | 0  |
| Ssl_finished_connects    | 0  |
| Threads_connected    | 3  |
+--++
7 rows in set (0.00 sec)



I stick to 1.8 because it just works. I had some issues with version 11 
and 13 in the past.



Regards

Jonas.


Op 04-10-18 om 17:49 schreef John Novack:

Woefully out of date.
You really need to put your efforts into at least a modest upgrade
I use version 13 with MySql queries built into the dialplan on CentOs 
6 and have NO such issues, either performance or any restart or 
reboot. It simply works


I never used either 1.6 or 1.8, going from 1.4 to version 11, which 
did require some syntax changes to the dialplan.


Given that even version 11 is EOL, you really need to put your efforts 
into doing the migration rather than tracking this one down


JMO

John Novack



Jonas Kellens wrote:


Hello

using Asterisk 1.8.32.

I notice that there is a spontaneous reboot of the Asterisk system 
from time to time.


When I look in the logs (verbose file) I noticed that every time this 
occurs it's at a moment that there is a MySQL action, be it a lookup 
or an insert/update/delete.


I must say I do have some MySQL queries that occur in my dialplan 
when a call comes in, to look up different actions to perform on this 
call.



An idea how to overcome this problem ? Seems a "performance" issue, no ?!

Is it better to have these MySQL queries to be done by an external 
script (like a php script that I call with the System()-command or a 
SHELL()-command) ?



Here are some examples from the verbose file.



[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing 
[s@sub-GetAlertInfo:3] MYSQL("SIP/SipAgenT01-317d", "Connect 
connid localhost myuser mypwd myDB") in new stack
[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing 
[s@sub-GetAlertInfo:5] MYSQL("SIP/SipAgenT01-317d", "Query 
resultid 1 SELECT uri, callinfo FROM distringtone WHERE onoff='1'") 
in new stack
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/logger.conf': [Aug 22 15:19:18] VERBOSE[3306] 
config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/asterisk.conf': [Aug 22 15:19:18] 
VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] manager.c: [Aug 22 15:19:18]   == 
Manager registered action DataGet
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/codecs.conf': [Aug 22 15:19:18] VERBOSE[3306] 
config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18] Asterisk 
Dynamic Loader Starting:
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/modules.conf': [Aug 22 15:19:18] VERBOSE[3306] 
config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == 
Parsing '/etc/asterisk/res_config_mysql.conf': [Aug 22 15:19:18] 
VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] res_config_mysql.c: [Aug 22 
15:19:18]   == MySQL RealTime driver loaded.
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18] 
res_config_mysql.so => (MySQL RealTime Configuration Driver)




[Aug 22 16:23:25] VERBOSE[24283] pbx.c: [Aug 22 16:23:25] -- 
Executing [s@sub-GetSipAccountdetails:3] 
MYSQL("SIP/SipAgenT01-4184", "Connect connid localhost myuser 
mypwd myDB") in new stack
[Aug 22 16:23:25] VERBOSE[24283] pbx.c: [Aug 22 16:23:25] -- 
Executing [s@sub-GetSipAccountdetails:4] 
MYSQL("SIP/SipAgenT01-4184", "Query resultid 1 SELECT 
SIPusername, currstatus, available FROM tbl_SIP WHERE ID="800"") in 
new stack
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32]   == 
Parsing '/etc/asterisk/logger.conf': [Aug 22 16:23:32] VERBOSE[24309] 
config.c: [Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32]   == 
Parsing '/etc/asterisk/asterisk.conf': [Aug 22 16:23:32] 
VERBOSE[24309] config.c: [Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] manager.c: [Aug 22 16:23:32]   == 
Manager registered action DataGet
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32]   == 
Parsing '/etc/asterisk/codecs.conf': [Aug 22 16:23:32] VERBOSE[24309] 
config.c: [Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] loader.c:

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-04 Thread John Novack 

Woefully out of date.
You really need to put your efforts into at least a modest upgrade
I use version 13 with MySql queries built into the dialplan on CentOs 6 and 
have NO such issues, either performance or any restart or reboot. It simply 
works

I never used either 1.6 or 1.8, going from 1.4 to version 11, which did require 
some syntax changes to the dialplan.

Given that even version 11 is EOL, you really need to put your efforts into 
doing the migration rather than tracking this one down

JMO

John Novack



Jonas Kellens wrote:


Hello

using Asterisk 1.8.32.

I notice that there is a spontaneous reboot of the Asterisk system from time to 
time.

When I look in the logs (verbose file) I noticed that every time this occurs 
it's at a moment that there is a MySQL action, be it a lookup or an 
insert/update/delete.

I must say I do have some MySQL queries that occur in my dialplan when a call 
comes in, to look up different actions to perform on this call.


An idea how to overcome this problem ? Seems a "performance" issue, no ?!

Is it better to have these MySQL queries to be done by an external script (like 
a php script that I call with the System()-command or a SHELL()-command) ?


Here are some examples from the verbose file.



[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing [s@sub-GetAlertInfo:3] 
MYSQL("SIP/SipAgenT01-317d", "Connect connid localhost myuser mypwd myDB") 
in new stack
[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- Executing [s@sub-GetAlertInfo:5] 
MYSQL("SIP/SipAgenT01-317d", "Query resultid 1 SELECT uri, callinfo FROM 
distringtone WHERE onoff='1'") in new stack
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18] == Parsing 
'/etc/asterisk/logger.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 
15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18] == Parsing 
'/etc/asterisk/asterisk.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 
22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] manager.c: [Aug 22 15:19:18] == Manager 
registered action DataGet
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18] == Parsing 
'/etc/asterisk/codecs.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 
15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18] Asterisk Dynamic 
Loader Starting:
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18] == Parsing 
'/etc/asterisk/modules.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 
15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18] == Parsing 
'/etc/asterisk/res_config_mysql.conf': [Aug 22 15:19:18] VERBOSE[3306] 
config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] res_config_mysql.c: [Aug 22 15:19:18]   == 
MySQL RealTime driver loaded.
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18] res_config_mysql.so 
=> (MySQL RealTime Configuration Driver)



[Aug 22 16:23:25] VERBOSE[24283] pbx.c: [Aug 22 16:23:25] -- Executing 
[s@sub-GetSipAccountdetails:3] MYSQL("SIP/SipAgenT01-4184", "Connect connid 
localhost myuser mypwd myDB") in new stack
[Aug 22 16:23:25] VERBOSE[24283] pbx.c: [Aug 22 16:23:25] -- Executing [s@sub-GetSipAccountdetails:4] 
MYSQL("SIP/SipAgenT01-4184", "Query resultid 1 SELECT SIPusername, currstatus, available 
FROM tbl_SIP WHERE ID="800"") in new stack
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/logger.conf': [Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 
16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/asterisk.conf': [Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 
22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] manager.c: [Aug 22 16:23:32]   == Manager 
registered action DataGet
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/codecs.conf': [Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 
16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] loader.c: [Aug 22 16:23:32] Asterisk Dynamic 
Loader Starting:
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/modules.conf': [Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 
22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/res_config_mysql.conf': [Aug 22 16:23:32] VERBOSE[24309] 
config.c: [Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] res_config_mysql.c: [Aug 22 16:23:32]   == 
MySQL RealTime driver loaded.
[Aug 22 16:23:32] VERBOSE[24309] loader.c: [Aug 22 16:23:32] res_config_mysql.so 
=> (MySQL RealTime Configuration Driver)



[Oct  4 10:11:25] VERBOSE[4944] pbx.c: [Oct  4 10:11:25] -- Executing [s@sub-settings:16] 
MYSQL("SIP/SipAgenT01-08cb", "Connect connid localhost myuser mypwd myDB") 
in new stack
[Oct  4 10:11:25] VERBOSE[4944] pbx.c: [Oct  4 10:11:25] -- Executing [s@sub-settings:17]

Re: [asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-04 Thread Antony Stone 
On Thursday 04 October 2018 at 17:10:01, Jonas Kellens wrote:

> Hello
> 
> using Asterisk 1.8.32.

Ooh, vintage :)

> I notice that there is a spontaneous reboot of the Asterisk system from
> time to time.
> 
> When I look in the logs (verbose file) I noticed that every time this
> occurs it's at a moment that there is a MySQL action, be it a lookup or
> an insert/update/delete.
> 
> I must say I do have some MySQL queries that occur in my dialplan when a
> call comes in, to look up different actions to perform on this call.
> 
> 
> An idea how to overcome this problem ?

I would recommend (a) update to a current and supported version of Asterisk, 
and (b) use the ODBC driver.

If the problem persists then with that setup you're more likely to get help 
here or be able to file a bug report, but no-one's going to fix a problem in 
1.8 
now.


Regards,


Antony.

-- 
3 logicians walk into a bar. The bartender asks "Do you all want a drink?"
The first logician says "I don't know."
The second logician says "I don't know."
The third logician says "Yes!"

   Please reply to the list;
 please *don't* CC me.

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Astricon is coming up October 9-11!  Signup is available at: 
https://www.asterisk.org/community/astricon-user-conference

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

[asterisk-users] Spontaneous reboot due to MySQL lookups ?

2018-10-04 Thread Jonas Kellens 

Hello

using Asterisk 1.8.32.

I notice that there is a spontaneous reboot of the Asterisk system from 
time to time.


When I look in the logs (verbose file) I noticed that every time this 
occurs it's at a moment that there is a MySQL action, be it a lookup or 
an insert/update/delete.


I must say I do have some MySQL queries that occur in my dialplan when a 
call comes in, to look up different actions to perform on this call.



An idea how to overcome this problem ? Seems a "performance" issue, no ?!

Is it better to have these MySQL queries to be done by an external 
script (like a php script that I call with the System()-command or a 
SHELL()-command) ?



Here are some examples from the verbose file.



[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- 
Executing [s@sub-GetAlertInfo:3] MYSQL("SIP/SipAgenT01-317d", 
"Connect connid localhost myuser mypwd myDB") in new stack
[Aug 22 15:19:10] VERBOSE[2977] pbx.c: [Aug 22 15:19:10] -- 
Executing [s@sub-GetAlertInfo:5] MYSQL("SIP/SipAgenT01-317d", "Query 
resultid 1 SELECT uri, callinfo FROM distringtone WHERE onoff='1'") in 
new stack
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/logger.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: 
[Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/asterisk.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: 
[Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] manager.c: [Aug 22 15:19:18] == Manager 
registered action DataGet
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/codecs.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: 
[Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18] Asterisk 
Dynamic Loader Starting:
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/modules.conf': [Aug 22 15:19:18] VERBOSE[3306] config.c: 
[Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] config.c: [Aug 22 15:19:18]   == Parsing 
'/etc/asterisk/res_config_mysql.conf': [Aug 22 15:19:18] VERBOSE[3306] 
config.c: [Aug 22 15:19:18]   == Found
[Aug 22 15:19:18] VERBOSE[3306] res_config_mysql.c: [Aug 22 15:19:18]   
== MySQL RealTime driver loaded.
[Aug 22 15:19:18] VERBOSE[3306] loader.c: [Aug 22 15:19:18] 
res_config_mysql.so => (MySQL RealTime Configuration Driver)




[Aug 22 16:23:25] VERBOSE[24283] pbx.c: [Aug 22 16:23:25] -- 
Executing [s@sub-GetSipAccountdetails:3] 
MYSQL("SIP/SipAgenT01-4184", "Connect connid localhost myuser mypwd 
myDB") in new stack
[Aug 22 16:23:25] VERBOSE[24283] pbx.c: [Aug 22 16:23:25] -- 
Executing [s@sub-GetSipAccountdetails:4] 
MYSQL("SIP/SipAgenT01-4184", "Query resultid 1 SELECT SIPusername, 
currstatus, available FROM tbl_SIP WHERE ID="800"") in new stack
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/logger.conf': [Aug 22 16:23:32] VERBOSE[24309] config.c: 
[Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/asterisk.conf': [Aug 22 16:23:32] VERBOSE[24309] 
config.c: [Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] manager.c: [Aug 22 16:23:32] == Manager 
registered action DataGet
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/codecs.conf': [Aug 22 16:23:32] VERBOSE[24309] config.c: 
[Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] loader.c: [Aug 22 16:23:32] Asterisk 
Dynamic Loader Starting:
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/modules.conf': [Aug 22 16:23:32] VERBOSE[24309] config.c: 
[Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] config.c: [Aug 22 16:23:32] == Parsing 
'/etc/asterisk/res_config_mysql.conf': [Aug 22 16:23:32] VERBOSE[24309] 
config.c: [Aug 22 16:23:32]   == Found
[Aug 22 16:23:32] VERBOSE[24309] res_config_mysql.c: [Aug 22 16:23:32]   
== MySQL RealTime driver loaded.
[Aug 22 16:23:32] VERBOSE[24309] loader.c: [Aug 22 16:23:32] 
res_config_mysql.so => (MySQL RealTime Configuration Driver)




[Oct  4 10:11:25] VERBOSE[4944] pbx.c: [Oct  4 10:11:25] -- 
Executing [s@sub-settings:16] MYSQL("SIP/SipAgenT01-08cb", "Connect 
connid localhost myuser mypwd myDB") in new stack
[Oct  4 10:11:25] VERBOSE[4944] pbx.c: [Oct  4 10:11:25] -- 
Executing [s@sub-settings:17] MYSQL("SIP/SipAgenT01-08cb", "Query 
resultid 1 SELECT blockID from DID where DID=987654321") in new stack
[Oct  4 10:11:29] VERBOSE[4961] config.c: [Oct  4 10:11:29]   == Parsing 
'/etc/asterisk/asterisk.conf': [Oct  4 10:11:29] VERBOSE[4961] config.c: 
[Oct  4 10:11:29]   == Found
[Oct  4 10:11:29] VERBOSE[4961] manager.c: [Oct  4 10:11:29] == Manager 
registered action DataGet
[Oct  4 10:11:29] VERBOSE[4961] config.c: [Oct  4 10:11:29]   == Parsing 
'/etc/asterisk/codecs.conf': [Oct  4