Maxscale slow and lost connection - mariadb

i have maxscale installed, I obtain this error:
Refresh rate limit exceeded for load of users' table.
what can I do? I have mariadb database

When the authentication of a user fails, MaxScale reloads the list of database users. This reloading is rate limited which causes the error message in question to be logged.
Inspecting the error logs of MaxScale for any clues about the failed authentication attempts will allow you to fix of the root cause of the problem.
The MaxScale tutorial over at the MariaDB KB shows How to set up MaxScale and how to configure database grants for use with MaxScale.

Related

Fail to collect MariaDB failed login event with packetbeat

I setup packetbeat on a server and set switch mirror traffic to this server.
It works fine except I can not collect user failed login.
Anything I misunderstood by using packetbeat ?
Any solution with "beats" can do without enable MariaDB Audit Plugin?

Failed to login when creating DataSet from DataStore using Azure Machine Learning Designer

I'm new to Azure and its ML Designer. I have an Azure SQL Database set up with my Client IP allowed through the Firewall. I can connect using SSMS without issue using the server path and credentials Azure supplied.
I have set up a Machine Learning Resource and launched the Learning Studio.
Inside the Learning Studio I created a DataStore pointing to my Azure SQL Database and everything seems just fine:
Azure SQL Database DataStore
However, when I try to create a DataSet from that DataStore I am getting Login errors:
Login error when creating DataSet
In "More details" I see the following:
ScriptExecutionException was caused by DatabaseConnectionException.\n DatabaseConnectionException was caused by AuthenticationException.\n 'MSSQl' encountered connection erro with error code '18456' while opening connection to server ([REDACTED]), database ([REDACTED]). Either the database name is not valid or username and password is wrong. Exception class: '14'. HResult: x80131904.\n Failed due to inner exception of type: SqlException\n
I am sure the database name and login credentials are correct i.e. they work just fine when connecting from my SSMS. What else can this be? I've checked the Azure SQL Database profile - is there something here regarding security or access that I should be setting?
Firewall Settings
** UPDATE **
Solved this by going to SQL Server > Active Directory admin. There was nothing set here so I clicked Set Admin and then from the right panel scrolled down to the ML service I had set up. Once I saved it and then created a Dataset in ML I could see the data Preview just fine.
To get a preview of the dataset, it goes through Azure ML's service. If the only kind of restriction are IP restrictions (nothing around vnets/private links), then you can add Azure ML's IP ranges to your network settings.
Alternatively, you can choose to "skip validation" where Microsoft will not parse the data while trying to create the dataset, but this means preview won't be shown.
Furthermore, ensure that you have created a server-level IP firewall rule in the firewall settings and allowed access to the server, entered valid authentication details when creating the datastore, and specified a valid table when querying your database.
Note: I was able to connect successfully using above guidelines. Thanks.

MariaDB Maxscale throwing Access Denied though UserID/Password is Correct

Database Version : 10.2.14
Maxscale Version : 2.4.6
Application is using jdbc driver to connect to database
userid1 & userid2 is allowed to connect from anywhere i.e.
If we connect to database directly from application server we are not receiving any issues, and connection establishes successfully, but when we connect to database via maxscale we receive intermittent Access Denied error
Note : USERID and PASSWORD are same and NEVER CHANGE FROM DAY 1
Scenario's
userid1 : Connect to database via Maxscale with ID/Password throws Access Denied Error intermittently, sometimes connects successfully
Userid1 : Connect to database directly from application, works fine no issues
userid2 : Connect to database via Maxscale with ID/Password throws Access Denied Error intermittently, sometimes connects successfully
Userid2 : Connect to database directly from application, works fine no issues
Earlier Maxscale Version was 2.2.19 and we never faced issues.
From both (application & Maxscale) logs we can see only ACCESS DENIED errors for those id's.
What am unable to understand is
1) Userid and Password never changed, so why we are receiving ACCESS DENIED when using Maxscale that too intermittently and no issue if we connect directly database.
2) IF Userid/Password passes wrongly then it should be always access denied, but in this case it's intermittently
Similar behavior is reported as MXS-2891 in the MariaDB Jira. I'd recommend reporting these problems on that Jira issue.

websphere liberty profile - add database connection errors to logs

I have a application deployed on liberty profile that connects to a db server over the network.
I'm trying to configure it so when connection time outs happen they are logged in messages or trace log files.
At the moment it just gives me an output like
Application xyz has not started in 30.004 seconds.
nothing to indicate why.... can anyone tell me how i configure it to output all DB related errors ?
A failure to connect to a database should not be related to whether or not your application starts. As any database access defined by application code would be running after the application has reported that it started.
I suspect there is a separate issue causing your application to not start. To confirm this theory you can comment out database access from your application and see if the app starts then.

ADO.Net Connection Pooling with an MSSQL Account that is Disabled

In our production environment we have a database that every 30 minutes is restored from a vendor's log shipping backup. When that restore happens, our SQL Auth account is disabled, the database is restored and the account is re-enabled.
A problem occurs when the connection pool is fresh and we attempt to connect to the disabled account. The bad connection is then pooled (I assume) and for the next 1 to 3 hours every connection throws a SQLException [SqlException: Login failed for user 'xxxxx'. Reason: The account is disabled.]
Even though, we can connect to the database via SSMS and an Application Pool reset fixes the issue.
Is there any fix other than to disable pooling?

Resources