[MXS-4118] Maxscale Segfault on get_password Created: 2022-05-03  Updated: 2023-01-31  Resolved: 2023-01-31

Status: Closed
Project: MariaDB MaxScale
Component/s: None
Affects Version/s: 2.4.17
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Jeff Smelser Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Environment:

Kubernetes using official maxscale images


 Description   

Looks like we received a segfault today on a running instance. 

 
 
2022-05-02 17:15:23.580   warning: (5975581) (change_rlag_state): Replication lag of 'replica0' is 0s, which is below the configured limit 30s. 'replica0' is returned to query routing.
 
2022-05-02 17:15:23.580   warning: (5975581) (change_rlag_state): Replication lag of 'replica1' is 0s, which is below the configured limit 30s. 'replica1' is returned to query routing.
 
Fatal: MaxScale 2.4.17 received fatal signal 11. Commit ID: a8bfbbe254095d931aed351871fee72ce9ea645c System name: Linux Release string: CentOS Linux release 8.3.2011
 
 
 
2022-05-03 15:01:45.271   alert  : (6526982) (sigfatal_handler): Fatal: MaxScale 2.4.17 received fatal signal 11. Commit ID: a8bfbbe254095d931aed351871fee72ce9ea645c System name: Linux Release string: CentOS Linux release 8.3.2011
 
2022-05-03 15:01:45.271   alert  : (6526982) (sigfatal_handler): Statement currently being classified: none/unknown
 
nm: /lib64/libsqlite3.so.0: no symbols
 
2022-05-03 15:01:46.452   alert  : (6526982) (sigfatal_handler):
 
  /lib64/libsqlite3.so.0(sqlite3_exec+0x12a): ??:0
 
  /usr/lib64/maxscale/libmariadbauth.so.1.0.0(get_password+0x416): server/modules/authenticator/MariaDBAuth/dbusers.cc:448
 
  /usr/lib64/maxscale/libmariadbauth.so.1.0.0(validate_mysql_user+0x55): server/modules/authenticator/MariaDBAuth/dbusers.cc:468
 
  /usr/lib64/maxscale/libmariadbauth.so.1.0.0(+0x5d8b): server/modules/authenticator/MariaDBAuth/mysql_auth.cc:408
 
  /usr/lib64/maxscale/libmariadbclient.so(+0x6454): server/modules/protocol/MySQL/mariadbclient/mysql_client.cc:976
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xa38cc): server/core/dcb.cc:2710
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xa3b61): server/core/dcb.cc:2757
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x196): maxutils/maxbase/src/worker.cc:858
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559
 
  /lib64/libstdc++.so.6(+0xc2ba3): ??:?
 
  /lib64/libpthread.so.0(+0x814a): pthread_create.c:?
 
  /lib64/libc.so.6(clone+0x43): :?
 
 
 
 
 
Writing core dump

Close as I could find was: https://jira.mariadb.org/browse/MXS-3585
Is it possible the sqllite db for the users was corrupted?

 Comments   
Comment by Johan Wikman [ 2022-05-04 ]

It's of course possible that the sqlite3 (in memory) database had become corrupted, but I find that quite unlikely. Was this a random occurrence or can you repeat it?

Comment by Jeff Smelser [ 2022-05-04 ]

So Far, just the one time and this has been running this way for a while. The pod crashed and restarted. It's been running fine since too. I assume by the error message, something was trying to log in and it failed by crashing? I would need to know if I can attempt to re-create the issue.

Comment by markus makela [ 2022-07-06 ]

jsmelser_recharge have you tried if this happens with 2.5 as well?

Comment by Johan Wikman [ 2023-01-31 ]

Closed as no additional feedback was received and 2.4 has anyway reached its EOL.

Generated at Thu Feb 08 04:26:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.