Welcome to Pandora FMS Community!

Find answers, ask questions, and connect with our community around the world.

Welcome to Pandora FMS Community Forums Community support Free Disk Space problem in FMS 1.3

  • Free Disk Space problem in FMS 1.3

    Posted by sillyPandora on February 26, 2008 at 21:30

    I have a problem with my free disk space displaced in units of K where it should be in GB. Any idea how to fix it?

    I am using FMS 1.3 and a mixed of 1.2 and 1.3 agents.
    For example, on my client I will have 8GB of free space, but it will display 8.00 K in my Pandora web console.

    Thanks!

    Sancho replied 17 years ago 2 Members · 1 Reply
  • 1 Reply
  • Sancho

    Administrator
    February 27, 2008 at 13:22
    2321 Karma points
    Community awards: bulb Bright ideas
    Community rank: tentacle_master_icon Tentacle Master
    Like it
    Up
    0
    Down
    Drop it
    ::

    I have a problem with my free disk space displaced in units of K where it should be in GB. Any idea how to fix it?

    I am using FMS 1.3 and a mixed of 1.2 and 1.3 agents.
    For example, on my client I will have 8GB of free space, but it will display 8.00 K in my Pandora web console.

    Thanks!

    At this moment there is no “centralized” solution. Best option is to adjust linux agents to return values in the same scale that windows.

    For next version (we’re currently working on 2.0) we’re working on a way to post-process all numerical values, and be able to multiply for a given value (for example 1024) to normalize data.

    If you want a module to get free disk in GB on linux:

    df -k | grep “/dev/sda3” | awk ‘{print $4/1048576 ‘}

    If you want to get on bytes:

    df -k | grep “/dev/sda3” | awk ‘{print $4 ‘}

    For example, my df -k returns:

    /dev/sda1 80120 7088 73032 9% /media/sda1
    /dev/sda2 10485756 3426012 7059744 33% /media/sda2
    /dev/sda3 77153268 12457120 64696148 17% /media/sda3
    /dev/sda7 1683484 4 1683480 1% /media/sda7

    You need to get the the fourth column, so awk ‘{ print $4 }’ gets the value for the fourth column.

    I hope this helps…