NetXMS Forum

Hi, looks like we did not rebuild libmosquitto (we ship agent with our own build) after moving to OpenSSL 1.1. Attached is correct version of libmosquitto.dll - replace old one in NetXMS\bin and subagent should start. I assume you have 64 bit system - let me know if you need 32 bit version of dll. Best regards, Victor libmosquitto.dll

Hi, Every setting regarding traps in server config is enabled. Event configuration is ok, Write to Event log is enabled. Nikk

You can create scheduled task that will iterate through nodes in given container and call UnbindObject as needed. Best regards, Victor

Hi, yes, it will work. Best regards, Victor

Do you find the solution for that? I have problem with log file encoding in cobian. It is UCS-2 LE BOM (notepad ++ showing) and the parser not working

You can use strftime patterns in file name. For example, to match dd-mm-yy.txt you can use %d-%m-%y.txt as file name. If hour is included, for example yymmddhh.txt - %y%m%d%H.txt. As time changes system will check different file names. If you need something even more complicated you can call external script to determine part of file name, like this: log-`script.cmd`.txt - it will call script.cmd and use it's output as part of file name. Best regards, Victor

Hi, operation and value are ignored for data collection error thresholds. Best regards, Victor

Into NetXMS bin directory, where all other NetXMS exe and dll resides. Best regards, Victor

Thank you!

Thank you, will give a try.

Hi! Looks like this MIB set contains incomplete SNMPv2-SMI module (file rfc2578.txt). It does not define MODULE-IDENTITY, etc. If you remove it and use SNMPv2-SMI.txt from NetXMS distribution those import errors should be gone. Best regards, Victor

Well thanks for solution and offering assistance! But we will till system upgrade, so you don't have to put effort in this! Thanks, Nikk

Sorry for late answer, been busy. I checked with nxget and it returned non-zero value.

Net.RemoteShareStatus should return status code returned by NetUseAdd Windows API call. Level 2 call is used. Best regards, Victor

Yes, first problem was obvious negligence mistake. And with upgrade to 1.2.14 everything works fine, thank you Regards, Nikk

Ok, figured it out. Used the script in the message of the event's event configuration and it worked perfect...

Hi! All ServiceCheck parameters just connects over TCP to target and do some handshaking. If I understand correctly you need to monitor local processes? Then you can just use Process.Count to check that required processes are running. Best regards, Victor

Thank you for response Nikk

Thank you, it worked

Hi, So, is this bug or it isn't implemented yet? Maybe there is another way how to send events to local server? The thing is, that our main devices are located in remote areas, but monitoring should be local. And Proxy-agent connections just occupy the network. Respectfully, Nikk