Finally I've done it with Hook:ConfigurationPoll and I check for both "node name" and "Interface name" as well. If it matches both of them then I set Interface Expected State to Ignore interfaces = GetNodeInterfaces($node); foreach (interface : interfaces) { if ( $node->name ~="(?i)Node1Name" && interface->name ~= "(?i)tun.*" ){ SetInterfaceExpectedState(interface, "IGNORE"); }else if ( $node->name ~="(?i)Node2Name" && interface->name ~= "(?i)tun.*|vmnet.*|docker.*|docker_gwbridge|vboxnet.*" ){ SetInterfaceExpectedState(interface, "IGNORE");} }

Hi! Yes, it is possible, for the available requests have a look at this documentation page: https://www.netxms.org/documentation/adminguide/advanced.html#web-api-rest-api. The WebApi is currently in early development but it will soon be updated with many more features! Regards, Eriks

@victor said in mac os-x freezing on server user/password window: Hi, you should downgrade your Java to version 8 update 151. version 8u161 is known to be causing this issue. Best regards, Victor Thank you!! I will pass this along!

Hi, are you sure that DNS name swi-hp-304-2 can be resolved from machine where ping subagent runs? Best regards, Victor

Hi! Thank you for the information. Best regards, Sch.Donat

Hi, I'm sorry. Thank you for pointing out. Windows teaming + NLB unicast mode was the cause. Because the NLB's unicast mode shares the same MAC address, packets arrive on each interface, so packets received by each interface were duplicated. Since the connection destination switch was compatible with IGMP snooping, solving it by enabling IGMP snooping and making NLB from unicast mode to IGMP multicast. Thanks for the advice. Thank you very much.

As gdodd said, you will need a tool like https://nxlog.co/products/nxlog-community-edition to forward Windows Event Log messages to a syslog server, as Windows Events and syslog (which is used on pretty much anything but Windows) are completely different formats. Depending on what you want to do, using Logwatch may be sufficient. The NetXMS agent monitors the Event Log for specific messages. Once such a message is found, the agent triggers a NetXMS Event on the NetXMS server. Those events can then be processed via NetXMS Event Processing Policies for alerting or actions. For our use case, Logwatch is all we need (i.e. we're not using nxlog or any other tool like it). But if you really want/need to forward every log message from a Windows server to a centralised syslog server for storage/processing, you'll have to use a third party tool like the one mentioned.

Downloaded the last release of sql and everything went through OK thx.

Hi all, For anybody reading, I think I've fixed the issue. Seems to have been the firewall; I'll list all the troubleshooting steps anyway just in case they help anybody else: Noticed Java listening on tcp6 (IPv6), switched Java to bind to IPv4 using this command: export _JAVA_OPTIONS="-Djava.net.preferIPv4Stack=true" I could't telnet to the server on 4710, which lead me to look at the firewall. Allowed all traffic on the local interface with the following: firewall-cmd --permanent --zone=trusted --add-interface=lo Restarted the reporting engine and netxmsd, waited around 30 seconds and the Report Server perspective loaded correctly: [image: PWTOEEQ.png]

@zachow said in installing on Centos 7: @91jme said in installing on Centos 7: You may find the directory is actually "/usr/local/lib/netxms/". Thanks for the suggestion. I took a look, and there is a .ddr file, but this doesnt seem to be the DB file. (I have attached screenshot) I havent changed any settings regarding the DB. Any other suggestions? Have you already tried starting the daemon as root? "sudo /usr/local/bin/nxagentd -d"?

Hi Victor; thanks for your reply, i attached 3 new screenshots: the first one shows the linK General Properties Panel , and indeed it is based on the status of Po1 interface. the others show the status of the interface on the switch at the moment when it is yellow on the map best regards [image: link General Properties.jpg] [image: Interface Status.jpg] [image: Interface Status 01.jpg]

I found them in the archive, thanks Tursiops

Misconfiguration on my part. Inother DCI was using the same event.

The only option I see is to set custom attributes with maintenance entrance time on EnterMaintenance($node) function execution. Create a script that will go through all nodes every minute and will check the custom attribute with maintenance start and will initiate maintenance leave in case if the note is in maintenance more than an hour.

Find template function using https://wiki.netxms.org/wiki/NXSL:FindObject function and then iterate over children using https://wiki.netxms.org/wiki/NXSL:GetObjectChildren function and for every netObject with type Node execute GetDCIValueByDescription.

Hi. Update Managed to solve it by `update-alternatives --config java` and setting standard Java to 8. Now netxms is working again. Thank you for helping me. @swedeozzie said in Netxms does not start after update (Debian): Hi. I may or may not be a real noob... still can't get it to work. Tried it and ill attach the ini and error i get.. Good thing is i get a different error Thank you for all the help.

Hi, Thank you very much for your quick response any time. Best regards,

Hi, from your description it's hard to tell if that was misconfiguration or a wrong data received from agent. If you get this issue next time check raw data of parameter and event log for the node for generated events. Best regards, Victor

Install DB on the new server Install NetXMS on the new server, cancel configuration wizard Dump old database / restore on the new server Copy configuration files (c:\netxms\etc\*.conf) Adjust configuration files (credentials, IP addresses, etc.) run "nxdbmgr upgrade" Start "NetXMS Core" service. We can perform migration for you remotely, please contact us at [email protected] for a quote.

High number of active alarms can also be an issue as server will cache them on startup. But usually you should not have many active alarms, if you do it's likely some flaw in your event processing logic. Best regards, Victor