• This forum has a zero tolerance policy regarding spam. If you register here to publish advertising, your user account will be deleted without further questions.

Munin startet nicht

Jesaja

Member
Guten Tag zusammen,
ich hab hier ein paar Probleme mit meinem Homeserver.
HP Microserver N36L mit frisch installiertem Ubuntu 13.04 (Raring).

Mein Munin macht ganz einfach: Nichts.
Apache2 ist installiert und funktioniert, Munin-Mode scheint auch zu funktionieren.
Munin selbst startet aber nicht:
Code:
root@hh-server:/etc/samba# service munin start
munin stop/waiting
root@hh-server:/etc/samba# ps aux | grep munin
root      3246  0.0  0.3  49880  9472 ?        Ss   12:56   0:01 /usr/bin/perl -wT /usr/sbin/munin-node
root      8084  0.0  0.0  10952   900 pts/2    R+   18:12   0:00 grep --color=auto munin
Der Aufruf im Browser von http://192.168.2.3/munin/ zeigt an, dass der Unterordner static vorhanden ist, aber sonst nichts.
Munin-check sagt folgendes: ls:
Code:
Zugriff auf /var/lib/munin/cgi-tmp/* nicht möglich: Datei oder Verzeichnis nicht gefunden

Wenn ich meinen Logs glauben könnte, würde ja alles funktionieren.
Hier das syslog:
Code:
Oct 24 18:10:01 hh-server CRON[8013]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi)
Oct 24 18:10:01 hh-server CRON[8011]: pam_unix(cron:session): session closed for user root
Oct 24 18:10:01 hh-server CRON[8012]: pam_unix(cron:session): session opened for user munin by (uid=0)
Oct 24 18:10:01 hh-server CRON[8014]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Oct 24 18:10:02 hh-server CRON[8012]: pam_unix(cron:session): session closed for user munin
Oct 24 18:15:01 hh-server CRON[8091]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 24 18:15:01 hh-server CRON[8092]: pam_unix(cron:session): session opened for user munin by (uid=0)
Oct 24 18:15:01 hh-server CRON[8093]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Oct 24 18:15:01 hh-server CRON[8096]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi)
Oct 24 18:15:01 hh-server CRON[8091]: pam_unix(cron:session): session closed for user root
Oct 24 18:15:02 hh-server CRON[8092]: pam_unix(cron:session): session closed for user munin
Oct 24 18:17:01 hh-server CRON[8124]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 24 18:17:01 hh-server CRON[8125]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 24 18:17:01 hh-server CRON[8124]: pam_unix(cron:session): session closed for user root
Oct 24 18:20:01 hh-server CRON[8492]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 24 18:20:01 hh-server CRON[8493]: pam_unix(cron:session): session opened for user munin by (uid=0)
Oct 24 18:20:01 hh-server CRON[8494]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Oct 24 18:20:01 hh-server CRON[8497]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi)
Oct 24 18:20:01 hh-server CRON[8492]: pam_unix(cron:session): session closed for user root
Oct 24 18:20:01 hh-server CRON[8493]: pam_unix(cron:session): session closed for user munin
 
Welche Munin-Pakete hast du installiert?
Was steht in den munin-Logs in /var/log/munin zu dem Problem?
 
Last edited by a moderator:
Muninversion ist 2.0.9-1ubuntu1
Zu den Logs:
Code:
root@hh-server:/var/log/munin# ls
munin-cgi-graph.log  munin-cgi-html.log  munin-html.log  munin-limits.log  munin-node-configure.log  munin-node.log  munin-update.log
Munin-node sieht normal aus
Code:
root@hh-server:/var/log/munin# tail -20 munin-node.log
2013/10/24-12:55:28 Server closing!
Process Backgrounded
2013/10/24-12:56:09 Munin::Node::Server (type Net::Server::Fork) starting! pid(3246)
Resolved [*]:4949 to [::]:4949, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4949 on host :: with IPv6
2013/10/24-13:00:01 CONNECT TCP Peer: "[::ffff:127.0.0.1]:49275" Local: "[::ffff:127.0.0.1]:4949"
Use of uninitialized value in pattern match (m//) at /usr/share/perl5/Net/Server.pm line 600.
2013/10/24-13:05:01 CONNECT TCP Peer: "[::ffff:127.0.0.1]:49277" Local: "[::ffff:127.0.0.1]:4949"
Use of uninitialized value in pattern match (m//) at /usr/share/perl5/Net/Server.pm line 600.
2013/10/24-13:10:01 CONNECT TCP Peer: "[::ffff:127.0.0.1]:49279" Local: "[::ffff:127.0.0.1]:4949"
Use of uninitialized value in pattern match (m//) at /usr/share/perl5/Net/Server.pm line 600.
2013/10/24-13:15:01 CONNECT TCP Peer: "[::ffff:127.0.0.1]:49281" Local: "[::ffff:127.0.0.1]:4949"
Use of uninitialized value in pattern match (m//) at /usr/share/perl5/Net/Server.pm line 600.
2013/10/24-23:07:43 Server closing!
Process Backgrounded
2013/10/25-12:03:04 Munin::Node::Server (type Net::Server::Fork) starting! pid(1004)
Resolved [*]:4949 to [::]:4949, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4949 on host :: with IPv6
Munin-html kann ich nicht wirklich deuten:
Code:
root@hh-server:/var/log/munin# tail -20 munin-html.log
2013/10/24 21:35:02 [PERL WARNING] Use of uninitialized value in list assignment at /usr/share/perl5/Munin/Master/Utils.pm line 134.
2013/10/24 21:40:02 [PERL WARNING] Use of uninitialized value in list assignment at /usr/share/perl5/Munin/Master/Utils.pm line 134.
Die beiden mit cgi sind leer, limits sieht normal aus
Code:
root@hh-server:/var/log/munin# tail -20 munin-limits.log
2013/10/24 22:25:02 [INFO] Starting munin-limits, getting lock /var/run/munin/munin-limits.lock
2013/10/24 22:25:02 [INFO] munin-limits finished (0.00 sec)
update ebenfall:
Code:
root@hh-server:/var/log/munin# tail -20 munin-update.log
2013/10/24 22:30:02 [INFO]: Starting munin-update
2013/10/24 22:30:02 [INFO]: Munin-update finished (0.02 sec)

Vielleicht verdächtig ist munin-node-configure, allerdings läuft der node ja
Code:
root@hh-server:/var/log/munin# tail -20 munin-node-configure.log
#       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)
# proc:
#       In family 'auto' but doesn't have 'autoconf' capability
# tomcat_:
#       Non-zero exit during autoconf (127)
# varnish_:
#       Non-zero exit during autoconf (2)
Okt 24 12:56:09 - Starting munin-node-configure --shell --newer 2.0.9
The following errors were reported by munin-node-configure --shell --newer 2.0.9
# FATAL: version '2.0.9' was not found in the plugin history file
 
Wieso versuchst du denn mit service munin start Munin zu starten?
Ist das ein Ubuntu-Spezial-Startskript?

Normalerweise rennt Munin als cron-job.
schau mal:
cat /etc/cron.d/munin
 
Wieso versuchst du denn mit service munin start Munin zu starten?
Ist das ein Ubuntu-Spezial-Startskript?
Ja. Und zwar das vermutlich sinnvollste, das je existierte. :p
Code:
root@ogmios:~# cat /etc/init.d/munin
#! /bin/sh

### BEGIN INIT INFO
# Provides:          munin
# Required-Start:    $network $named $local_fs $remote_fs
# Required-Stop:     $network $named $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Create /var/run/munin on boot
# Description:       Create /var/run/munin on boot. Munin itself runs as CGI and has no extra startscript...
### END INIT INFO

case "$1" in
  start|restart|force-reload)
	# Create various dirs
	mkdir -p /var/run/munin && chown munin /var/run/munin
	exit $?
	;;
  stop)
	# Nothing to do
	exit $?
	;;
  *)
	echo "Usage: /etc/init.d/munin" \
			"{start|stop}"
	exit 2
	;;
esac

Normalerweise rennt Munin als cron-job.
Tut es bei Ubuntu aucht, und das sollte bei Jesaja auch funktionieren. Sonst würde er ja nicht loggen.
 
Oh, peinlich :eek: ich glaube, in das init-script hatte ich sogar mein reingeguckt ;)
Ubuntu startet alle Dienste über upstart, was init.d abgelöst hat.
Der Crontab ist aber eingetragen, daran liegts nicht.

Ja, htmldir /var/cache/munin/www ist in der munin.conf angegeben, ansonsten nur n paar andere Pfade und der includedir für munin-conf.d, welches aber leer ist. (Liegt da vielleicht der Fehler?)
In dem www-Verzeichnis ist aber nur der Unterordner static, welchen ich über den Apache auch erreichen kann.

Ein Aufruf von su munin -c "/usr/bin/munin-cron" bringt auch keine Fehlermeldung.

Es scheint also alles zu funktionieren, bis auf das Anzeigen der Ergebnisse.
 
Back
Top