Nagios Support Forum

Hi,

Every time I apply a new configuration, I am getting the message " Users are currently editing objects in the CCM". I have tried to disable "Enable page locking for multiple users editing same page" under settings but still the same message shows up. One of the dates shown at that Apply configuration page is 15 days ago. How can I fix this?

Try this:
In the XI UI go to: Core Config Manager > Tools > Write Config Files

Then follow these steps in order:

delete (deletes all flat files)
write (creates new flat files based off of what is in the MySQL db)
verify (runs the nagios verify cmd)

* If verify is good, then apply the config.
* If verify is bad, then correct the corresponding error, then repeat these steps until there are no more errors. If caught in a cycle post the last error message here in your next post.


You might also have a corrupt db - it can't hurt to run the db repair script to eliminate this as a possible culprit. Follow the steps outlined here
https://assets.nagios.com/downloads/nag ... tabase.pdf



*If* that doesn't do it, can you PM me your Profile? You can download it by going to Admin > System Config > System Profile and click the Download Profile button towards the top. If for whatever reason you *cannot* download the profile, please put the output of View System Info (5.3.4+, Show Profile if older) in the thread (that will at least get us some info). This will give us access to many of the logs we would otherwise ask for individually. If security is a concern, you can unzip the profile take out what you like, and then zip it up again. We may end up needing something you remove, but we can ask for that specifically. The thing I'll want the most out of the profile is your mysql/mariadb log.

Assuming you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.

Hi dwhitfield,

The problem went away by itself. Thanks for the detailed reply, it may come handy if the problem shows up again.

vmesquita wrote: The problem went away by itself.

The error itself is fairly rare, but it going away by itself when it does come up is a common resolution. Maybe it's just a sign to go get a cup of tea.