Notifications

90 views

Description

Scenario: Password Reset Pugin enabled but no Discovery plugin enabled.

Log errors related to a non-existent table "perf_metric_probe_sensor table" after the Password Reset process.

This was not occurring before the upgrade to Madrid Patch 2.

Whenever the customer finishes up a Password Reset Process, the log system populates with the following error:

FAILED TRYING TO EXECUTE ON CONNECTION glide.15 (connpid=70249): INSERT INTO perf_metric_probe_sensor () VALUES() /* <instance-name>, gs:glide.scheduler.worker.0, tx:57a695dcdb0df7008f145487dc96195b */
Syntax Error or Access Rule Violation detected by database (Table '<instance-name>.perf_metric_probe_sensor' doesn't exist)
: java.sql.SQLSyntaxErrorException: Table '<instance-name>.perf_metric_probe_sensor' doesn't exist: org.mariadb.jdbc.internal.SQLExceptionMapper.get(SQLExceptionMapper.java:138)
org.mariadb.jdbc.internal.SQLExceptionMapper.throwException(SQLExceptionMapper.java:106)
org.mariadb.jdbc.MySQLStatement.executeQueryEpilog(MySQLStatement.java:274)
org.mariadb.jdbc.MySQLStatement.execute(MySQLStatement.java:302)
org.mariadb.jdbc.MySQLStatement.execute(MySQLStatement.java:393)

The customer has no Discovery plugin enabled.

Steps to Reproduce

In an instance with Password Reset process configured without Discovery plugin, create and make a simple password changing process.

Expected behavior: We should not log those errors if the client has no Discovery plugin enabled.

Actual behavior: We are trying to insert and logging the error after the Password Reset process finishes.

Error sample:

FAILED TRYING TO EXECUTE ON CONNECTION glide.27 (connpid=1982904): INSERT INTO perf_metric_probe_sensor () VALUES() /* <node-name>, gs:glide.scheduler.worker.3, tx:82435e4ddb3b7f042afe3391f4961923 */
Syntax Error or Access Rule Violation detected by database (Table '<instance-name>.perf_metric_probe_sensor' doesn't exist)

Workaround

  • These errors can be ignored and do not impact the Password Reset Application.
  • The only impact is increasing error logs in the system log table but that would be regularly cleaned via Table Rotation.
  • There is no workaround for this issue.
  • You may consider ignoring this error messages until you can upgrade to a release where this is fixed.

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

 


Related Problem: PRB1341910

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6

Fixed In

Madrid Patch 9
New York Patch 3
Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-05-18 06:15:47
Published:2020-05-18