Bug#290681: [Pkg-nagios-devel] Bug#290681: sparc version is using file based extinfo instead of sql tables

sean finney sean finney <seanius@debian.org>, 290681@bugs.debian.org
Sun, 16 Jan 2005 15:42:45 -0500


--ZPt4rx8FFjLCG7dd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

hi roy,

i've made a change that i believe fixes this, and i'm building the
packages right now.  if you'd like i can send you a link to the package
when i'm done and you can verify that it works before we upload=20
the next version.


	sean

On Sun, Jan 16, 2005 at 02:58:16PM -0500, Roy Bonser wrote:
> Thanks, got bit by the mysql-server bug too. I back rev'd that one.
> Looking through the build log I see three different configure options=20
> listed for extinfo and it seems the first one got used:
>=20
> CFLAGS=3D'-g -O2' ./configure --prefix=3D/usr --mandir=3D/usr/share/man=
=20
> --bindir=3D/usr/sbin --sbindir=3D/usr/lib/cgi-bin/nagios=20
> --datadir=3D/usr/share/nagios/htdocs --sysconfdir=3D/etc/nagios=20
> --infodir=3D/usr/share/info --libexecdir=3D/usr/lib/nagios/plugins=20
> --localstatedir=3D/var/log/nagios --with-ping-command=3D"/bin/ping -n %s =
-c=20
> %d" --with-mail=3D/usr/bin/mail --with-perlcache=20
> --with-nagios-user=3Dnagios --with-nagios-grp=3Dnagios=20
> --with-template-objects --with-template-extinfo --with-default-extinfo =
=20
> --with-mysql-comments --with-mysql-downtime --with-mysql-extinfo=20
> --with-mysql-retention --with-mysql-status --with-mysql-xdata
>=20
> ...
>=20
> We'll use MySQL database routines (in xdata/xsddb.*) for status data=20
> I/O...
> We'll use MySQL database routines (in xdata/xcddb.*) for comment data=20
> I/O...
> We'll use template-based routines (in xdata/xedtemplate.*) for extended=
=20
> data I/O...
> We'll use MySQL database routines (in xdata/xrddb.*) for retention data=
=20
> I/O...
> We'll use template-based routines (in xdata/xodtemplate.*) for object=20
> data I/O...
> We'll use default routines (in xdata/xpddefault.*) for performance data=
=20
> I/O...
> We'll use MySQL database routines (in xdata/xdddb.*) for scheduled=20
> downtime data I/O...
>=20
> ...
>=20
> *** Configuration summary for nagios 1.3 10-24-2004 ***:
>=20
>  General Options:
>  -------------------------
>         Nagios executable:  nagios
>         Nagios user/group:  nagios,nagios
>        Command user/group:  nagios,nagios
>             Embedded Perl:  no
>         Install ${prefix}:  /usr
>                 Lock file:  /var/log/nagios/nagios.lock
>            Init directory:  /etc/init.d
>=20
>  Web Interface Options:
>  ------------------------
>                  HTML URL:  http://localhost/nagios/
>                   CGI URL:  http://localhost/nagios/cgi-bin/
>  Traceroute (used by WAP):
>=20
>  External Data Routines:
>  ------------------------
>               Status data:  Database (MySQL)
>               Object data:  Template-based (text file)
>              Comment data:  Database (MySQL)
>             Downtime data:  Database (MySQL)
>            Retention data:  Database (MySQL)
>           Peformance data:  Default (external commands)
>        Extended info data:  Template-based (text file)
>=20
>=20
> Review the options above for accuracy.  If they look okay,
> type 'make all' to compile the main program and CGIs.
>=20
> btw, it looks like the same problem with nagios-pgsql
>=20
> External Data Routines:
>  ------------------------
>               Status data:  Database (PostgreSQL)
>               Object data:  Template-based (text file)
>              Comment data:  Database (PostgreSQL)
>             Downtime data:  Database (PostgreSQL)
>            Retention data:  Database (PostgreSQL)
>           Peformance data:  Default (external commands)
>        Extended info data:  Template-based (text file)
>=20
> Hope this helps,
>   --Roy
>=20
> On Jan 16, 2005, at 2:36 PM, sean finney wrote:
>=20
> >On Sun, Jan 16, 2005 at 02:23:45PM -0500, Roy Bonser wrote:
> >>1.2-3.6 - I'm running the testing version.
> >
> >okay, so this was a woody-sarge version upgrade then.  fyi you'll
> >want to take a look at #289762 if you're upgrading your mysql
> >server too.
> >
> >i'll look into what's causing the failure for extended info,
> >probably something got left out when we took over the package.
> >
> >
> >	sean
> >
> >--=20
>=20

--=20

--ZPt4rx8FFjLCG7dd
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFB6tHFynjLPm522B0RAkj6AJ9ebcpdTZDnFCw8OcQALdIUJ3RS1ACfSFkE
wNOQl2JU/qd6MtGO3JWzUt8=
=gLob
-----END PGP SIGNATURE-----

--ZPt4rx8FFjLCG7dd--