NetXMS Support Forum

Hi!

Looks like gcc on your system configured to use i386 instruction set by default (see line "Target: i386-redhat-linux" in gcc version output). Atomic functions required at least i486. Try to use compilation flag -march=i486 when building agent, like this:

CPPFLAGS="-march=i486" ./configure other configure options as usual

Best regards,
Victor

Hi!

You can upgrade directly to 1.2.9. Actual upgrade procedure depends on your platform and installation method (from sources or using binary packages). Installation guide (http://wiki.netxms.org/wiki/Server_Installation_Guide) contains necessary upgrade steps.

Best regards,
Victor

The only way I can think of is to create "dummy" DCI and use transformation script to read value from correct OID directly in transformation script.

Best regards,
Victor

Unlikely in 1.2.10, but I'll register as feature request for one of the next releases.

Best regards,
Victor

Hi!

You can create a calculated DCI which will calculate uptime in transformation script, and then add it to dashboard using "gauge" type element. Alternatively, you can create business service and appropriate checks.

Best regards,
Victor

Here it is: http://wiki.netxms.org/wiki/Subagent:Ping

Best regards,
Victor

субагент в аттаче. Инсталлер я порсмотрю, спасибо за репорт.

Seems that atomic functions are missing on XEN server for some reason. What is output of your gcc -v?

Also, you can try to run pre-compiled static agent: https://www.netxms.org/download/agent_packages/nxagent-1.2.9-linux-x86-static.tar.gz - there are good chances that it will work.

Best regards,
Victor

Can you show me results of the following SQL queries:

SELECT * FROM nodes;
SELECT * FROM object_properties;
SELECT * FROM nsmap;

you can send results to [email protected] if it contains sensitive data.

Best regards,
Victor

Hi!

What operating system you run server on? Can you please run it with debug level 6 and send me the log (or check what is logged during housekeeper run)?

Best regards,
Victor

Hi!

Try to look under appropriate subnet in Entire Network tree - it should be there. If not, you can try to stop the server and run nxdbmgr check in case there are database inconsistencies.

Best regards,
Victor

Подставил присланные сообщения в консоль. Могу сделать сборку чтобы можно было посмотреть что получается.

Еще измемение в репозитории - мы перенесли исходники в git, теперь они доступны по git://git.netxms.org/public/netxms.git

Hi!

Looks like a bug. I'll try to reproduce it.

Best regards,
Victor

According to RFC, all object identifiers in SNMP MIB must start with lower case letter. Our MIB compiler is quite strict, this is why you get the error. Try to replace object identifiers like Repeater6500 with repeater6500, and it should compile.

Best regards,
Victor

Events will be generated based on trap OID only. However, you can filter them later in event processing policy. For example, if you have .1.3.6.1.2.1.16.9.1.1.2.839 varbind mapped to event parameter, you can check if it is empty or not. Filtering script for event processing policy will be like


return (($2 != null) && ($2 != ""));


For notifications, you can just use %2 in e-mail action - it will be replaced by full varbind value. Alternatively, you can parse it in filtering script using regular expressions and pass required parts to the email.

Best regards,
Victor