Nagios Support Forum

What is winbindd doing for you?
=> I don't know
we need to know how and why this would have been altered
=> From what I could recall, the rights may have been changed by the Nagios support to solve the post below
Please take a look at that post :

2012 R1.6 : apply configuration doesn't work Attachment(s)
by Frédéric GRANAT » Mon Mar 04, 2013

Well, I can say that windbindd is not standard on our systems, and I would doubt that any of us would tell you to change the nagios uid as it will definitely cause issues, as you have found unfortunately. I think it is rather vital that you find out what the software is doing and how it is configured, as winbindd is specifically for managing linux users from a M$ AD system.

As for temporarily resolving this, you might try some steps that you have previously, by running the reconfigure_perms script, however ideally once the nagios user is back to uid 500, you will need to run it again.

Run the following commands: Then also run the following command to begin capturing log output: Attempt to Apply Configuration from the web interface. After the browser has returned some output to the screen, press Ctrl+C to stop the log tail, and post cmd.txt file and the reconfig.txt that was generated by the above instructions.

I can say that windbindd is not standard on our systems
=> I think that windbindd was natively installed when Linux was installed

and I would doubt that any of us would tell you to change the nagios uid
=> According to the post of March, it seems that one of yours adviced me to replace the user 500 by the user Nagios for some particular files (Postby mguthrie » Mon Mar 18, 2013 9:20 am)

I think it is rather vital that you find out what the software is doing and how it is configured, as winbindd is specifically for managing linux users from a M$ AD system.
=>

Found on the net :

winbind is ONLY necessary if you are participating in a windows
controlled domain and need the users defined on your windows domain to
have permissions/logins on your samba server without having local users
set up and mapped manually.

Our nagios server is not in the AD system, could you please give me the commands to add it to the AD ?

Frederic

Mike telling you to change the user to nagios from the uid 500, would have been post the uid of the nagios user changing, and I would agree that he likely said this. I can say this because our installer sets the uid to 500 by default, and with your files having that set as the uid correctly, the nagios user at one point was using uid 500. His previous changes were much the same as what I suggested for a temporary fix, to change the file permissions from the current uid of 500, that has no user associated, to the nagios user. Again this is less than ideal as there are many files that may need to be altered. At no point did he say to alter the uid in /etc/passwd of the nagios user, as that would cause the breakage that is happening now. As for winbindd, this may be installed with samba or smbd, but it is not default with a minimal cent\rhel install on systems that I have checked, might this be part of an internal build setup at your company?

As for commands to add an XI system to AD, that is out of the scope of our support. If you wish to integrate the base linux OS with AD, I am sure there are guides out there. As for web\XI integration, we do cover that, and it can be found in the Active Directory Integration document.

At no point did he say to alter the uid in /etc/passwd of the nagios user
=> I never changed something that hasn't been asked to me, so never change anything in /etc/passwd

might this be part of an internal build setup at your company?
=> No, Install Linux and install Nagiosxi

Just be sure that the UID for the nagios user does not change from 500.. This is set by our installed by default as noted above and would have had to have been changed after the fact, or the line removed from our installed in order for this to happen. I'm going to lock this up now as the resolution has been reached, and it appears that either someone change the UID by hand, commented the corresponding lines out of our installed and set the user up before installing, or something such as windbindd changed it. If you run into issues working with the AD component let us know in a new thread and we will help troubleshoot there.