Hello, I just installed Nagios XI as Virtual Machine, Hyper-V. Everything went fine, it is up and running, I even changed 'root' password. But, when I try log in to the Web Interface it tells me that my user name or password is incorrect.
Do I use the 'root' user and password or do I need to create a new user for this? I tried to look for information on this but the only thing I found was to use 'nagiosadmin' user, if this is the case what is the password for this user?
I am evaluating this for some potential customers but I need to have a good understanding of Nagios XI. Can you guys provide a link where I can find this information?
I also started to read about how to monitor a Windows Server and its Services. It was good until the instructions talked about how to configure '.cfg' files in the Linux server. I could not find where does files are, It talks about a directory and a windows config file that does not exist in my installation of Nagios. Is there an updated instructions on how to do this?
Please help, thanks
Gus G.
New Nagios install issues
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: New Nagios install issues
Lets first work on getting you up and running, please review the following document for a list of default user/password's for the VM's:
http://assets.nagios.com/downloads/nagi ... _Notes.pdf
http://assets.nagios.com/downloads/nagi ... _Notes.pdf
Re: New Nagios install issues
Thank you slansing,
I got it all working, I am evaluating this application for some customers and I need to really test most if not all of Nagios features.
I set up a Windows 2003 server Host to be monitored by Nagios. I installed the NSClient++ on the server, I then setup the Host in Nagios to monitor CPU, Storage, Memory, and a couple of services and processes. In the Dashboard for this Host I am receiving Warnings saying "could not fetch information from server".
I even tried to set up this Win 2003 server Host using the Windows WMI Wizard to configure server, no NSClient++. In the monitoring dasboard for this server I get "unknown" status with the following message "UNKNOWN - The WMI query had problems. You might have your username/password wrong or the user's access level is too low. Wmic error text on the next line."
What am I doing wrong, I even turned off Firewall in this server.
Thank you much for your help.
I got it all working, I am evaluating this application for some customers and I need to really test most if not all of Nagios features.
I set up a Windows 2003 server Host to be monitored by Nagios. I installed the NSClient++ on the server, I then setup the Host in Nagios to monitor CPU, Storage, Memory, and a couple of services and processes. In the Dashboard for this Host I am receiving Warnings saying "could not fetch information from server".
I even tried to set up this Win 2003 server Host using the Windows WMI Wizard to configure server, no NSClient++. In the monitoring dasboard for this server I get "unknown" status with the following message "UNKNOWN - The WMI query had problems. You might have your username/password wrong or the user's access level is too low. Wmic error text on the next line."
What am I doing wrong, I even turned off Firewall in this server.
Thank you much for your help.
Re: New Nagios install issues
Which version of nsclient did you install? In your nsc.ini or nsclient.ini, you need to set the directive "allowed_hosts" to the ip of your nagios server.
Concerning wmi, have you followed the documentation below?
http://assets.nagios.com/downloads/nagi ... ng_WMI.pdf
One way to test login credentials, is to use WBEMTEST on another windows machine to test the credentials to the checked host.
start > run > WBEMTEST
connect > Namespace = \\<ip address of remote windows machine>\root\cimv2
User: <some admin account>
Password: <some password>
Concerning wmi, have you followed the documentation below?
http://assets.nagios.com/downloads/nagi ... ng_WMI.pdf
One way to test login credentials, is to use WBEMTEST on another windows machine to test the credentials to the checked host.
start > run > WBEMTEST
connect > Namespace = \\<ip address of remote windows machine>\root\cimv2
User: <some admin account>
Password: <some password>
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: New Nagios install issues
Thank you Abrist,
I got Nagios client to work on the winodws 2003 Server, it was the IP Address entry. It is strange, I got the Nagios client to work on a Windows 2008 server without changing any entry in INI file.
I did test the monitored HOST using WBEMTEST, it logged me in with no problem, I am doing a evaluation of Nagios so for right now I will stick with the NSClient++.
Thank you.
I got Nagios client to work on the winodws 2003 Server, it was the IP Address entry. It is strange, I got the Nagios client to work on a Windows 2008 server without changing any entry in INI file.
I did test the monitored HOST using WBEMTEST, it logged me in with no problem, I am doing a evaluation of Nagios so for right now I will stick with the NSClient++.
Thank you.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: New Nagios install issues
Keep in mind, there are some things you will most likely need to change in the nsc.ini file at some point in order to get it's full functionality, what version did you install on that 2008 machine? Glad to hear you got WMI checks up and running.