2.12.1 on SLES10, is there a simple way to upgrade to 2.12.9 on this
platform (64bit on the Master, a mix of 64 and 32 bit on the slaves with a
couple of them running SUSE 9.2 Pro), is it just the master that would
require upgrade, I have a hot-standby clone of my live server I could  use
for upgrading/testing.
 
I am in the process of pushing to use Debian and rebuild all the machines,
this issue may be just the leverage I need.
 
With slaves installed with 2.12.1, running SUSE9 and SUSE10 in 32 and 64 bit
versions, if I build a 2.14 Debian server, will it allow me to use the
exsisting slaves, so that I can do a rolling upgrade of the OS ?
 
It is my goal to upgrade to version 3.x, if for no reason other than LDAP
support.
 
Thanks for all your help in this, I knew I was in for a world of pain when I
failed to win the argument about using an unsupported OS.

David

 
 


  _____  

From: [email protected]
[mailto:[email protected]] On Behalf Of Ton Voon
Sent: 09 July 2009 16:25
To: Opsview Users
Subject: Re: [opsview-users] Hostgroup Caching ?


Hi David, 

On 9 Jul 2009, at 16:12, David Bell wrote:


Thanks for the response Raf.
 
Yes the Nagios cgi pages are correct - I assume that is because its reading
that info from files.
 
My opsviewd.log does have a few import issues that seem to co-incide with
when we see problems - I am concerned about the one at the top of this list
 
[2009/07/08 17:44:54] [import_ndologsd] [WARN] Import of 1247068819470548,
size=35240212, took 2674.88318109512 seconds > 5 seconds
[2009/07/08 17:45:02] [import_ndologsd] [WARN] Import of 1247068821483999,
size=86727, took 8.11954402923584 seconds > 5 seconds
[2009/07/08 17:45:34] [import_ndologsd] [WARN] Import of 1247068834758987,
size=2306127, took 28.0002701282501 seconds > 5 seconds
[2009/07/08 17:45:51] [import_ndologsd] [WARN] Import of 1247068844539990,
size=1401907, took 16.6511950492859 seconds > 5 seconds
[2009/07/08 17:46:07] [import_ndologsd] [WARN] Import of 1247068852496928,
size=1386952, took 16.3429758548737 seconds > 5 seconds
[2009/07/08 17:46:32] [import_ndologsd] [WARN] Import of 1247068863620525,
size=2233089, took 25.1329939365387 seconds > 5 seconds
[2009/07/08 17:46:45] [import_ndologsd] [WARN] Import of 1247068871060241,
size=1083300, took 13.0434839725494 seconds > 5 seconds
[2009/07/08 17:47:10] [import_ndologsd] [WARN] Import of 1247068949423567,
size=537320, took 6.85540199279785 seconds > 5 seconds
[2009/07/08 17:52:54] [import_ndologsd] [WARN] Import of 1247070234375124,
size=100348, took 5.26332020759583 seconds > 5 seconds
 
We are using a remote server for the mySQL database which is of a very high
spec, hardware is Sun, it has 16GB of RAM etc, so I dont think the database
server is the issue - so although we dont have the innodb optimisations on
it (it hosts a few databases) I dont think this is the problem. 
 
I am currently thinking that it may be a network issue between the Master
and the Database server - is this likely?


What sub version of Opsview are you on?

In 2.12.9, we did some big improvements to the import time for large scale
systems, which have carried over to the current versions.

You really need to upgrade to see these benefits though.

Ton



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users

Reply via email to