NetXMS Forum

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?

AS a part of this feature, it could be nice for windows copy-paste functionality in object browser. Such way brief info about monitoring settings could be pasted from single node

And if only copy paste could work in data collection configuration... mmm!

Also, feel free to move this topic to general support tree - to keep forum clean

There are 2 situations described:

1st with server XXX, which shows how bad is to do not read manual. Actually, I have seen Disk.Free & Disk.Avail, but didn`t udnerstand from an explanation that difference is about reserved blocks, so i throw it :$ Sorry. Looks stupid

Everything okay with this server. Checks works fine.

2nd situation is with server YYY.

I have added Disk.Avail and got 5% difference with DiskFree.  
But reported data still doesn`t fit together with DF produced one.
With Disk.Avail - 1-4% misses (on different size partitions) !!!

[root@YYY netxms-0.2.31]# df -kh
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2              12G  3.1G  7.9G  29% /
...
/dev/sda5              48G   31G   15G  69% /export/stroage0
/dev/sdb1             268G   73G  182G  29% /export/storage1

While NetXMS reports free space:

/                      - 68  ::: 100 - 29 = 71 : 3% missed
/export/stroage0 - 30   ::: 100 - 69 = 31 : 1% missed
/export/storage1 - 67   ::: 100 - 29 = 71 : 4% missed

I did NetXMS agent ugrade from 0.2.19 to 0.2.31, but this didn`t changed situation.
Someone lies - either DF, either NetXMS.

Also, seems, it is specific to server environment, because on server XXX checks works as expected.
Could it be so?

Hmm.
Nope, here is somthing else

on an another machine, with almost same parameters, data differs:

NetXMS agent: 0.2.19

[root@YYY ~]# df -k
Filesystem          1K-blocks      Used Available Use% Mounted on
/dev/sda2            12096756  3191224  8291048  28% /

[root@YYY ~]# df -kh
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2              12G  3.1G  8.0G  28% /
...

[root@YYY ~]# tune2fs -l /dev/sda2
...
Block count:                  3072431
Reserved block count:    153621
...

* df shows 28% used space
* NetXMS shows 73% free disk space
* 4,99% approx reserved

Difference between df & NetXMS is 1% in this case. And 4% in previous case. WTF?

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%

Yep!!!

That worked.

little note for every others: for server`s timeout to apply NetXMS server needs to be restarted after change

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?

Uff, sorry - i was busy with some other tasks...
I have cured another one machine (gcc-c++ wasn`t installed), so there is only one left. Right the one we are talking about

zipped config.log attached (zipped because vanilla txt larger than 256kb)

---

config.zip

Sorry about last paragraph (where agent version mentioned), it could mislead
it is obvious, agent version does not makes any sense - problem is in OS environemnt, for sure

@victor said in Centralized agent upgrade feature:

Hello!

Usually you should be able to upgrade any version of agent. Most likely there are a problem with specific system. Agent installer should left logs in /tmp on target machine - could you please provide them?

Best regards,
Victor

MM.. seems so.Added to attachment.
Configure goes with OK, but make messes. Undefined references in libnetxms.so
I googled a bit and installed glibc-devel. Then I tried export LIBS=-ldl && ./configure... - both did not helped

This log is from another one machine (agent - 0.2.15 ). So, at this moment I have 2 machines with same error NetXMS console shows.

Heelp!

---

nxagentupdate.log

I am interested in those Service.Check.SSH parameter response statuses

2 means ?
3 means ?

Wich ones, even, exists?

As I understand, update procedure sends sourceball, then configures and automakes it on the host. installs it in the same directory where current netxms operates.
It would be nice to tune/control more this process, because

1. many of admin crews organizes directory structure and compiled soft differently in their environments.
2. configure, make logs could be retreived from server in the same way as nxagent.conf file does

Real example:
We store every compiled soft in form of: /opt/$software_brand-$version
Then we create softlink in form of: /opt/$software_brand-$version <- /opt/$software_brand
So, it just need to be done "ls /opt/" on a server to know main applications or software installed manually.

In case netxms-agent update proceeds remotely, form of $software_brand-$version becomes misleading.

It doesn`t scares us much, but it makes a little hole in our logic. So - it possibly can unsatisfy other teams with larger or more specific or more beurocratic IT organisations.
Even more: in case of tests there could be specially different agent versions keeped. And not only on one single server. I do so, for example.
I have even quickfixed init script to understand version of agent I want to start via second variable passed (/etc/init./netxms start 0.2.26):
...
[ -z "$2" ] || netxmsExec="/opt/netxms-$netxmsVer/bin/nxagentd -c /opt/netxms$netxmsVer/etc/nxagentd.conf -d"
[ -n "$2" ] || netxmsExec="/opt/netxms/bin/nxagentd -c /opt/netxms/etc/nxagentd.conf -d"
...

That`s why I suggest to invent more control in auto-deployment.

There is no difficulty to implement unified control for many different store conventions we can emagine.
Autodeploy destination directory need to be configurable, possibility to retrieve logs, older ver move configurable (some kind of automatic logical or manual suffix addon). Softlink of new location to old location could be created for linux systems because of init scripts.

Small addon to instruction:
InstallationServers instruction need to be set in nxagent.conf to be able to deploy package onto agent`s OS using centralised deployment

But in case when there was no InstallationServers instruction provided, I wasn`t able even to EDIT agent`s configuration file from NetXMS server. So, I did this via standart ssh session Is it normal behavior?

Only after I have added meaned parameter pointed the same as MasterServers (is MasterServers same instruction as Servers, or there is some difference?) I was able to edit agent`s configuration

I have did as written in an instruction provided at this topic, but did not succeed

1. Took this:

UNIX source package
nxagent-0.2.31.apkg
nxagent-0.2.31.npi

2. Agent, tried to upgrade:

NetXMS agent 0.2.16
Linux-i686
Linux $hostname 2.6.20-1.2952.fc6 #1 SMP Wed May 16 17:59:13 EDT 2007 i686

I have seen deployment and even installing process (I mean, green play button and word "installing" in a status column). And then an error:
"Agent`s version doesn`t match package version after upgrade"

In the same time, I was able to update another one agent with a version 0.2.26. Does it mean, there is some "too old to be upgraded centralised" agent versions, which need to be recompiled manually, or described problem has some other nature? in case it is, which version of agent starts to be too old?