Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.3.20, 2.4.11, 2.5.2
-
None
-
CentOS 7
Description
error : (7782078) [mariadbbackend] 'getpeername()' failed on file descriptor '203'.
|
Backend server's error log contains-
[Warning] Access denied for user 'xxxx'@'yyyy' (using password: YES)
|
[Warning] Aborted connection 29958992 to db: 'unconnected' user: 'xxxx' host: 'yyyy' (Access denied for user 'xxxx'@'yyyy' (usin...)
|
There are many entries in the backend for Access denied and Aborted connection, but these other entries do not correspond with MaxScale frontend errors about a failed file descriptor.
Th getpeername()' failed on file descriptor errors are at this point the only errors continuing to populate MaxScale's log file, unabated.
This may be a legitimate networking issue between MaxScale and the backend server(s) (backing servers are a three-node Galera cluster using mariadbclient and readwritesplit router), but the error messages MaxScale is providing do not seem to match documentation nor are they immediately helpful in verifying the issue is networking rather than an internal MaxScale problem.
I am opening this bug to seek clarification of what is going on here and to seek improved documentation or error messages.