We are running Nagios Core 3.06n8 on suse linux 11 with a separate MYSQL server for reports.
MYSQL ver is 5.0.67. WE would like to move to a CORE version that is supported by Nagios.
Pl let me know the CORE ver that we can upgrade to with min disruption and also keep the MYSQL servers connected
with all funtionalities currently used ( reports/performance colection )
Thank you in advance for your suggestions/recommendations
Ravi
3.0n8 running on Suse Linux 11
Re: 3.0n8 running on Suse Linux 11
What version of ndoutils are you using? Are you using mklivestatus, any other third party brokers, or any other third party addons? (nagiosql, nagvis, etc)
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: 3.0n8 running on Suse Linux 11
So far ndoutils have not been utilized, but we plan on utilizing the plugin after consolidation.
ndoutil1.5.7 is installed.NO 3rd party or addons.
ndoutil1.5.7 is installed.NO 3rd party or addons.
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: 3.0n8 running on Suse Linux 11
Are you sure that ndoutils is 1.5.7, the latest available is 1.5.2, and trunk has not been incremented for a sub version release either. At this time, I would suggest at least 3.4 but 3.5 would work just as well, and not require changes to the db or ndoutils provided you are on 1.5.2.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: 3.0n8 running on Suse Linux 11
Is there an automated way of consolidating 2 Nagios servers after upgrading to CORE 3.5.
We have 4 nagios servers monitoring 800 windows/unix clients.
Plan is to consolidate them to 2 monitoring servers. Currently with CORE 3.06N8 we donot have any
graphical interface to perform import/export
Thanks.
Ravi
We have 4 nagios servers monitoring 800 windows/unix clients.
Plan is to consolidate them to 2 monitoring servers. Currently with CORE 3.06N8 we donot have any
graphical interface to perform import/export
Thanks.
Ravi
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: 3.0n8 running on Suse Linux 11
No there is no way to do this beyond hand scripted solutions, this is partially automated along with many other tasks, in Nagios XI.
Re: 3.0n8 running on Suse Linux 11
Is there a limit on number of clients monitored using Nagios CORE 3.5 running on a SUSE Linux 11.1 VM.
Currently each Nagios 3.0 is monitoring 260 cleints. Plan is to consolidate them to one server with increased resources
Currently each Nagios 3.0 is monitoring 260 cleints. Plan is to consolidate them to one server with increased resources
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: 3.0n8 running on Suse Linux 11
There are no hard limits, but you will need to be careful depending on the server's hardware, how often you are running active checks, and what type of checks you are running. If you have 260 hosts, with roughly 4 services per host, that would put you at around 800-1000 services, which is not that much for a typical, modern server to handle. What are the hardware specs?
Re: 3.0n8 running on Suse Linux 11
We are running on VM with following CPU 's: & 4GB ram. After consolodation we will be moving from $ nagios servers to 2 Nagios servers
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 12
model name : Intel(R) Xeon(R) CPU X5660 @ 2.80GHz
stepping : 2
cpu MHz : 2799.096
cache size : 256 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht syscall nx lm pni cmpxchg16b lahf_lm
bogomips : 5554.17
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 12
model name : Intel(R) Xeon(R) CPU X5660 @ 2.80GHz
stepping : 2
cpu MHz : 2799.096
cache size : 256 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht syscall nx lm pni cmpxchg16b lahf_lm
bogomips : 5603.32
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 12
model name : Intel(R) Xeon(R) CPU X5660 @ 2.80GHz
stepping : 2
cpu MHz : 2799.096
cache size : 256 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht syscall nx lm pni cmpxchg16b lahf_lm
bogomips : 5554.17
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 12
model name : Intel(R) Xeon(R) CPU X5660 @ 2.80GHz
stepping : 2
cpu MHz : 2799.096
cache size : 256 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht syscall nx lm pni cmpxchg16b lahf_lm
bogomips : 5603.32
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
Re: 3.0n8 running on Suse Linux 11
While hardware requirements are not an exact science, the current specs you are running with should suffice. It gets tricky because some checks take a lot more memory or CPU (or both) and that get majorly skew any estimated specifications.
Former Nagios employee