WMI - Backend login to the Core Config Manager failed.

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
[email protected]
Posts: 52
Joined: Wed Nov 12, 2014 3:09 pm

Re: WMI - Backend login to the Core Config Manager failed.

Post by [email protected] »

Yes the /etc/wgetrc is setup for proxy:

http_proxy=http://172.16.2.203:80/ # All in one string this time
https_proxy=https://172.16.2.203:80/ # Only required if you have a HTTPS proxy
no_proxy=localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,*.grhc.local,*.clinicalkey.com,*.mckesson.com,*.uptodate.com,*.amerisourcebergen.com,sym-end-01,grhc-vs-sav-01,grhc-midas,moonwalk,grhc-trn,grhc-vs-sig06,grhcfac03,sde,xen,xen-web-01,xen-web-02,vpn.aznet.gov,*.local


And the /etc/yum.conf is setup for proxy also:

[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=5
bugtracker_url=http://bugs.centos.org/set_project.php? ... tegory=yum
distroverpkg=centos-release
proxy=http://172.16.2.203:80/
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: WMI - Backend login to the Core Config Manager failed.

Post by dwhitfield »

It might be best at this point to move this to a ticket: [email protected]. If you want to do that, please reference this forum thread.

Alternatively, 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.

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.
[email protected]
Posts: 52
Joined: Wed Nov 12, 2014 3:09 pm

Re: WMI - Backend login to the Core Config Manager failed.

Post by [email protected] »

Here is the profile...
profile.zip
You do not have the required permissions to view the files attached to this post.
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: WMI - Backend login to the Core Config Manager failed.

Post by dwhitfield »

It's hard to know if this will fix the issue at hand, but there definitely some issues in your profile that need to be addressed.

Regarding the instructions below, if you do not have killall, you can install it via the following command:
# yum install psmisc

If psmisc is not in your repos, then instead you can check to make sure nagios is not running with
# ps -aef | grep nagios

If that document does not resolve your issue, please run the following commands in order and report any errors. You ***must*** use mariadb instead of mysqld in the commands below, ***if*** you have mariadb.
# service nagios stop
# service ndo2db stop
# service mysqld stop
# service crond stop
# service httpd stop
# killall -9 nagios
# killall -9 ndo2db
# rm -rf /usr/local/nagios/var/rw/nagios.cmd
# rm -rf /usr/local/nagios/var/nagios.lock
# rm -f /usr/local/nagios/var/ndo.sock
# rm -f /usr/local/nagios/var/ndo2db.lock
# rm -f /usr/local/nagiosxi/var/reconfigure_nagios.lock
# for i in `ipcs -q | grep nagios |awk '{print $2}'`; do ipcrm -q $i; done
# service ndo2db start
# service nagios start
# service mysqld start
# service crond start
# service httpd start

If that does not resolve the issue, please generate and post a new profile.
[email protected]
Posts: 52
Joined: Wed Nov 12, 2014 3:09 pm

Re: WMI - Backend login to the Core Config Manager failed.

Post by [email protected] »

I tried a different server and same issue. Profile attached...

Also I had to run this script that I found on the forum to get access to the WMIAGENT on the client:

C:\Windows\system32>wmic useraccount where name='wmiagent' get sid
SID
S-1-5-21-3194300723-1584388699-3506550038-1001


C:\Windows\system32>sc sdset SCMANAGER D:(A;;CCLCRPRC;;;S-1-5-21-3194300723-1584
388699-3506550038-1001)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)S:(AU;FA;KA;;;WD)(AU;OIIO
FA;GA;;;WD)
[SC] SetServiceObjectSecurity SUCCESS
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: WMI - Backend login to the Core Config Manager failed.

Post by tgriep »

FYI, changing the WMI settings on the Windows server has noting to do with the the Backend login to the Core Config Manager.
It just happened when you are running the wizard.

Can you login to the XI GUI and go to the Core Config Manager > CCM Admin > Settings menu and click on the Paths tab.
If the Server Protocol is not set to HTTPS, set it and save the settings.
Then see if you can Apply the Config or run the reconfigure script in a shell using the following procedure.

Code: Select all

su - nagios
cd /usr/local/nagiosxi/scripts
./reconfigure_nagios.sh
Let us know when you change to the nagios user account, it if asks for a password.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked