Expat-IT Tech Bits

Home

Contact

Links

Search this site:

Categories:

/ (287)
  Admin/ (122)
    Apache/ (10)
      HTTPS-SSL/ (4)
      PHP/ (3)
      performance/ (2)
    Cherokee/ (1)
    LAN/ (4)
    LVM/ (6)
    Monitoring/ (2)
      munin/ (2)
    SSH/ (6)
    SSL/ (1)
    Samba/ (1)
    VPN-options/ (6)
      OpenVPN/ (1)
      SSH-Proxy/ (3)
      Tinc/ (1)
      sshuttle/ (1)
    backups/ (17)
      SpiderOak/ (1)
      backuppc/ (5)
      dirvish/ (1)
      misc/ (6)
      rdiff-backup/ (1)
      rsync/ (1)
      unison/ (2)
    commandLine/ (24)
      files/ (8)
      misc/ (10)
      network/ (6)
    crontab/ (1)
    databases/ (15)
      MSSQL/ (2)
      MySQL/ (8)
      Oracle/ (3)
      PostgreSQL/ (1)
    dynamicDNS/ (2)
    email/ (11)
      Dovecot/ (1)
      deliverability/ (1)
      misc/ (1)
      postfix/ (7)
      puppet/ (1)
    iptables/ (3)
    tripwire/ (1)
    virtualization/ (9)
      VMware/ (1)
      virtualBox/ (8)
  Coding/ (14)
    bash/ (1)
    gdb/ (1)
    git/ (3)
    php/ (5)
    python/ (4)
      Django/ (2)
  Education/ (1)
  Hosting/ (27)
    Amazon/ (18)
      EBS/ (3)
      EC2/ (10)
      S3/ (1)
      commandline/ (4)
    Godaddy/ (2)
    NearlyFreeSpeech/ (3)
    Rackspace/ (1)
    vpslink/ (3)
  Linux/ (30)
    Android/ (1)
    Awesome/ (3)
    CPUfreq/ (1)
    China/ (2)
    Debian/ (8)
      APT/ (3)
      WPA/ (1)
    audio/ (1)
    encryption/ (3)
    fonts/ (1)
    misc/ (6)
    remoteDesktop/ (1)
    router-bridge/ (3)
  SW/ (45)
    Micro$soft/ (1)
    browser/ (2)
      Chrome/ (1)
      Firefox/ (1)
    business/ (28)
      Drupal/ (9)
      KnowledgeTree/ (6)
      Redmine/ (2)
      SugarCRM/ (7)
      WebERP/ (2)
      WordPress/ (1)
      eGroupware/ (1)
    chat/ (1)
    email/ (1)
    fileSharing/ (2)
      btsync/ (1)
      mldonkey/ (1)
    graphics/ (2)
    research/ (2)
    website/ (6)
      blog/ (6)
        blosxom/ (3)
        rss2email/ (1)
        webgen/ (1)
  Security/ (15)
    IMchat/ (2)
    circumvention/ (2)
    cryptoCurrency/ (1)
    e-mail/ (4)
    greatFirewall/ (1)
    hacking/ (1)
    password/ (1)
    privacy/ (2)
    skype/ (1)
  Services/ (1)
    fileSharing/ (1)
  TechWriting/ (1)
  xHW/ (14)
    Lenovo/ (1)
    Motorola_A1200/ (2)
    Thinkpad_600e/ (1)
    Thinkpad_a21m/ (3)
    Thinkpad_i1300/ (1)
    Thinkpad_x24/ (1)
    USB_audio/ (1)
    scanner/ (1)
    wirelessCards/ (2)
  xLife/ (17)
    China/ (9)
      Beijing/ (5)
        OpenSource/ (3)
    Expatriation/ (1)
    Vietnam/ (7)

