NagMIN - Null Values - FreeBSD

Fred Reimers FReimers at infosysinc.com
Fri May 23 22:05:09 CEST 2003


Eric, et.al:
 
I've been able to recreate the NULL problem on FreeBSD that doesn't
happen on RedHat 7.3.
 
I built a FreeBSD(4.8) server with MySQL 4.0.10-gamma and now see the
NULL values in the configuration files.
 
I'm also using the FreeBSD Nagios package and see why some of you wanted
better control over directories.  
 
What I don't know is why it worked with RedHat 7.3 and not RedHat 9.0.
I'm not going to find out either since I'm also having memory management
problems with RedHat and have no plans to use RedHat 9.0.
 
I'll hopefully have this fixed by early next week.
 

------------------------------------------------- 
Fred Reimers (CCIE #1469, CCSA) 
Senior Network Consultant 
Info Systems, Inc. 
freimers at infosysinc.com 

-----Original Message-----
From: Eric Austin 
Sent: Tuesday, May 13, 2003 12:56 PM
To: Fred Reimers
Subject: RE: NagMIN



Fred,

     Glad to help.  FYI, none of the system calls appear to be working
either.  This may be a configuration issue on my part but the rest of
the WebMIN tools seem to be working OK.  I hacked my way around it for
now.  I see it try to do an "ssh service nagios restart" but nothing
happens.  Should the IP address be included in the command after ssh?
No big rush, like I said I've got a work around.

 

Eric

 

-----Original Message-----
From: Fred Reimers 
Sent: Monday, May 12, 2003 4:25 PM
To: Eric Austin
Subject: RE: NagMIN

 

Eric,

 

This will be a big help.  I'll get back to you soon.

 

 

Fred

 

-----Original Message----- 
From: Eric Austin 
Sent: Mon 5/12/2003 9:56 AM 
To: Fred Reimers 
Cc: 
Subject: RE: NagMIN

 

-----Original Message----- 
From: Fred Reimers 
Sent: Mon 5/12/2003 9:49 AM 
To: Eric Austin 
Cc: 
Subject: RE: NagMIN

Eric,

 

This appears to be a MySQL problem with RH9.  

 

NagMIN is handling NULL values per the MySQL ntation and works fine with
any RedHat version up to RH9.  

 

Per MySQL, you have to enter the word NULL or you get an empty string
instead of a true NULL character.

 

This will require some more investigation.  

 

Could you email me your nagmin_load.sql file and a dump of your
database?

 

Thanks,

 

Fred

 

 

 

-----Original Message----- 
From: Eric Austin 
Sent: Mon 5/12/2003 9:16 AM 
To: Fred Reimers 
Cc: 
Subject: RE: NagMIN

Fred,

 

They are NULL from the get go.  I reran setup, created a new database
and did a SELECT * FROM Service.Template; and it showed NULL values.

 

Eric

-----Original Message----- 
From: Fred Reimers 
Sent: Mon 5/12/2003 9:01 AM 
To: Eric Austin 
Cc: 
Subject: RE: NagMIN

Eric,

 

Thanks, starting to nail this one down, although I'm not sure how to fix
it.

 

One more question.  Does the initial loading of the database show NULL
values, or only after you edit something with NagMIN?

 

Fred

 

-----Original Message----- 
From: Eric Austin 
Sent: Mon 5/12/2003 7:58 AM 
To: Fred Reimers 
Cc: 
Subject: RE: NagMIN

Yes, the NagMINdatabase tables show a value of NULL unless I set it to
"".

 

Eric

-----Original Message----- 
From: Fred Reimers 
Sent: Mon 5/12/2003 7:57 AM 
To: Eric Austin 
Cc: 
Subject: RE: NagMIN

Eric,

 

This problem appears to only be happening with people using freebsd and
now RH9.  The difference is probably with perl and the MySQL DBD
modules.  I'm looking for values to ignore and not write the objects.
The perl DBD module appears to now be returning a string "NULL" instead
of a null value since you are seeing "NULL" as the object value.  In
that case ( if $object eq undef ), the perl way of checking for a null
value, won't work.  I may have to check for ( if $object eq "NULL" ).

 

Are you seeing the value "NULL" in the NagMIN database tables?

 

 

Fred

 

-----Original Message----- 
From: Eric Austin 
Sent: Mon 5/12/2003 6:40 AM 
To: Fred Reimers 
Cc: 
Subject: RE: NagMIN

Fred,

     I'm using RH9 anf MySQL 3.23.54.  If I do a mysqldump on any
database with null values, the SQL output has a value of NULL rather
than "".  I guess the easiest way to handle it would be to have your cgi
script check IF NULL THEN VALUE = ""; when dumping values to cfg files.

 

Eric

-----Original Message----- 
From: Fred Reimers 
Sent: Sat 5/10/2003 7:21 AM 
To: Eric Austin 
Cc: 
Subject: RE: NagMIN

Eric,

 

I'm trying to get a handle on the NULL value problem.  In the version of
MySQL I'm using,  NULL is the only way to enter a null value.

 

What OS and version of MySQL are you using?

 

 

Fred

 

-----Original Message----- 
From: Eric Austin 
Sent: Sat 5/10/2003 6:54 AM 
To: Fred Reimers 
Cc: 
Subject: RE: NagMIN

Fred,

    Thanks, that's just what I did.  I'm having some issues with the
verification not liking NULL values but if I replace them with "" in the
database, all seems good.

 

Eric

-----Original Message----- 
From: Fred Reimers 
Sent: Sat 5/10/2003 5:05 AM 
To: Eric Austin 
Cc: 
Subject: RE: NagMIN

Eric,

 

Not everyone, probably most, do not install Nagios with MySQL support.
If you have, then choose a different database name when installing
NagMIN.  It will drop whatever database with the name you select to
create its own.

 

 

Fred

 

-----Original Message----- 
From: Eric Austin 
Sent: Fri 5/9/2003 2:59 PM 
To: Fred Reimers 
Cc: 
Subject: NagMIN

Fred,
    I'm trying to get NagMIN setup and running and have run into a
problem.  Here's what I've done:

Installed and Configured Nagios w/ MySQL support database name 'nagios'
Monitored 1 object for testing - works OK
Discovered NagMIN (Recommended by Chris Patterson)
Installed NagMIN and prerequisits
Allowed NagMIN setup routine to drop/create database called 'nagios'
Nagios no longer runs

Should I have given my NagMIN database a different name?  Should I not
have used MySQL with the initial Nagios installation?  Please advise.

Thanks,
Eric

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20030523/162b2d85/attachment.html>


More information about the Users mailing list