Dir size check "Could not determine size of directory" 🔗 link

Trying to do a directory size alert but I am getting a yellow alert:

! /mm/foo/request/chkpt
Could not determine size of directory /mm/foo/request/chkpt

The directory exists and xymon can read it.    It does take a very
long time, up to two minutes. Might there be a timeout and if so might
I be able to change it?

(but that's why we need to alert, because this dir is growing too large...)

-bash-3.2$ whoami
xymon
-bash-3.2$ time du -s /mm/foo/request/chkpt
2627560 /mm/foo/request/chkpt

real    1m29.059s
user    0m0.115s
sys     0m2.259s

client-local config:
[foo.example.com]
log:/var/log/messages:102400
ignore MARK
ignore be2net
dir:/mm/foo/request/chkpt

analysis.cfg:
HOST=foo.example.com
        LOAD 12.0 99.0
        MEMPHYS 100 101
        MEMACT 70 80
        MEMSWAP 60 95
        DIR /mm/foo/request/chkpt yellow size<25622560
        PROC crond 1 -1 yellow
        PROC nscd 1 -1 yellow
        UP 30m 9999d

Looking at client data I see:

[dir:/mm/foo/request/chkpt ]
2627096	/mm/foo/request/chkpt

Any thoughts?
server and client are both 64-bit  RHEL5 running xymon 4.3.10
(hope to update soon!)

Unless I'm misreading this, it's working.

DIR /mm/foo/request/chkpt yellow size<25622560

I believe that says to turn yellow if less than ~25 MB.

=G=

From: Xymon <xymon-bounces at xymon.com> on behalf of Betsy Schwartz <user-c61747246f66@xymon.invalid>
Sent: Tuesday, February 11, 2014 9:37 PM
To: xymon at xymon.com
Subject: [Xymon] Dir size check "Could not determine size of directory"

Trying to do a directory size alert but I am getting a yellow alert:

! /mm/foo/request/chkpt
Could not determine size of directory /mm/foo/request/chkpt


The directory exists and xymon can read it.    It does take a very long time, up to two minutes. Might there be a timeout and if so might I be able to change it?

(but that's why we need to alert, because this dir is growing too large...)


-bash-3.2$ whoami
xymon
-bash-3.2$ time du -s /mm/foo/request/chkpt
2627560 /mm/foo/request/chkpt

real    1m29.059s
user    0m0.115s
sys     0m2.259s


client-local config:

[foo.example.com<http://foo.example.com>;]
log:/var/log/messages:102400
ignore MARK
ignore be2net
dir:/mm/foo/request/chkpt

analysis.cfg:
HOST=foo.example.com<http://foo.example.com>;

        LOAD 12.0 99.0
        MEMPHYS 100 101
        MEMACT 70 80
        MEMSWAP 60 95
        DIR /mm/foo/request/chkpt yellow size<25622560
        PROC crond 1 -1 yellow
        PROC nscd 1 -1 yellow
        UP 30m 9999d

Looking at client data I see:

[dir:/mm/foo/request/chkpt ]
2627096 /mm/foo/request/chkpt

Any thoughts?
server and client are both 64-bit  RHEL5 running xymon 4.3.10
(hope to update soon!)

On 12-02-2014 03:37, Betsy Schwartz wrote:

! /mm/foo/request/chkpt
Could not determine size of directory /mm/foo/request/chkpt

client-local config:
[foo.example.com]
dir:/mm/foo/request/chkpt

analysis.cfg:
HOST=foo.example.com <http://foo.example.com>;
         DIR /mm/foo/request/chkpt yellow size<25622560

Looking at client data I see:

[dir:/mm/foo/request/chkpt ]
2627096	/mm/foo/request/chkpt

Any thoughts?

The only thing that sticks out to my eye is that there seems to be some whitespace after the directory name in the client data:

[dir:/mm/foo/request/chkpt ]

I think this might be the cause - when the client runs the 'du' command, it is passed to a shell which will ignore the trailing whitespace; but the analysis module back on the Xymon server treats it as a valid part of the directory name and so it cannot match the name from the client data with the name from the analysis.cfg file.

Could you check the client-local.cfg file and see if there is a trailing space in the "dir:/mm/foo/request/chkpt" line ?


Regards,
Henrik

That was it, thank you! A space at the end of the file name.

On Wed, Feb 12, 2014 at 12:55 AM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote: