SQL syntax error when editing services.

[Unigarant]

Code: Select all

SQL Error [nagiosxi] : ERROR:  syntax error at or near "CPU"
LINE 1: ...gios XI','mkaiser',4,'User reconfigured service \'CPU Usage\...

When we edit a service (either using the advanced tab, to change some threshold or via CCM) we get the above error when hitting the apply button.
It does not happen when I bulk edit services, like adding them to a contact group or such...

It seems to apply the changes just fine, we just get the above error type.

I would like to know what causes the error and how to fix it.

[tmcdonald]

Please provide the following information:

• Nagios XI version
• Full name of the service

We would like to try replicating this on our end.

[Unigarant]

Please provide the following information:

• Nagios XI version
• Full name of the service

We would like to try replicating this on our end.

Nagios XI 5.4.10 (and the previous version as well)
At least the check_xi_service_nsclient is affected, probably more.

I have already tried the default SQL DB repair script, no differene.

[dwhitfield]

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.

You can also generate a profile manually using the script at /usr/local/nagiosxi/html/includes/components/profile/getprofile.sh

That should generate a profile in /usr/local/nagiosxi/var/components/ which you can get off the server with an application such as FileZilla.

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