Archives:

  • 2016/07
  • 2016/05
  • 2016/02
  • 2016/01
  • 2015/12
  • 2015/11
  • 2015/06
  • 2015/01
  • 2014/12
  • 2014/11
  • 2014/10
  • 2014/09
  • 2014/07
  • 2014/04
  • 2014/02
  • 2014/01
  • 2013/12
  • 2013/10
  • 2013/08
  • 2013/07
  • 2013/06
  • 2013/05
  • 2013/04
  • 2013/02
  • 2013/01
  • 2012/12
  • 2012/10
  • 2012/09
  • 2012/08
  • 2012/07
  • 2012/06
  • 2012/05
  • 2012/04
  • 2012/03
  • 2012/01
  • 2011/12
  • 2011/11
  • 2011/10
  • 2011/09
  • 2011/08
  • 2011/07
  • 2011/06
  • 2011/05
  • 2011/04
  • 2011/02
  • 2010/12
  • 2010/11
  • 2010/10
  • 2010/09
  • 2010/08
  • 2010/07
  • 2010/06
  • 2010/05
  • 2010/04
  • 2010/03
  • 2010/02
  • 2010/01
  • 2009/12
  • 2009/11
  • 2009/10
  • 2009/09
  • 2009/08
  • 2009/07
  • 2009/06
  • 2009/05
  • 2009/04
  • 2009/03
  • 2009/02
  • 2009/01
  • 2008/12
  • 2008/11
  • 2008/10
  • 2008/09
  • Subscribe XML RSS Feed

    Creative Commons License
    This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
    PyBlosxom

    This site has no ads. To help with hosting, crypto donations are accepted:
    Bitcoin: 1JErV8ga9UY7wE8Bbf1KYsA5bkdh8n1Bxc
    Zcash: zcLYqtXYFEWHFtEfM6wg5eCV8frxWtZYkT8WyxvevzNC6SBgmqPS3tkg6nBarmzRzWYAurgs4ThkpkD5QgiSwxqoB7xrCxs

    Fri, 30 Dec 2011


    /Admin/Monitoring/munin: Turn on the Apache Munin Plugins

    You need to enable extended status on Apache. Assuming the status module is enabled, create another file /etc/apache2/conf.d/extendedStatus containing the following:

    ExtendedStatus On <Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from 127.0.0.1 localhost </Location>

    (Note that /etc/apache2/mods-enabled/status.conf contains some of the above, but may not be enough.)

    Restart Apache, and now on the server itself, if you use a terminal-based web browser like w3m, for instance, this

    w3m localhost/server-status

    should show you Apache's status page. And now these plugins should work:

    apache_accesses -> /usr/share/munin/plugins/apache_accesses
    apache_processes -> /usr/share/munin/plugins/apache_processes
    apache_volume -> /usr/share/munin/plugins/apache_volume

    And finally, if due to some insoluble weirdness in your Apache configuration you cannot get it working, I have found (thanks to [1]) that putting the status stuff on another port can work, ie. /etc/apache2/mods-enabled/status.conf:

    <IfModule mod_status.c> # # Allow server status reports generated by mod_status, # with the URL of http://servername/server-status # Uncomment and change the ".example.com" to allow # access from other hosts. # Listen 8001 ExtendedStatus On <VirtualHost *:8001> <Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from localhost ip6-localhost # Allow from .example.com </Location> </VirtualHost> </IfModule>

    Then in the tree /usr/share/munin/plugins/apache_* files, replace

    my @PORTS = exists $ENV{'ports'} ? split(' ', $ENV{'ports'}) : (80);

    with

    my @PORTS = (8001);

    And hopefully you are good to go.

    [1] http://serverfault.com/questions/200320/apache-server-status-403-at-non-standard-port

    posted at: 04:04 | path: /Admin/Monitoring/munin | permanent link to this entry

    Sun, 28 Nov 2010


    /Admin/Monitoring/munin: Server Monitoring for Dummies

    Munin[1] is almost trivial to install and configure. You need two servers, one to be monitored (client) and one to do the monitoring (master). On a Debian/Ubuntu system, install Munin:

    apt-get install munin-node (on the client)
    apt-get install munin munin-node (on the master)

    I recommend installing munin-node on the master too, not only to monitor, but to get monitoring working on localhost before playing with ports and firewalls. On my Debian master, localhost monitoring worked out of the box. The only complication: documentation says to point your browser at http://master/munin/ to see the output graphs. On Debian, Apache barfs if your web browser is not on the master machine. You need to edit /etc/apache2/conf.d/munin and replace the "Allow from 127.0.0.1" with an "Allow from all".

    On the client machine, open port 4949. Edit /etc/munin/munin-node.conf so that the "allow" line specifies the IP address of your master machine. Restart the munin-node daemon so your change takes effect. And now monitoring should be working for your remote machine (the client / node).

    Note that on the master machine, the Munin master is not a daemon but a cron entry. On my Debian machine it fires every five minutes by default, so you have to wait for up to five minutes to see changes take effect in the displayed graphs.

    One other thing you probably want to do is to add to or reduce the number of things you are collecting data for and monitoring. This is done very simply in the /etc/munin/plugins/ directory of the client node. Add links for plugins you want to add to monitoring (and do not forget to restart the munin-node daemon). Delete links for data items you do not want to monitor.

    One possibly useful utility is:

    munin-node-configure --suggest

    which will list all the installed plugins, tell you whether they are turned on, and make a best guess as to whether they would be useful if you were to turn them on.

    [1] http://munin-monitoring.org/wiki/Documentation

    posted at: 08:50 | path: /Admin/Monitoring/munin | permanent link to this entry