[MXS-175] sudden signal 6 abort after running for 2 days Created: 2015-05-31  Updated: 2015-11-25  Resolved: 2015-11-25

Status: Closed
Project: MariaDB MaxScale
Component/s: Core, qlafilter, topfilter
Affects Version/s: 1.1.0
Fix Version/s: 1.3.0

Type: Bug Priority: Minor
Reporter: Glenn Plas Assignee: markus makela
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"


Attachments: File MaxScale.cnf    
Issue Links:
Blocks
is blocked by MXS-164 setting log_debug=1 triggers signal 1... Closed

 Description   

Getting a signal 6 abort about 3 hours after getting authentication failures on a certain DB. I'm not able to estimate the significance of those auth. failures in relation to the signal 6. Pay attention to the event time (silent for almost 3 hrs ->@ 13:55:36 ).

This actually never happend until now, uptime a few weeks. But I started using topfilter/qla filter recently, which is the only change I can think of. I cannot debug/trace/log due to issues described in #MXS-164 bug report.

The permission problem warning disappeared now that I added the needed privileges. I also switched topfilter off for now.

May 31 11:03:18 ttextlb1 MaxScale[18908]: Error : Invalid authentication message from backend. Error : 42000, Msg : Access denied for user 'ticketing'@'%' to database 'ticketingfrontend_crm2'
May 31 11:03:18 ttextlb1 MaxScale[18908]: Error : Backend server didn't accept authentication for user ticketing.
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingfrontend_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingfrontend_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logmediaframe
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logstaging
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logticketing
May 31 11:03:18 ttextlb1 MaxScale[18908]: Error : Unable to write to backend due to authentication failure.
May 31 11:03:18 ttextlb1 MaxScale[18908]: Error : Invalid authentication message from backend. Error : 42000, Msg : Access denied for user 'ticketing'@'%' to database 'ticketingfrontend_crm2'
May 31 11:03:18 ttextlb1 MaxScale[18908]: Error : Backend server didn't accept authentication for user ticketing.
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingfrontend_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingfrontend_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging_crm
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logmediaframe
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logstaging
May 31 11:03:18 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logticketing
May 31 11:03:25 ttextlb1 MaxScale[18908]: Error : Invalid authentication message from backend. Error : 42000, Msg : Access denied for user 'ticketing'@'%' to database 'ticketingfrontend_crm2'
May 31 11:03:25 ttextlb1 MaxScale[18908]: Error : Backend server didn't accept authentication for user ticketing.
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingfrontend_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingfrontend_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logmediaframe
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logstaging
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logticketing
May 31 11:03:25 ttextlb1 MaxScale[18908]: Error : Unable to write to backend due to authentication failure.
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingfrontend_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: tim@% for database: ticketingstaging_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingfrontend_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketingstaging_crm
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logmediaframe
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logstaging
May 31 11:03:25 ttextlb1 MaxScale[18908]: Warning: Duplicate MySQL user found for service [RW Split Router]: logging@% for database: logticketing
May 31 11:03:35 ttextlb1 MaxScale[18908]: Error : Invalid authentication message from backend. Error : 42000, Msg : Access denied for user 'ticketing'@'%' to database 'ticketingfrontend_crm2'
May 31 11:03:35 ttextlb1 MaxScale[18908]: Error : Backend server didn't accept authentication for user ticketing.
May 31 11:03:35 ttextlb1 MaxScale[18908]: RW Split Router: Refresh rate limit exceeded for load of users' table.
May 31 11:03:35 ttextlb1 MaxScale[18908]: Error : Unable to write to backend due to authentication failure.
May 31 11:03:35 ttextlb1 MaxScale[18908]: RW Split Router: Refresh rate limit exceeded for load of users' table.
May 31 11:03:35 ttextlb1 MaxScale[18908]: Error : Unable to write to backend due to authentication failure.
May 31 13:55:36 ttextlb1 MaxScale[18908]: Fatal: MaxScale received fatal signal 6. Attempting backtrace.
May 31 13:55:36 ttextlb1 MaxScale[18908]: /usr/local/mariadb-maxscale/bin/maxscale() [0x5483e3]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f7e636b2340]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7f7e622e9cc9]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f7e622ed0d8]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /lib/x86_64-linux-gnu/libc.so.6(+0x73394) [0x7f7e62326394]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /lib/x86_64-linux-gnu/libc.so.6(+0x7f66e) [0x7f7e6233266e]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /usr/local/mariadb-maxscale/modules/libtopfilter.so(+0x3d64) [0x7f7e4408fd64]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /usr/local/mariadb-maxscale/modules/libMySQLClient.so(+0x6ac6) [0x7f7e472ceac6]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /usr/local/mariadb-maxscale/modules/libMySQLClient.so(+0x57de) [0x7f7e472cd7de]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /usr/local/mariadb-maxscale/bin/maxscale() [0x55ac51]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /usr/local/mariadb-maxscale/bin/maxscale(poll_waitevents+0x6d4) [0x55a502]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7f7e636aa182]
May 31 13:55:36 ttextlb1 MaxScale[18908]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f7e623ad47d]



 Comments   
Comment by markus makela [ 2015-11-25 ]

Since we have not been able to reproduce this bug, it needs to be tested with the latest version of MaxScale, preferably the upcoming 1.3.0 release. If the problem persists, this bug can be reopened.

Generated at Thu Feb 08 03:57:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.