Your message dated Wed, 06 Apr 2005 09:32:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#299613: fixed in nagios 2:1.3-cvs.20050402-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 15 Mar 2005 12:04:16 +0000
>From [EMAIL PROTECTED] Tue Mar 15 04:04:16 2005
Return-path: <[EMAIL PROTECTED]>
Received: from s2.ukfsn.org (mail.ukfsn.org) [217.158.120.143] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DBAmV-0006pj-00; Tue, 15 Mar 2005 04:04:15 -0800
Received: from localhost (lucy.ukfsn.org [127.0.0.1])
        by mail.ukfsn.org (Postfix) with ESMTP id A3525E6D81
        for <[EMAIL PROTECTED]>; Tue, 15 Mar 2005 11:59:08 +0000 (GMT)
Received: from mail.ukfsn.org ([127.0.0.1])
 by localhost (lucy.ukfsn.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 16042-02 for <[EMAIL PROTECTED]>;
 Tue, 15 Mar 2005 11:59:08 +0000 (GMT)
Received: from oak.dgreaves.com (modem-2956.lion.dialup.pol.co.uk 
[217.135.171.140])
        by mail.ukfsn.org (Postfix) with ESMTP id 24424E6D95
        for <[EMAIL PROTECTED]>; Tue, 15 Mar 2005 11:59:06 +0000 (GMT)
Received: from ash.dgreaves.com ([10.0.0.90])
        by oak.dgreaves.com with esmtp (Exim 4.20)
        id 1DBAmQ-00017C-3E
        for [EMAIL PROTECTED]; Tue, 15 Mar 2005 12:04:10 +0000
Received: from david by ash.dgreaves.com with local (Exim 4.44)
        id 1DBAmP-0001Tb-U3
        for [EMAIL PROTECTED]; Tue, 15 Mar 2005 12:04:09 +0000
Content-Type: multipart/mixed; boundary="===============0244242169=="
MIME-Version: 1.0
From: David Greaves <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: nagios-mysql: Confusing installation documentation
X-Mailer: reportbug 3.8
Date: Tue, 15 Mar 2005 12:04:09 +0000
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

This is a multi-part MIME message sent by reportbug.

--===============0244242169==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: nagios-mysql
Severity: important
Tags: patch

The installation instructions are incomplete and have lead to at least 1
bug report.
I've made some minor edits which I hope will help.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.2-ash-050309-01
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--===============0244242169==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="README.mysql.patch"

*** /usr/share/doc/nagios-mysql/README.mysql    Thu Feb 17 17:39:03 2005
--- /usr/share/doc/nagios-mysql/README.mysql.new        Tue Mar 15 12:01:29 2005
***************
*** 16,22 ****
  
  $ mysqladmin -u root -p create nagios
  
! $ zcat /usr/share/doc/nagios-mysql/create_mysql.sql.gz | mysql -u root -p 
nagios
  
  When prompted for a password, please enter the password you choosed when 
  configuring the package at install time... If you did not set a password,
--- 16,22 ----
  
  $ mysqladmin -u root -p create nagios
  
! $ zcat /usr/share/doc/nagios-mysql/create_mysql.gz | mysql -u root -p nagios
  
  When prompted for a password, please enter the password you choosed when 
  configuring the package at install time... If you did not set a password,
***************
*** 45,50 ****
--- 45,52 ----
  be sure to make them NOT world readable by issuing something like
  chmod o= /etc/nagios/resource.cfg.
  
+ First, how to do it by hand, then there's a sed script that may help:
+ 
  1) /etc/nagios/resource.cfg
  
  Uncomment and set the following lines to appropriate values, replacing
***************
*** 75,80 ****
--- 77,112 ----
  At the bottom of this file, you'll find the similar lines commented
  out as were in the previous one.  Do the same here.
  
+ This sed script assumes you have a local database on a standard port
+ with a database/user/password of nagios/nagios/password
+ 
+ sed -i.orig '
+ s/#x\(.\)ddb_database=somedatabase/x\1ddb_database=nagios/;
+ s/#x\(.\)ddb_username=someuser/x\1ddb_username=nagios/;
+ s/#x\(.\)ddb_password=somepassword/x\1ddb_password=password/;
+ ' /etc/nagios/cgi.cfg /etc/nagios/nagios.cfg
+ 
+ Then you want the cgi-script and the init.d script to correctly know the
+ status of nagios. You need the check_nagios_db file from
+ /usr/doc/nagios-common/, put it where you like but adjust the pathes in
+ the following examples. I REALLY suggest /etc/nagios/check_nagios_db as
+ the init-script now already looks if it is there and will use it
+ automagically.
+ If you use PostgreSQL you need to change the line
+ my $driver = "mysql"; in the script to
+ my $driver = "Pg";
+ 
+ Make it executable:
+ sudo chmod +x /etc/nagios/check_nagios_db
+ 
+ Now edit the /etc/nagios/cgi.cfg and put a # in front of the line
+ nagios_check_command=/usr/lib/nagios/plugins/check_nagios 
/var/log/nagios/status.log 5 'nagios'
+ 
+ and remove the # in front of the line
+ nagios_check_command=/etc/nagios/check_nagios_db
+ 
+ now start nagios
+ 
  You should now be up and running enough to get started.  You'll still
  need to edit your /etc/nagios/hosts.cfg and other files, but you'll be
  able to see that the default machines in there are now on the web

--===============0244242169==--

