NetXMS Support Forum

Hi!

I see that you are using @{timestamp} macro, but you didn't define it. You should either define the macro, or specify valid regular expression in matching rule.

Best regards,
Victor

Hi!

Network discovery is not working in remote zones yet. You have to add devices in remote zones manually. We will address this issue in one of next releases.

Best regards,
Victor

Hi!

The only workaround I've found is to generate alarm for that node with "Normal" state and keep it in outstanding or acknowledged state. I've added a feature request for adding DCI based status calculation (https://www.radensolutions.com/chiliproject/issues/324).

Best regards,
Victor

Hi!

System does not search MIBs automatically for a match. You should create matching between traps and events in SNMP trap configurator (Configuration -> SNMP Traps COnfiguration in console).

Best regards,
Victor

Такое бывает при обновлении, когда в /usr/local/lib лежат библиотеки от предыдущей версии. Если ето обновление, то попробуйте удалить старые библиотеки перед сборкой.

Hi!

Currently it's not possible. Most likely you can use some command line mail sending tool instead of built-in to send mails with attachments.

Best regards,
Victor

Hi!

Can you enable debug on server and check server log when you create map object? I cannot reproduce this on test system, so it should be related to your specific system and/or configuration.

Best regards,
Victor

Hi!

I've found syntax error in transformation script - if statement starts with capital letter:

If (CurrentStatus == 0 || CurrentStatus == 4)

after changing it to lowercase, script seems to be working.

Best regards,
Victor

Hi!

I plan to release 1.2.9 by end of August. It will be mostly bugfix release.
Btw, I completely forgot about patched 1.2.8 console I promise you. There are download links:

https://netxms.org/download/nxmc/nxmc-1.2.8-fp1-win32-x64.zip
https://netxms.org/download/nxmc/nxmc-1.2.8-fp1-win32-x86.zip

Best regards,
Victor

Hi!

You have to add node where you create proxied DCI to proxy node's "trusted nodes" list, or turn off trusted nodes checking by setting server configuration variable CheckTrustedNodes to 0. A bit more detailed explanation of trusted nodes concept is here: http://wiki.netxms.org/wiki/SG:Security_Issues.

Best regards,
Victor

Hi!

You can create two links, but they will take same path on the map. You have to change routing to "bend points" for at least one of them and lay it out manually.

Best regards,
Victor

Hi!

Problem is that NXSL does not understand ".1" notation - you have to give it as "0.1".
Btw, you can check your scripts with nxscript command line tool:


C:\Source\NetXMS\x64\debug>nxscript -r test.nxsl
NetXMS Scripting Host  Version 1.2.8
Copyright (c) 2005-2013 Victor Kirhenshtein

syntax error, unexpected '.'

C:\Source\NetXMS\x64\debug>


Best regards,
Victor

Quote from: Nikk on August 14, 2013, 01:02:39 PM
But on the sender server i still get   ISC::ReceiverThread(): RecvNXCPMessage() failed: error=0, socket_error=0 ..
Maybe that's how it should be, I don't know.

It is misleading message: in fact, error code 0 means that connection was just closed. That's ok, other side can close connection when it's not needed.

Best regards,
Victor

Вопрос в том, правильное ли UTC время на сервере. Например, если на сервере стоит тайм зона UTC-3, а реально время на нем выставлено так, чтобы выглядело правильно в UTC-2, то внутреннее UTC время будет отличатся на 1 час от правильного.

В чем причина проблемы вроде ясно. Поскольку проблема в том, как реализована обработка входящих syslog сообщений, то без переделки кода эту проблему решить нельзя. В 1.2.9 мы исправим проблемное место, и должно заработать как надо.