2014R1.2 CCM Stuck in German

[dangladesh]

Somehow my Nagios CCM 1.03 is stuck in German.

Any support I've found directs a user to Config Manager Admin -> Config Manager Settings, but the language option is only available in the Legacy CCM (changing it there does not affect CCM 1.03).

Any help would be greatly appreciated.

[abrist]

Lets check your user in the ccm and see what language is set:

Code: Select all

echo "select id,username,locale from nagiosql.tbl_user;" | mysql -t -pnagiosxi

[dangladesh]

Wunderbar, danke!!

This select revealed that the user locale was set to de_DE. I was able to change it with the following:

Code: Select all

echo "update nagiosql.tbl_user set locale='en_EN' where username='<username>';" | mysql -t -pnagiosxi

I wonder how it ever got set to German in the first place.

[dangladesh]

Unfortunately, after logging out, rebooting the nagios machine, and logging back into CCM, it is still in German.

Do I have to apply a configuration or something like that?

[abrist]

That query doesn't fix anything. I wanted to see the output to try to determine if the ccm was pulling the lang from the table . . . .

[dangladesh]

Okay. 'locale' was set to 'de_DE'

But I don't think that it is pulling the language from the table, because now 'locale' is set to 'en_EN' for the user.

[dangladesh]

Are there other places I could look for language configuration? Where can I go from here?

[dangladesh]

After updating the locale field in the tmp_user table to en_EN, the CCM did not recognize this change (even after a cache clear, reboot of nagios server, etc). After "Updating Credentials" (via a password reset) for the user, the CCM displayed the proper language. I am wondering if this change caused the CCM to look at the settings in the table that would have otherwise been stored somewhere else?

This seems to have solved my problem.

[abrist]

It may have been a mismatch between the CCM locale in the nagiosql mysql db table and the postgresql user settings. (As both are updated when you change locales)
I am glad that it is fixed. When I get time I will investigate the tables a bit more to try to reproduce the behavior. Cheers!