NetXMS Support Forum

Hello

Any tips how to solve following error message, i get it when trying to migrate from MSSQL to Postgresql?

Migrating table snmp_ports
SQL query failed (23505 ERROR:  duplicate key value violates unique constraint "
snmp_ports_pkey"
DETAIL:  Key (id)=(1) already exists.):
INSERT INTO snmp_ports (id,port,zone) VALUES (?,?,?)
Failed input record:
   id = "1"
   port = "161"
   zone = "0"
Database migration failed.

"My desire is to have a map that supports network connection linkage" +10 to this idea.

Out of curiosity, if node inherites custom attribute + value from template and later that value is modified on node, will it return to template value at some point ?

Today i noticed a different behavior from NetXms, not sure from what version it started.

Basicly i have template for each logical drive letter: C,D,E etc. In that template, 2 dci is created per drive and one dci is with threshold value "%{dci-DiskFreeGB-C:50}". "dci-DiskFreeGB-C" is inherited from template and by default is empty. So expected behavior was when drive free space is under 50, trigger alert. But today i noticed that when empty "dci-DiskFreeGB-C" is inherited no alerts are triggered. When i set "dci-DiskFreeGB-C" manualy to 50 then it will work. So easy fix right, lets set template inherited value to 50, but for some reason it wount be inherited. Even if i remove node from template and do another config discovery, still no luck. Next i tryed to removed template custom atribute and re add note, from some mysterios place it still auto inherits it.

Any ideas ?

Yes, using desktop management console. Unfortunately i dont have log messages.

Fix was to delete last element from DB tabel "network_map_elements". then quick server restart and map started working again.

Simple way how to reproduce: Create costum map and add dci container. Under dci container->Data source add format string "Packet Loss: %s %". This will breake the map. Correct string would be "Packet Loss: %s %%".

Egert

Version 3.4.178

Egert

Hello

After adding dci container to network map, map is broken. No scroll bars and no tool icons (top right corner). Where are map elements stored in db so i could remove it manualy and restore map?

Also would it be possible to add some check when inserting dci containers so it would not be so easy to break map?

format string that broke map: "Packet Loss: %s %"

Egert

Hello

Would it be possible to add "Package Manager" option to deploy package once agent is online ?

Egert

Seems that issue is still present. Active agent version is 3.3.314 and trying to upgrade to 3.4.178 with package manager. After few seconds i get message failed - File transfer failed.

Hello

Is it possible to create "advanced" dci poll like:

Example 1: Check if windows service is running and network speed is above some value. If some criteria is not matched, return specific alert message, not just general error.

Example 2: Check for multiple wifi ap frequencis on same tower and if they overlap then alert, but with specific message again, like what ap's are overlaping.

Example 3: Count specific node events per given time. Like Event X happened over last 7 days.

Egert

In Package Manager:

• Uploading
• File transfer failed

Upgrade log:

They are present yes.

Also, sometimes when the station disconnects for short ammount of time then forcing dci poll will clear unsupported errors. Other times when station is down longer, i have to manualy resolve and terminate them.

Hello

Default EPP is present and active, that generates alarm with sys_dci_disabled / sys_dci_unsupported. Also one that terminates alarms with sys_dci_active.

Any other ideas why certain node dci wount get cleared ? When i check dci history its older than unsupported alarm date, so its definitly old dci and not new. maybe somthing with instance discovery is messing with auto alarm termination ?

Hello

What could cause the following behavior: Lets say i have Ubiquity ap added to NetXms and with template it gets dci-s to monitor. Under that template there is instance discovery for every connected station. Now when station gets disconnected for x amount of time, the instance dci values turn into unsupported. When station returns the dci monitoring continues but alerts for unsupported never dissapear. I checked manualy and oid is same in old and new discovery. Any way how to auto terminate them ?

Egert

I am upgrading with "Package Manager".