munin-node-configure --shell fails on lucid

Bug #604110 reported by Aaron Brashears
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
munin (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: munin-node

Attempting to run munin-node-configre with --shell results in no output and non-zero return code whereas without the --shell option, the command returns reasonable yes/no suggestions.

Command and output:

$ sudo munin-node-configure --shell
# The following plugins caused errors:
# ip_:
# Nothing printed to stdout
# No valid suggestions
# postgres_bgwriter:
# Non-zero exit during autoconf (255)
# postgres_cache_:
# Non-zero exit during autoconf (255)
# postgres_checkpoints:
# Non-zero exit during autoconf (255)
# postgres_connections_:
# Non-zero exit during autoconf (255)
# postgres_connections_db:
# Non-zero exit during autoconf (255)
# postgres_locks_:
# Non-zero exit during autoconf (255)
# postgres_querylength_:
# Non-zero exit during autoconf (255)
# postgres_scans_:
# Non-zero exit during autoconf (255)
# postgres_size_:
# Non-zero exit during autoconf (255)
# postgres_transactions_:
# Non-zero exit during autoconf (255)
# postgres_tuples_:
# Non-zero exit during autoconf (255)
# postgres_users:
# Non-zero exit during autoconf (255)
# postgres_xlog:
# Non-zero exit during autoconf (255)
# snort_alerts:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_bytes_pkt:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_drop_rate:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_pattern_match:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_pkts:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_traffic:
# Non-zero exit during autoconf (1)
# Junk printed to stderr

Munin version information:

$ dpkg -l | grep munin
ii munin 1.4.4-1ubuntu1 network-wide graphing framework (grapher/gat
ii munin-common 1.4.4-1ubuntu1 network-wide graphing framework (common)
ii munin-node 1.4.4-1ubuntu1 network-wide graphing framework (node)
ii munin-plugins-extra 1.4.4-1ubuntu1 network-wide graphing framework (user contri

Revision history for this message
Chuck Short (zulcss) wrote :

Do you have autoconf installed?

Changed in munin (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Aaron Brashears (aaronbrashears) wrote :

Yes I do.

$ dpkg -l | grep autoconf
ii autoconf 2.65-3ubuntu1 automatic configure script builder

Revision history for this message
Christine G. (ctrobbia) wrote :

I have the same issue here.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04 LTS"

$ dpkg -l | grep autoconf
ii autoconf 2.65-3ubuntu1 automatic configure script builder

dpkg -l | grep munin
ii munin 1.4.4-1ubuntu1 network-wide graphing framework (grapher/gat
ii munin-common 1.4.4-1ubuntu1 network-wide graphing framework (common)
ii munin-node 1.4.4-1ubuntu1 network-wide graphing framework (node)
ii munin-plugins-extra 1.4.4-1ubuntu1 network-wide graphing framework (user contri

Revision history for this message
Aaron Brashears (aaronbrashears) wrote :

I dug into this a little today by running strace on the call:

sudo strace munin-node-configure --shell &> strace.output

Examining that led to the suspicious discover that somebody was attempting to use the Text::CSV_XS library and not finding it so I installed libtext-csv-xs-perl and tried again with no real change in output. Examining the output of strace more revealed that all 109 SIGCHLD actually returned 0.

The strace did reveal what appeared to be read off of stdout from child processes and they were all of the form:

read(4, "int \"no (no ipmitool output)\"\n\nd"..., 4096) = 1107
read(4, "no (cannot read /proc/acpi/therm"..., 4096) = 55
read(4, "no (Port 80: Forbidden)\n", 4096) = 24
...

or the positive:
read(4, "yes\n", 4096) = 4

During the run after the installation of Text::CSV_XS, I did not find anything particularly suspicious in the output. Is there anything else I could provide which might shine light on why --shell does not work?

Revision history for this message
UndiFineD (k.dejong) wrote :

reproduced with munin 1.4.5

# munin-node-configure --shell
ln -s '/usr/share/munin/plugins/ip_' '/etc/munin/plugins/ip_XXX.54.35.25'
ln -s '/usr/share/munin/plugins/ip_' '/etc/munin/plugins/ip_XXX.54.40.25'
ln -s '/usr/share/munin/plugins/nfsd' '/etc/munin/plugins/nfsd'
ln -s '/usr/share/munin/plugins/postgres_cache_' '/etc/munin/plugins/postgres_cache_ALL'
ln -s '/usr/share/munin/plugins/postgres_connections_' '/etc/munin/plugins/postgres_connections_ALL'
ln -s '/usr/share/munin/plugins/postgres_locks_' '/etc/munin/plugins/postgres_locks_ALL'
ln -s '/usr/share/munin/plugins/postgres_querylength_' '/etc/munin/plugins/postgres_querylength_ALL'
ln -s '/usr/share/munin/plugins/postgres_size_' '/etc/munin/plugins/postgres_size_ALL'
ln -s '/usr/share/munin/plugins/postgres_transactions_' '/etc/munin/plugins/postgres_transactions_ALL'
ln -s '/usr/share/munin/plugins/postgres_users' '/etc/munin/plugins/postgres_users'
ln -s '/usr/share/munin/plugins/postgres_xlog' '/etc/munin/plugins/postgres_xlog'
# The following plugins caused errors:
# df:
# Junk printed to stderr
# df_inode:
# Junk printed to stderr
# postgres_scans_:
# Non-zero exit during autoconf (2)
# postgres_tuples_:
# Non-zero exit during autoconf (2)
# slony_lag_:
# Non-zero exit during autoconf (2)
# snort_alerts:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_bytes_pkt:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_drop_rate:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_pattern_match:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_pkts:
# Non-zero exit during autoconf (1)
# Junk printed to stderr
# snort_traffic:
# Non-zero exit during autoconf (1)
# Junk printed to stderr

Revision history for this message
UndiFineD (k.dejong) wrote :

my strace.output as suggested above

I use perl 5.12.1

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for munin (Ubuntu) because there has been no activity for 60 days.]

Changed in munin (Ubuntu):
status: Incomplete → Expired
Revision history for this message
mpasadas (mpasadas) wrote : Earn a Univesrity Dgeree based on your professional experience. business idea marketing small

   Pass the time of day with somebody !
   Customer

We provide a program that will allow someone with sufficient work experience to obtain a fully verifiable Dgeree: Dotcorate, Matsers or Masetrs.

Diploma from prestigious non-accredited universities based on your present knowledge & professional experience.

No books!. Obtain a Dgeree!. Ticket to Success.

Think of it, within four to six weeks, you too could be a colelge graduate. Many people share the same frustration, they are doing the work of the person that has the degree and the person that has the degree is getting all the money.

-----------------------------------------------------
Give us a call NOW!

+ 1 - 646 - 537 - 1732
Please leave us your:
1) Your Name
2) Your Country
3) Phone No. with countrycode if outside USA

We will get back to you ASAP
-----------------------------------------------------

Do Not Reply to this Email.
We do not reply to text inquiries, and our server will reject all response traffic.
We apologize for any inconvenience this may have caused you.

Revision history for this message
Denis (link011) wrote :

Hi all.

Any news on this problem ? I have exactly same issue :(

Revision history for this message
DisasteR (benj.saiz) wrote :

Hi,

any news ?

Revision history for this message
Artur Jackowski (artur-jackowski) wrote :

It's not a bug in app but in your configuration. I have a newer version (1.4.5) than yours and I get the same logs like UndiFineD but I'm almost 100% sure it's the same problem.

You need to set environment variables to give libdbd-pg-perl information how and where to connect. Maybe there is some other way but I don't know perl (Java rules).

root@arturc:/etc/munin# export PGHOST=localhost
root@arturc:/etc/munin# export PGPORT=5432
root@arturc:/etc/munin# export PGUSER=postgres
And also (!!!)
root@arturc:/etc/munin# export PGPASSWORD=mySecretPassword
Note, that having a password in ~/.pgpass change nothing. Munin (or per libraries) simply ignore it.

With these environment params you can successfuly run both
 # munin-node-configure --suggest
 # munin-node-configure --shell
and (after symbolic link creation) install munin.

Changed in munin (Ubuntu):
status: Expired → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.