Monitorix 3.4.0 Released – A Lightweight System and Network Monitoring Tool for Linux

If you have any questions or problems regarding this article and want help within 24 Hours? Ask Now

Ravi Saive

Simple Word a Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

Receive Your Free Complimentary eBook NOW! -

Download Free Linux eBooks

Advanced Bash-Scripting Guide
Linux Bible
A Newbie's Getting Started Guide to Linux
Ubuntu Linux Toolbox: 1000+ Commands

You may also like...

20 Responses

  1. Koshal says:

    [root@wapp Desktop]# yum install /tmp/monitorix-3.6.0-1.noarch.rpm
    Loaded plugins: refresh-packagekit, rhnplugin
    This system is not registered with RHN.
    RHN support will be disabled.
    Setting up Install Process
    Examining /tmp/monitorix-3.6.0-1.noarch.rpm: monitorix-3.6.0-1.noarch
    Marking /tmp/monitorix-3.6.0-1.noarch.rpm to be installed
    Resolving Dependencies
    –> Running transaction check
    —> Package monitorix.noarch 0:3.6.0-1 set to be updated
    –> Processing Dependency: perl(MIME::Lite) for package: monitorix-3.6.0-1.noarch
    –> Processing Dependency: perl(RRDs) for package: monitorix-3.6.0-1.noarch
    –> Processing Dependency: perl-MIME-Lite for package: monitorix-3.6.0-1.noarch
    –> Running transaction check
    —> Package monitorix.noarch 0:3.6.0-1 set to be updated
    –> Processing Dependency: perl(RRDs) for package: monitorix-3.6.0-1.noarch
    —> Package perl-MIME-Lite.noarch 0:3.027-2.el6 set to be updated
    –> Processing Dependency: perl(MIME::Types) >= 1.28 for package: perl-MIME-Lite-3.027-2.el6.noarch
    –> Running transaction check
    —> Package monitorix.noarch 0:3.6.0-1 set to be updated
    –> Processing Dependency: perl(RRDs) for package: monitorix-3.6.0-1.noarch
    —> Package perl-MIME-Types.noarch 0:1.28-2.el6 set to be updated
    –> Finished Dependency Resolution
    Error: Package: monitorix-3.6.0-1.noarch (/monitorix-3.6.0-1.noarch)
    Requires: perl(RRDs)
    You could try using –skip-broken to work around the problem
    You could try running: rpm -Va –nofiles –nodigest
    [root@wapp Desktop]#

    • Ravi Saive says:

      @Koshar,
      First install all the required packages as shown in the article and then try again..

      • Koshal says:

        Thanks for reply, Actually problem in rrdtool package. After installing correct rpm architecture , its working

        • Ravi Saive says:

          @Koshal,
          That’s good to hear, finally it worked for you..may I know on which distro you’ve tired latest version of Monitorix? Could you please share the steps with us so that we can update the article to latest version..

  2. SteveR says:

    Well, we actually used some of the mentioned tools. And we ended up using
    CloudView NMS http://www.cloudviewnms.com . We run it on Ubuntu, but it can run on any Linux. Seems like it can monitor/manage practically anything: SNMP, sysLog TL1, services, web access, servers…). They discovered our network put in maps (they use Google maps). Secure multi-user web access with configurable profiles . Alarms forwarding via many protocols (including e-mail) They claim it scalable to thousands of nodes (we have 245 so far) and unlike others they do not charge as your network grows – from my point of view very important feature :-). Remote HTML-5 based interface from anywhere including mobile devices. The only caveat: manual is not that good, but they have very enthusiastic e-mail support. They added some specific feature for us in several days

  3. Bl_nK says:

    There are better troubleshooting and configuration options for SELinux than disabling it.

  4. Mufler says:

    Just installed monitorix and found out that it is exposed to open world!!! Huge security risk here guys. I thougt it was safe and as this turtorial says that one should allow access manually because it is only opened for local host by default, is just bogus. I have tried to close down the access other than from localhost, but it is still open!

  5. Gopi says:

    Hi
    I have installed and configured monitorix . I am able to view http://localhost/monitorix/ page but can’t view graph following error iam getting

    (Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log. )

    Can please help me…..?

  6. I prefer Zenoss over Zabbix, more enterprise look and really good support.

  7. Bob Snuffy says:

    Can someone please explain why we’re still publishing how-to articles with SECURITY DISABLING steps in them?! SELinux has been around for a long time, with plenty of documentation. As an industry, taking something that’s designed to make a system more secure and announcing to the world we’re purposefully disabling it rather than taking the time to learn why it’s restricting something seems rather foolish.

  8. Stuart says:

    Can someone give me a really good reason why I would use this instead of Nagios? ( http://www.nagios.org/ )

    • Noman says:

      Can someone give me a really good reason why i would Nagios over Monitorx?

      • Stuart Page says:

        1. Nagios monitors all your services on the network rather than just the single host that it is on.

        2. Nagios has significant amounts of documentation. This book is VERY detailed:
        http://shop.oreilly.com/product/9781593270704.do
        but you can of course use the website for a lot of docs.

        3. Nagios is clever enough to work out whether just a service is down instead of a host, or whether it is likely that a switch is down, rather than the hosts themselves, which helps admins get to the real issue rather than having a lot of warnings that don’t directly tell you the real issue.

        4. The way Nagios works means that it is fairly easy to create a ‘plugin’ for it, and as a side effect means that there are already lots of ‘plugins’ available for it.

        • tom says:

          I say, if you have one or two servers, use Monitorix (easy to set up – took me two minutes), if you have a farm of servers, use Nagios.

          • John says:

            I say, if you have a farm of servers, or multiple farms of servers use Zabbix over Nagios. Scales better and is easier to make custom monitoring and triggers, etc. Not that it’s particular hard in Nagios, but it’s even it easier in Zabbix.

          • Stuart Page says:

            @ John
            Thanks! I do have a farm of servers/network to manage. I had not heard of Zabbix before and from the 5 minutes spent looking at it, it does appear ‘more polished’ than nagios. I will compare the two in more detail.

          • kevin says:

            With a farm of servers, You should probably checkout http://www.sealion.com. Recently found out about it. Setup is a cake walk, its free and it caters to all system monitoring requirements from top CPU taking processes, memory, disk usage, to network summary, everything I need. Hope you find it useful! :)

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Join Over 80000+ Linux Users
  1. 52882
  2. 2763
  3. 18,639

Enter your email to get latest Linux Howto's