Munin integration !?

  • 7.X

Der neue Support Bereich ist absofort unter community.teklab.de zu finden.

Leider bietet das WBB keinen vernünftigen Spamschutz, daher sind Neuanmeldungen gesperrt. Wir werden die nächsten Tage das Handbuch/WIKI im neuen Support Bereich übernehmen. Dieses Forum bleibt jedoch mit seinen bisherigen Beiträgen, für alle die die Suchfunktion nutzen wollen, vorerst erhalten. User die über den Kundenbereich die Zugangsdaten erhalten und Bestandsuser können das Forum weiter nutzen. Jedoch würden wir alle gerne im neuen Support Bereich begrüßen wollen.

Anfang Juni wird im Kundenbereich automatisch ein Zugang zum neuen Support Bereich angelegt, ähnlich wie es derzeit für WBB geschieht. Somit entfällt dann die Neuanmeldung. ;)

  • Munin integration !?

    Hallo zusammen :)

    Ich habe seid ein paar Tagen nun auch Munin drauf und versuche zumindest erst mal vom RootServer selber die Statistiken anzeigen zu lassen. Ich habe wie folgt alles Eingestellt:
    Im Adminbereich unter Einstellungen beim Statistikserverpfad steht: domain.de/munin
    Im Rootserver bei Grafiken für Statistiken steht:
    Spoiler anzeigen
    MuninMaster/MuninMaster/acpi-{%statusview%}.png
    MuninMaster/MuninMaster/apache_accesses-{%statusview%}.png
    MuninMaster/MuninMaster/apache_processes-{%statusview%}.png
    MuninMaster/MuninMaster/apache_volume-{%statusview%}.png
    MuninMaster/MuninMaster/cpu-{%statusview%}.png
    MuninMaster/MuninMaster/df-{%statusview%}.png
    MuninMaster/MuninMaster/df_inode-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_iops-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_iops/sda-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_iops/sdb-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_latency-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_latency/sda-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_latency/sdb-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_throughput-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_throughput/sda-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_throughput/sdb-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_utilization-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_utilization/sda-{%statusview%}.png
    MuninMaster/MuninMaster/diskstats_utilization/sdb-{%statusview%}.png
    MuninMaster/MuninMaster/entropy-{%statusview%}.png
    MuninMaster/MuninMaster/forks-{%statusview%}.png
    MuninMaster/MuninMaster/fw_packets-{%statusview%}.png
    MuninMaster/MuninMaster/if_err_eth0-{%statusview%}.png
    MuninMaster/MuninMaster/if_eth0-{%statusview%}.png
    MuninMaster/MuninMaster/interrupts-{%statusview%}.png
    MuninMaster/MuninMaster/iostat-{%statusview%}.png
    MuninMaster/MuninMaster/iostat_ios-{%statusview%}.png
    MuninMaster/MuninMaster/irqstats-{%statusview%}.png
    MuninMaster/MuninMaster/load-{%statusview%}.png
    MuninMaster/MuninMaster/memory-{%statusview%}.png
    MuninMaster/MuninMaster/open_files-{%statusview%}.png
    MuninMaster/MuninMaster/open_inodes-{%statusview%}.png
    MuninMaster/MuninMaster/postfix_mailqueue-{%statusview%}.png
    MuninMaster/MuninMaster/postfix_mailvolume-{%statusview%}.png
    MuninMaster/MuninMaster/processes-{%statusview%}.png
    MuninMaster/MuninMaster/proc_pri-{%statusview%}.png
    MuninMaster/MuninMaster/swap-{%statusview%}.png
    MuninMaster/MuninMaster/threads-{%statusview%}.png
    MuninMaster/MuninMaster/uptime-{%statusview%}.png
    MuninMaster/MuninMaster/users-{%statusview%}.png
    MuninMaster/MuninMaster/vmstat-{%statusview%}.png


    im var/www/munin/MuninMaster/MuninMaster/ Verzeichnis sind auch die besagten Grafiken vorhanden aber wenn ich mir dann die Grafiken anschauen möchte
    wird mir nichts angezeigt und die fehlenden Bilder sind wie folgt verlinkt: domain.de/tekbase/domain.de/mu…/apache_processes-day.png .

    Ich gehe mal ganz Stark davon aus das was an der munin.conf nicht richtig ist welche folgenden Inhalt hat:
    Spoiler anzeigen
    # Example configuration file for Munin, generated by 'make build'

    # The next three variables specifies where the location of the RRD
    # databases, the HTML output, logs and the lock/pid files. They all
    # must be writable by the user running munin-cron. They are all
    # defaulted to the values you see here.
    #
    dbdir /var/lib/munin
    htmldir /var/www/munin
    logdir /var/log/munin
    rundir /var/run/munin

    # Where to look for the HTML templates
    #
    tmpldir /etc/munin/templates

    # Where to look for the static www files
    #
    #staticdir /etc/munin/static

    # temporary cgi files are here. note that it has to be writable by
    # the cgi user (usually nobody or httpd).
    #
    # cgitmpdir /var/lib/munin/cgi-tmp

    # (Exactly one) directory to include all files from.
    includedir /etc/munin/munin-conf.d

    # You can choose the time reference for "DERIVE" like graphs, and show
    # "per minute", "per hour" values instead of the default "per second"
    #
    #graph_period second

    # Graphics files are generated either via cron or by a CGI process.
    # See munin-monitoring.org/wiki/CgiHowto2 for more
    # documentation.
    # Since 2.0, munin-graph has been rewritten to use the cgi code.
    # It is single threaded *by design* now.
    #
    #graph_strategy cron

    # munin-cgi-graph is invoked by the web server up to very many times at the
    # same time. This is not optimal since it results in high CPU and memory
    # consumption to the degree that the system can thrash. Again the default is
    # 6. Most likely the optimal number for max_cgi_graph_jobs is the same as
    # max_graph_jobs.
    #
    #munin_cgi_graph_jobs 6

    # If the automatic CGI url is wrong for your system override it here:
    #
    #cgiurl_graph /munin-cgi/munin-cgi-graph

    # max_size_x and max_size_y are the max size of images in pixel.
    # Default is 4000. Do not make it too large otherwise RRD might use all
    # RAM to generate the images.
    #
    #max_size_x 4000
    #max_size_y 4000

    # HTML files are normally generated by munin-html, no matter if the
    # files are used or not. You can change this to on-demand generation
    # by following the instructions in munin-monitoring.org/wiki/CgiHowto2
    #
    # Notes:
    # - moving to CGI for HTML means you cannot have graph generated by cron.
    # - cgi html has some bugs, mostly you still have to launch munin-html by hand
    #
    #html_strategy cron

    # munin-update runs in parallel.
    #
    # The default max number of processes is 16, and is probably ok for you.
    #
    # If set too high, it might hit some process/ram/filedesc limits.
    # If set too low, munin-update might take more than 5 min.
    #
    # If you want munin-update to not be parallel set it to 0.
    #
    #max_processes 16

    # RRD updates are per default, performed directly on the rrd files.
    # To reduce IO and enable the use of the rrdcached, uncomment it and set it to
    # the location of the socket that rrdcached uses.
    #
    #rrdcached_socket /var/run/rrdcached.sock

    # Drop somejuser@fnord.comm and anotheruser@blibb.comm an email everytime
    # something changes (OK -> WARNING, CRITICAL -> OK, etc)
    #contact.someuser.command mail -s "Munin notification" somejuser@fnord.comm
    #contact.anotheruser.command mail -s "Munin notification" anotheruser@blibb.comm
    #
    # For those with Nagios, the following might come in handy. In addition,
    # the services must be defined in the Nagios server as well.
    #contact.nagios.command /usr/bin/send_nsca nagios.host.comm -c /etc/nsca.conf

    # a simple host tree
    [MuninMaster]
    address 127.0.0.1
    use_node_name yes

    #
    # A more complex example of a host tree
    #
    ## First our "normal" host.
    # [fii.foo.com]
    # address foo
    #
    ## Then our other host...
    # [fay.foo.com]
    # address fay
    #
    ## IPv6 host. note that the ip adress has to be in brackets
    # [ip6.foo.com]
    # address [2001::1234:1]
    #
    ## Then we want totals...
    # [foo.com;Totals] #Force it into the "foo.com"-domain...
    # update no # Turn off data-fetching for this "host".
    #
    # # The graph "load1". We want to see the loads of both machines...
    # # "fii=fii.foo.com:load.load" means "label=machine:graph.field"
    # load1.graph_title Loads side by side
    # load1.graph_order fii=fii.foo.com:load.load fay=fay.foo.com:load.load
    #
    # # The graph "load2". Now we want them stacked on top of each other.
    # load2.graph_title Loads on top of each other
    # load2.dummy_field.stack fii=fii.foo.com:load.load fay=fay.foo.com:load.load
    # load2.dummy_field.draw AREA # We want area instead the default LINE2.
    # load2.dummy_field.label dummy # This is needed. Silly, really.
    #
    # # The graph "load3". Now we want them summarised into one field
    # load3.graph_title Loads summarised
    # load3.combined_loads.sum fii.foo.com:load.load fay.foo.com:load.load
    # load3.combined_loads.label Combined loads # Must be set, as this is
    # # not a dummy field!
    #
    ## ...and on a side note, I want them listen in another order (default is
    ## alphabetically)
    #
    # # Since [foo.com] would be interpreted as a host in the domain "com", we
    # # specify that this is a domain by adding a semicolon.
    # [foo.com;]
    # node_order Totals fii.foo.com fay.foo.com
    #


    kann mir da einer helfen?

    Mit freundlichen Grüßen
    Zonk87
  • Wenn die Grafiken im Verzeichnis der Domain liegen, ist doch eigentlich alles richtig. Hier einfach schaun, dass die Dateirechte stimmen und diese sowie die Verzeichnisse für alle lesbar sind.

    Bei Statistikserver lass mal domain.de/munin raus oder nur durch / ersetzen. Dann wäre es
    domain.de/tekbase/munin/muninMaster/....
    Bitte die Forumsuche und das Handbuch verwenden. Wenn die Suche erfolglos war, bitte ein Thema erstellen und das Problem ausführlich beschreiben. Dieser Ablauf spart Zeit und unnötige Fragen zu immer gleichen Problemen. Sie können uns aber auch eine Supportanfrage zukommmen lassen.

    Gefällt Ihnen TekLab?

    Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von CFrankenstein ()