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

[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.