You are not logged in.

#1 2010-02-03 15:55:02

jelly
Administrator
From: /dev/null
Registered: 2008-06-10
Posts: 714

[solved] Munin-Node fails too start

When starting munin-node on my server, i get the message [done] but when i get `ps aux` munin isn't there.

Process Backgrounded
2010/02/03-16:52:52 Munin::Node::Server (type Net::Server::Fork) starting! pid(4926)
Binding to TCP port 4949 on host *
Setting gid to "0 0"
Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl5/site_perl/5.10.1/Munin/Node/OS.pm line 49.

It seems for me that , munin node stops working because of the error

munin-node.conf

#
# Example config-file for munin-node
#

log_level 4
log_file /var/log/munin/munin-node.log
pid_file /var/run/munin/munin-node.pid

background 1
setsid 1

user root
group root

# Regexps for files to ignore

ignore_file ~$
#ignore_file [#~]$  # FIX doesn't work. '#' starts a comment
ignore_file DEADJOE$ 
ignore_file \.bak$
ignore_file %$
ignore_file \.dpkg-(tmp|new|old|dist)$
ignore_file \.rpm(save|new)$
ignore_file \.pod$

# Set this if the client doesn't report the correct hostname when
# telnetting to localhost, port 4949
#
#host_name myhostname

# A list of addresses that are allowed to connect.  This must be a
# regular expression, since Net::Server does not understand CIDR-style
# network notation unless the perl module Net::CIDR is installed.  You
# may repeat the allow line as many times as you'd like

allow ^127\.0\.0\.1$

# If you have installed the Net::CIDR perl module, you can use
# multiple cidr_allow and cidr_deny address/mask patterns.  A
# connecting client must match any cidr_allow, and not match any
# cidr_deny.  Example:

# cidr_allow 127.0.0.1/32
# cidr_allow 192.0.2.0/24
# cidr_deny  192.0.2.42/32

# Which address to bind to;
host *
# host 127.0.0.1

# And which port
port 4949

Last edited by jelly (2010-02-04 13:23:19)

Offline

#2 2010-02-03 17:35:42

juster
Forum Fellow
Registered: 2008-10-07
Posts: 195

Re: [solved] Munin-Node fails too start

I found this in the perldiag manpage:

Insecure directory in %s
       (F) You can't use system(), exec(), or a piped open in a setuid or
       setgid script if $ENV{PATH} contains a directory that is writable
       by the world.  Also, the PATH must not contain any relative
       directory.  See perlsec.

The "-T switch" turns on added security checks like the fatal error that is preventing munin from running insecurely.  Just to reiterate: check the permissions of the dirs in your PATH to make sure they aren't "writable by the world" (aka other... which is bad) and make sure the dirs aren't relative (meaning they don't have a leading /).

Offline

#3 2010-02-04 13:22:55

jelly
Administrator
From: /dev/null
Registered: 2008-06-10
Posts: 714

Re: [solved] Munin-Node fails too start

fixed the error with reinstalling

Offline

Board footer

Powered by FluxBB