---------------------------------------
Received: (at 299613-close) by bugs.debian.org; 6 Apr 2005 13:49:46 +0000
>From [EMAIL PROTECTED] Wed Apr 06 06:49:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DJAuf-0002gF-00; Wed, 06 Apr 2005 06:49:45 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DJAdr-0007bn-00; Wed, 06 Apr 2005 09:32:23 -0400
From: sean finney <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#299613: fixed in nagios 2:1.3-cvs.20050402-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 06 Apr 2005 09:32:23 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 7

Source: nagios
Source-Version: 2:1.3-cvs.20050402-1

We believe that the bug you reported is fixed in the latest version of
nagios, which is due to be installed in the Debian FTP archive:

nagios-common_1.3-cvs.20050402-1_all.deb
  to pool/main/n/nagios/nagios-common_1.3-cvs.20050402-1_all.deb
nagios-mysql_1.3-cvs.20050402-1_i386.deb
  to pool/main/n/nagios/nagios-mysql_1.3-cvs.20050402-1_i386.deb
nagios-pgsql_1.3-cvs.20050402-1_i386.deb
  to pool/main/n/nagios/nagios-pgsql_1.3-cvs.20050402-1_i386.deb
nagios-text_1.3-cvs.20050402-1_i386.deb
  to pool/main/n/nagios/nagios-text_1.3-cvs.20050402-1_i386.deb
nagios_1.3-cvs.20050402-1.diff.gz
  to pool/main/n/nagios/nagios_1.3-cvs.20050402-1.diff.gz
nagios_1.3-cvs.20050402-1.dsc
  to pool/main/n/nagios/nagios_1.3-cvs.20050402-1.dsc
nagios_1.3-cvs.20050402.orig.tar.gz
  to pool/main/n/nagios/nagios_1.3-cvs.20050402.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
sean finney <[EMAIL PROTECTED]> (supplier of updated nagios package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 05 Apr 2005 00:47:23 -0400
Source: nagios
Binary: nagios-pgsql nagios-text nagios-mysql nagios-common
Architecture: source i386 all
Version: 2:1.3-cvs.20050402-1
Distribution: unstable
Urgency: low
Maintainer: Debian Nagios Maintainer Group <[EMAIL PROTECTED]>
Changed-By: sean finney <[EMAIL PROTECTED]>
Description: 
 nagios-common - A host/service/network monitoring and management system
 nagios-mysql - A host/service/network monitoring and management system
 nagios-pgsql - A host/service/network monitoring and management system
 nagios-text - A host/service/network monitoring and management system
Closes: 283947 292473 299467 299470 299613 301099 301105 302245 302994
Changes: 
 nagios (2:1.3-cvs.20050402-1) unstable; urgency=low
 .
     - new upstream cvs snapshot (bugfixes and doc updates only).
     - somehow nagios got packaged as a debian-native package.  oops.
       thanks to Stephen Gran <[EMAIL PROTECTED]> for pointing out
       the mistake (closes: #302245).
     - remove duplicate call do db_purge in maintainer scripts
     - remove duplicate call to invoke-rc.d in maintainer scripts, thanks
       to alban browaeys <[EMAIL PROTECTED]> (closes: #301099).
     - don't jump the gun and use htpasswd-caudium just because it exists.
       instead, make sure that the admin has also not selected to configure
       nagios for apache variants (in which case htpasswd should stay as
       the nagios htpasswd).  thanks again to alban (closes: #301105).
     - check_started was broken for reloading nagios-pgsql and nagios-mysql.
       thanks to Olleg Samoylov <[EMAIL PROTECTED]> (closes: #299470).
     - plugins would break in environments that use commas in their floating
       points.  as a workaround, set LC_NUMERIC=POSIX in the init script.
       thanks again to Olleg Samoylov <[EMAIL PROTECTED]> (closes: #299467).
     - documentation changes suggested by David Greaves <[EMAIL PROTECTED]>
       (closes: #299613).
     - added a note about heavily loaded servers in README.Debian
       (closes: #283947, #292473).  thanks to Cyril Bouthors <[EMAIL 
PROTECTED]>.
     - updated README.Debian, removing various out-of-date info, and putting
       in a little more about virtual hosts with apache.
     - also updated NEWS, as it looks like the recent side.html change broke
       the configs of some people who were using nagios in a virtualhost.  note
       that a simple fix exists, see README.Debian :)
     - change and clarification in the default contacts.  thanks to
       alban (closes: #302994).
Files: 
 7b4caa20e606dd4f9d53f50b20b6f9f1 1021 net optional 
nagios_1.3-cvs.20050402-1.dsc
 0f92b7b8e705411b7881d3650cbb5d56 1621251 net optional 
nagios_1.3-cvs.20050402.orig.tar.gz
 3d297ce0143142929442a2022e390440 64408 net optional 
nagios_1.3-cvs.20050402-1.diff.gz
 773a70d04bc47910a6c433d2293a4e1a 901316 net optional 
nagios-text_1.3-cvs.20050402-1_i386.deb
 68e37489ad6e230ddd5a6f43b5fb64a6 906498 net optional 
nagios-mysql_1.3-cvs.20050402-1_i386.deb
 9ee311660bdf2e80c162f18b7d8c43e7 916970 net optional 
nagios-pgsql_1.3-cvs.20050402-1_i386.deb
 ac7b4c4c6b90e48e50fc070f3e4f9349 1217990 net optional 
nagios-common_1.3-cvs.20050402-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCU+FyynjLPm522B0RAuwvAJ9l0hKRcHeuKv0RAauMyHSyTvfKGwCfbrwj
F15nCY49c8uU+FMvkuWsrc4=
=foed
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to