Users are currently editing objects in the CCM won't clear

[tgriep]

One more thing to do. The Max Connections to the MYSQL database is close so you should double the MAX Connections on the MYSQL database.
If not, that would cause corrupted data if it is hit.

[TBT]

Below is the result of verifying STRICT_TRANS_TABLES setting as per the document you linked.

Code: Select all

mysql> SELECT @@SQL_MODE, @@GLOBAL.SQL_MODE\G
*************************** 1. row ***************************
       @@SQL_MODE:
@@GLOBAL.SQL_MODE:
1 row in set (0.00 sec)

mysql> show variables like '%version%';
+-------------------------+---------------------+
| Variable_name           | Value               |
+-------------------------+---------------------+
| innodb_version          | 5.5.60              |
| protocol_version        | 10                  |
| slave_type_conversions  |                     |
| version                 | 5.5.60-0+deb7u1-log |
| version_comment         | (Debian)            |
| version_compile_machine | x86_64              |
| version_compile_os      | debian-linux-gnu    |
+-------------------------+---------------------+
7 rows in set (0.00 sec)

Please advise on how you'd like to proceed.

[tgriep]

Your are running a version of MYSQL that does not require the Strict Trans settings but you still need to increase the Max Connections to the database.

[TBT]

Your are running a version of MYSQL that does not require the Strict Trans settings but you still need to increase the Max Connections to the database.

Okay, so we've bumped up the Max Connections to 1000, our current usage is 279 concurrent connections (approx. 28%), historically the highest we've never maxed was 692/750.

Where do we go from here?

[tgriep]

One thing to check is to make sure the time is set on the XI server and the MYSQL server.
In XI, it you go to the Admin > System Profile menu and click on the View System Info button, under the Date/Time section, the time zone has to be set and the PHP time and the System Time needs to match.
If not, follow this KB article.

https://support.nagios.com/kb/article/n ... e-152.html

When you dumped the tbl_session table last Friday, the session was only around 30 seconds old so the message should be displayed as it is less than 300 seconds.
Did you disable the Page Locking on the server?

Can you run this command on the XI server and post the output to the post?

Code: Select all

echo 'select * from xi_options;' |psql nagiosxi nagiosxi |grep ccm_enable_locking

[TBT]

Date/Time are a match.

Code: Select all

PHP Time: Tue, 27 Oct 2020 11:33:07 -0400
System Time: Tue, 27 Oct 2020 11:33:07 -0400

Page locking is not enabled as far as I can tell.

Code: Select all

# echo 'select * from xi_options;' |psql nagiosxi nagiosxi |grep ccm_enable_locking

# echo "select * from xi_options where name like '%ccm%' order by option_id;" |psql nagiosxi nagiosxi
 option_id |           name            |   value
-----------+---------------------------+------------
       101 | ccm_last_update           | 1359642192
       153 | ccm_apply_config_needed   | 0
       199 | ccm_modified_tables_array | YTowOnt9
(3 rows)

[tgriep]

If the locking is not set in the database, the default is to enable it so go to the CCM settings menu and disable it and save the settings.

[TBT]

If the locking is not set in the database, the default is to enable it so go to the CCM settings menu and disable it and save the settings.

So to confirm, you're suggesting we disable User-Based Editing Page Locking in CCM and truncate the two tables from the earlier thread?

Also, since Page Locking is disabled on the DB, having User-Based Editing Page Locking enabled would cause this warning and if so, would enabling Page Locking resolve the warnings?

XI has been functioning for years without these persistent warnings, I find it very odd all of a sudden they no longer clear.

[tgriep]

Yes, I am suggesting to disable the Page Locking feature and to truncate the tables.

The way that function works is if someone is in the CCM and is editing a object and another user does the same and Applies the Config and it has been less than 300 seconds when the first person is in, it will display that message.

If a user is in the CCM and they lose connection to the server or just close their browser and they did not save, it will display that message.

[TBT]

So, we've done as suggested. The warning is gone afterward, however, once a user applies configuration the warning returns again.

ccm1.png

ccm2.png

Please advise,