News:

We really need your input in this questionnaire

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - CTXM

#1

After upgrading massively (via agent packages) clients to 0.2.31 (majorly 0.2.19 or 0.2.26 were previous. some versions skipped)
ServiceCheck.ssh began to return status code 3 (bad server response) right after upgrade.

On most of them additional parameters set as 127.0.0.1,22

Because of that I had manually disabled some of those check or reconfigured to ServiceCheck.Telnet other ones.

Same happens with current 1.0.0rc2 - have been checked on 2 linux clients

Do I missed something in configuration?
#2
extX partitions reserves some % of blocks (which can be freed most time, but no one does that :) ).

I have noticed, that free space reported by NetXMS agent differs from what is seen using "df".
I see only one explanation - NetXMS check does not pay an attention to reserved block count.

Detailed:


NetXMS agent ver: 0.2.27
Space check via DiskFreePerc

[root@XXX ~]# df -kh
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2              12G  8.7G  2.3G  80% /
...
[root@XXX ~]# tune2fs -l /dev/sda2
...
Block count:                  3072431
Reserved block count:     153621
...

* df shows 20% free space.
* NetXMS reports 24% for this mountpoint (I have looked a bit later +/- 1%)
* 4,99% approx reserved


Repeated once again:

[root@XXX ~]# df -kh
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2              12G  8.3G  2.8G  76% /
...

[root@XXX ~]# df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda2             12096756   8642080   2840192  76% /
...


* df shows 76% used space.
* NetXMS shows 28% free space
* 4,99% approx reserved

Difference: 4%
#3
Hi there!

As I understand, this parameter extends execution timeout for queries done locally on monitored server by netxms agent
That`s right?

I have set it to: ExecTimeout=200000
But still have "Cannot get parameter: communication failure" for an ExternalParameter which 100% is working, because:
1. we use it on a bunch of servers
2. it is shell script which runs as expected from CMD

I have tried to set it as ExternalParameterShellExec, too. Without any luck


CMD`s output for script:
***@***:~# time /***/report_***_idleness.sh 20 Casino    
OK

real    0m2.513s
user    0m0.000s
sys     0m0.000s

Output shown is definently stdout and "OK" text is expected!



Is ExecTimeout really working parameter?
May be, i need to set some other parameter?