[#MXS-966] If secrets_readKeys() in secret.c fails (return NULL) MaxScale will keep trying again

[MXS-966] If secrets_readKeys() in secret.c fails (return NULL) MaxScale will keep trying again Created: 2016-11-09 Updated: 2017-02-22 Due: 2016-11-30 Resolved: 2017-02-22
Status:	Closed
Project:	MariaDB MaxScale
Component/s:	Core, maxpasswd
Affects Version/s:	2.0.1
Fix Version/s:	2.1.0

Type:

Bug

Priority:

Minor

Reporter:

Esa Korhonen

Assignee:

Esa Korhonen

Resolution:

Fixed

Votes:

Labels:

None

Sprint:

2017-28

Description

If reading file ".secrets" fails for any reason in secrets_readKeys(const char* path), an error message is produced but MaxScale keeps running and will try again later. This continues ad infinitum. For this bug to happen the services must successfully start (using cached passwords?).
Call stack (other stacks are also possible):
secrets_readKeys
decryptPassword
mon_connect_to_db
monitorDatabase
monitorMain
start_thread
clone ()

Comments

Comment by Esa Korhonen [ 2017-02-22 ]

The same error is produced several times (once for each backend per service or monitor), but stops eventually.

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

[MXS-966] If secrets_readKeys() in secret.c fails (return NULL) MaxScale will keep trying again Created: 2016-11-09 Updated: 2017-02-22 Due: 2016-11-30 Resolved: 2017-02-22