NetXMS Support Forum

It seems there is same problem with address_lists table. Try to set PK using columns list_type,community_id,addr_type,addr1,addr2. Also check vpn_connector_networks table - if it doesn't have PK, set it on columns vpn_id,ip_addr.

Best regards,
Victor

Hi,

I think we can make it in 2.1-M3 or 2.1-M4.

Best regards,
Victor

Следующий запуск housekeeper'a все лишнее вычистит.

Please check that cluster_sync_subnets table has primary key. If not, try to create primary key (using columns cluster_id and subnet_addr) and re-run DB migration.

Best regards,
Victor

Hi,

you can also disable template auto import by setting server configuration parameter ImportConfigurationOnStartup to 0. It is preferred method, because after upgrade standard templates will be back in share/templates.

Best regards,
Victor

Hi,

there is no way to determine exact cause without access to agent log. In agent log you will find record started with text "LogWatch: Unable to open event log". Btw, if you can edit agent's config from console, you can enable file manager subagent and download agent's log file.

Best regards,
Victor

Hi,

could you please run this query manually (for example in SQL Server Management Studio) and post detailed error message?

Best regards,
Victor

Hi,

currently it's not possible. I've added it as feature request (https://dev.raden.solutions/issues/1384).

Best regards,
Victor

Hi,

currently it's not configurable. Feel free to enter appropriate feature request into our tracker.

Best regards,
Victor

Hi all!

NetXMS version 2.0.8 is out. It is final patch release for 2.0 branch. Changes since 2.0.7:

- Fixed response parsing in MyMobile SMS driver
- Improved HP ProCurve driver
- Fixed high CPU load on FreeBSD
- Event sending by agent do not restricted to master servers only anymore
- Default RADIUS authentication method set to PAP to maintain compatibility with older versions
- Fixed issues: #1258, #1311, #1314, #1351, #1352, #1357, #1376

Best regards,
Victor

Hi,

agent installer is build using InnoSetup. There is MSI wrapper that can wrap installer exe into MSI suitable for GPO deployment - http://www.exemsi.com/inno-setup-and-msi, although I didn't try it myself. You may need to specify installer options for unattended installation - they described here: https://wiki.netxms.org/wiki/Agent_Installation_Guide#Unattended_installation_of_NetXMS_Agent_on_Windows.

Best regards,
Victor

Hi,

in map options (map object properties -> "Map Options" page) turn on "Include end nodes" checkbox.

Best regards,
Victor

Hi,

simplest way is to define instance discovery DCI with SNMP based discovery:

1. use parameter name .1.3.6.1.4.1.14988.1.1.3.8.{instance}
2. set origin to SNMP
3. set instance discovery method to "SNMP Walk - OIDs"
4. set base SNMP OID to .1.3.6.1.4.1.14988.1.1.3.8
5. leave filter script empty

Such instance discovery DCI will create single instance .1.3.6.1.4.1.14988.1.1.3.8.0 when it is supported and will not create anything when it is not supported.

As for .1.3.6.1.4.1.14988.1.1.1.4 - you should use .1.3.6.1.4.1.14988.1.1.1.4.0 as parameter name (you can see full OID in walk result).

Best regards,
Victor

Hi,

it's already fixed in version 2.1-M1. This fix is also included into upcoming 2.0.8 patch release.

Best regards,
Victor

What version of NetXMS you are using? At some point there was a bug when IP address was inverted. Just in case, try to specify destination server address as 42.228.19.172.

Best regards,
Victor