Hello Richard, Am Sat, 25 Oct 2008 10:24:20 -0700 schrieb Richard Hecker <[EMAIL PROTECTED]>:
> Package: munin-node
> Version: 1.2.6-7
> Severity: important
>
> In previous months, munin-node was working so this might just be a
> symptom of another problem introduced when I started to pull in some
> testing packages on this stable system. When I saw the error from my
> dpkg --purge attempts, I felt compelled to send this report because
> an unclean purge could interfere with the next install.
>
> About a month ago, the munin data from this system stopped appearing
> on the graphs. I tried my typical apt-get install --reinstall
> munin-node response. For some reason, no error messages show up
> during a --reinstall. But if I use dpkg --purge munin-node to clear
> the slate, on the next install I always get the following error
> messages:
thanks for the bugreport!
> Setting up munin (1.2.6-7) ...
> Setting up munin-node (1.2.6-7) ...
> Initializing plugins..# There were some errors:
> # Got junk from postgres_space_: DBI connect('','',...) failed:
> FATAL: Ident authentication failed for user "nobody"
> at /usr/share/munin/plugins/postgres_space_ line 62 # Got junk from
> postgres_queries_: DBI connect('','',...) failed: FATAL: Ident
> authentication failed for user "nobody"
> at /usr/share/munin/plugins/postgres_queries_ line 98 # Got junk from
> postgres_block_read_: DBI connect('','',...) failed: FATAL: Ident
> authentication failed for user "nobody"
> at /usr/share/munin/plugins/postgres_block_read_ line 96 # Got junk
> from postgres_commits_: Use of uninitialized value $maybe_dbname in
> string eq at /usr/share/munin/plugins/postgres_commits_ line 111. #
> Got junk from postgres_commits_: DBI connect('','',...) failed:
> FATAL: Ident authentication failed for user "nobody"
> at /usr/share/munin/plugins/postgres_commits_ line 130 done.
> Starting Munin-Node: done.
This output comes from munin-node-configure in postinst. While
initializing the postgresql plugins we check the munin environment.
If nothing is configured we use the defaults to test a connection
to the database. If you want to use the postgres plugins take a look
in the plugins there is some documentation:
# Configuration variables:
#
# PGHOST - Database server to use. Defaults to using ident
# authentication with the local server.
# PGPORT - Port to connect to. Defaults to '5432'.
# PGDATABASE - Database to connect to. Defaults to 'template1'.
# PGUSER - User to connect as, if necessary.
# PGPASSWORD - Corresponding password to use, if necessary.
#
# (See libpq documentation for more.)
# Note that PGDATABASE will default to 'template1' in this
plugin, and
# without PGHOST it will try ident authentication with the local
server,
# as the user that the plugin is running as.
#
# Configuration example:
#
#
# Use local server, ident authentication with the 'postgres' user.
# [postgres_*]
# user postgres
#
#
# Use local server, TCP authentication with a username and password.
# [postgres_*]
# env.PGHOST localhost
# env.PGUSER someuser
# env.PGPASSWORD somepassword
#
>
> It puzzles me why a --reinstall does not generate these error
> messages. An example of the --reinstall follows below:
This behavior is normal because during a "reinstall" only newer plugins
(== new in this package version) are initialized in postinst
(munin-node-configure --newer...). If you purge and reinstall the
package all plugins are initialized in postinst.
> The errors on dpkg --purge are less consistent. The initial attempts
> complained about directories not being deleted and I manually deleted
> them. Since I started to type this message and have been cutting and
> pasting from another window, I am unable to reproduce the errors I
> previously saw. I was not rigorous in using a script to return to
> the same pristine condition on each attempt. It is possible that the
> errors were related to some intermediate state where only some of the
> directories were manually deleted. I remember the error message
> talking about post-removal issues but I cannot reproduce it to cut
> and paste into this email.
The warnings about /var/www/munin (html and graphs), /etc/munin/ (your
configuration files), /etc/munin/plugins/ (links to the plugins)
and /var/lib/munin/ (all the rrds) are quite normal. There is user
generated content and dpkg won't delete the directories.
---------------
The following packages will be REMOVED:
munin* munin-node*
0 upgraded, 0 newly installed, 2 to remove and 13 not upgraded.
After this operation, 2449kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 192913 files and directories currently installed.)
Removing munin ...
Purging configuration files for munin ...
The generated web site or accumulated data won't be removed.
dpkg - warning: while removing munin, directory
`/var/www/munin' not empty so not removed.
Removing munin-node ...
Stopping Munin-Node: done.
Purging configuration files for munin-node ...
dpkg - warning: while removing munin-node, directory
`/etc/munin/plugin-conf.d' not empty so not removed.
dpkg - warning: while removing munin-node, directory
`/etc/munin/plugins' not empty so not removed.
dpkg - warning: while removing munin-node, directory
`/etc/munin' not empty so not removed.
dpkg - warning: while removing munin-node, directory
`/var/lib/munin/plugin-state' not empty so not removed.
dpkg - warning: while removing munin-node, directory
`/var/lib/munin' not empty so not removed.
dpkg - warning: while removing munin-node, directory
`/usr/share/munin/plugins' not empty so not removed.
dpkg - warning: while removing munin-node, directory
`/usr/share/munin' not empty so not removed.
Processing triggers for man-db ...
[EMAIL PROTECTED]:~$
>
> I wish I could be more helpful in this report, but perhaps it is
> sufficient to start exploring why apt-get install --reinstall
> munin-node fails to generate the error messages I find after the dpkg
> --purge munin-node. If reportbug does not supply enough information,
> I will gladly provide any more that you request. I should also let
> you know that I was previously installing and purging all 3 packages
> (munin, munin-node, and munin-plugins-extra) with the same results
> although this report was generated with 2 packages.
So the reported messages from munin-node-configure like "# Got
junk from pipapo...." are normal. Also the messages from dpkg during
purge are normal.
But i think i remove the autoconfiguration capability from the
postgres plugins because in the "real world" no database lets 'nobody'
connect ;-).
best regards,
Matthias
signature.asc
Description: PGP signature
