NetXMS Support Forum

Hello guys,
I have a cronjob evey night for backing up everything, mysql and configuration files. The mysqldump takes some time though, around 6 minutes +
netxms reports a critical event after 3 minutes of the start of dump: Thread "Syncer Thread" is not responding
I assume that this is because of the mysqldump.
Is there another approach of doing daily backups?
should you stop/pause netxms service and then backup?
or is there a way to disable that check?

Hello all,
I'm facing a problem, on a pc that has tunnel interfaces for VPN connections. After the interface get up/down then it deletes the interface and recreates it, and it also gives it an expected state up so I get notifications and email warnings.
I've done delete the interface, obviously doesn't helped. On interfaces I've done unmanage and exclude this interface from network topology with expected state ignore. Nothing of that helps.
Is there another way to disable all other interfaces except the ethernet interface, or at least make for that specific node(pc) default expected state for new interfaces to be ignonre?
here is a part of event log of that node:

ID Time Source DCI Event Sevirety Message Root ID
591861 06.11.2018 12:25:32 PC 0 SYS_IF_UP Normal Interface "tun1" changed state to UP (IP Addr: 10.0.1.6/32) 0
591895 06.11.2018 13:15:34 PC 0 SYS_IF_DOWN Minor Interface "tun1" changed state to DOWN (IP Addr: 10.0.1.6/32) 0
591916 06.11.2018 13:24:17 PC 0 SYS_IF_ADDED Normal Interface "tun1" added (IP Addr: 10.0.1.6/32, IfIndex: 36) 0
591915 06.11.2018 13:24:17 PC 0 SYS_IF_DELETED Normal Interface "tun1" deleted (IP Addr: 10.0.1.6/32, IfIndex: 35) 0
591917 06.11.2018 13:24:47 PC 0 SYS_IF_EXPECTED_STATE_UP Normal Expected state for interface "tun1" set to UP 0
591918 06.11.2018 13:25:52 PC 0 SYS_IF_UP Normal Interface "tun1" changed state to UP (IP Addr: 10.0.1.6/32) 0
592005 06.11.2018 14:54:23 PC 0 SYS_IF_EXPECTED_STATE_IGNORE Normal Expected state for interface "tun1" set to IGNORE 0
592078 06.11.2018 16:24:32 PC 0 SYS_IF_ADDED Normal Interface "tun1" added (IP Addr: 10.0.1.6/32, IfIndex: 37) 0
592079 06.11.2018 16:24:42 PC 0 SYS_IF_EXPECTED_STATE_UP Normal Expected state for interface "tun1" set to UP 0
592080 06.11.2018 16:25:47 PC 0 SYS_IF_UP Normal Interface "tun1" changed state to UP (IP Addr: 10.0.1.6/32) 0


Hello all,
I have a question, is there a way for some specific interfaces from a node send email alerts on another additional email address, when the interface change state other than expected?
thank you in advance

Hello again,
I was wondering if there is a way to group email alerts.
The reason I'm asking is because in a device ex. a switch I could have set a lot of data collection items with thresholds as well.
When a critical problem could happen on the switch ex. power failure the switch is unavailable and I'm getting alerts from thresholds port state and device status which it will result from around 7-10 warning/critical email per device, and same when it gets back to normal.
Is there a possible way to group alerts, for example in that situation to group everything and tell netxms to send only 1 email with all the problems or a status problem?
Thank you in advance

Hello all,
I've been using netxms as snmp server for more than a year. I'm quite pleased with the service but I'm having an issue regarding to agent polling.
I've configured several devices. On the servers(centos and ubuntu) I use the netxms agent for polling.
what happens sometimes is after netxms server reboot (and maybe when the "clients" or agents are not yet ready) I'm having problem on polling data.
When I do a status poll on the agent "clinet" I get this:
[05.03.2018 12:28:43] **** Poll request sent to server ****
[05.03.2018 12:28:43] Poll request accepted
[05.03.2018 12:28:43] Starting status poll for node sftptest
[05.03.2018 12:28:43]    Starting status poll on interface lo
[05.03.2018 12:28:43]       Current interface status is UNKNOWN
[05.03.2018 12:28:43]       Interface status cannot be determined
[05.03.2018 12:28:43]       Interface is UNKNOWN for 21239 polls (1 poll required for status change)
[05.03.2018 12:28:43]       Interface status after poll is UNKNOWN
[05.03.2018 12:28:43]    Finished status poll on interface lo
[05.03.2018 12:28:43]    Starting status poll on interface eth0
[05.03.2018 12:28:43]       Current interface status is NORMAL
[05.03.2018 12:28:43]       Starting ICMP ping
[05.03.2018 12:28:43]       Interface is NORMAL for 21238 polls (1 poll required for status change)
[05.03.2018 12:28:43]       Interface status after poll is NORMAL
[05.03.2018 12:28:43]    Finished status poll on interface eth0
[05.03.2018 12:28:43] Node is connected
[05.03.2018 12:28:43] Finished status poll for node sftptest
[05.03.2018 12:28:43] Node status after poll is NORMAL
[05.03.2018 12:28:43] **** Poll completed successfully ****
If I disable usage of ICMP pings for status polling I get this:
[05.03.2018 12:37:25] **** Poll request sent to server ****
[05.03.2018 12:37:25] Poll request accepted
[05.03.2018 12:37:25] Starting status poll for node sftptest
[05.03.2018 12:37:25]    Starting status poll on interface lo
[05.03.2018 12:37:25]       Current interface status is UNKNOWN
[05.03.2018 12:37:25]       Interface status cannot be determined
[05.03.2018 12:37:25]       Interface is UNKNOWN for 21248 polls (1 poll required for status change)
[05.03.2018 12:37:25]       Interface status after poll is UNKNOWN
[05.03.2018 12:37:25]    Finished status poll on interface lo
[05.03.2018 12:37:25]    Starting status poll on interface eth0
[05.03.2018 12:37:25]       Current interface status is UNKNOWN
[05.03.2018 12:37:25]       Interface status cannot be determined
[05.03.2018 12:37:25]       Interface is UNKNOWN for 1 poll (1 poll required for status change)
[05.03.2018 12:37:25]       Interface status after poll is UNKNOWN
[05.03.2018 12:37:25]    Finished status poll on interface eth0
[05.03.2018 12:37:25] Node is still unreachable
[05.03.2018 12:37:25] Finished status poll for node sftptest
[05.03.2018 12:37:25] Node status after poll is UNKNOWN
[05.03.2018 12:37:25] **** Poll completed successfully ****

From what I see is like server is not even trying to poll from netxms agent on that machine. Also on the overview of the machine on capabilities the isAgent has switched to No.
Firewall ports are open
At the Switches and router that I'm doing snmp polls I've never had that issue.
Normally if I do a reboot on netxms server it will solve the issue, but is there anyway to track the problem in order not to happen again, because it could happen and I could notice it after a few days.

On netxms server and the other machine's agents I don't get any logs.
Netxms current version is 2.2.1, but I've got this issue from previous versions as well.
Netxms server is on centos.