NetXMS Support Forum

Haven't tried this (and our server is currently rather unstable, so can't test it), so I could be completely wrong.

Would it be possible to create an object tool that sets a custom attribute on a node, similar to enabling maintenance mode?
The event processing policy for notifications then filters based on that attribute.
You would still need to split the email notification from the rest in your event processing policies.

Kind of a "maintenance light"?

I'd actually love to test this, if I could. 

Hi Victor,

I am trying that now, will let you know how it goes.

I noticed something in the logs on the latest crash (prior to configuration change) which seemed odd:
[ERROR] SQL query failed (Query = "SELECT idata_value,idata_timestamp FROM idata_225 WHERE item_id=1047081695 ORDER BY idata_timestamp DESC LIMIT 32767"): 42P01 ERROR:  relation "idata_225" does not exist LINE 1: SELECT idata_value,idata_timestamp FROM idata_225 WHERE item...

I have no idea why NetXMS would try to query a table that doesn't exist for an item_id which definitely does not exist (way too high, max(item_id) in the items table is currently '668531'). This was literally the last entry in the log (I did not see anything like this in the previous crashes though).

Cheers

Closing the Alarm Browser makes a huge difference, so for the last few days, we have avoided opening it.
Clicking on a container or network in the system with Object Details open can slow it right down again and it does seem to depend on the number of alerts.
My guess right now is that loading the alarms is triggering this, maybe adding the zones column is causing some queries to run a lot slower? Some missing index?

Not sure if my other issue with "Change Zone" in the GUI not actually moving a device into the matching Zone is related either.
(Change zone moving devices into the zone with the Object ID of the Zone selected, instead of the Zone GUID).

Hi,

Ok, after checking on multiple other systems, the performance of the Console has definitely seriously degraded going from 2.1-M3 to 2.1-RC1. At times, this is to the point of being unusable - some tabs won't load, Windows will tell us the application is "Not Reponding" and going into Alarm views for the entire network is futile.

I am unsure what has changed between versions?
The web console is just as bad. 

Cheers

I am guessing that the System.Update.LastInstallTime is based on reading the Windows Update registry value, which Microsoft removed with Windows 10 and Server 2016, i.e. it won't work anymore.

The following PowerShell gives you the date of the last successful Windows Update installation (works for me, but knowing when my system last installed updates, the time appears to be in UTC):
$updateSearch = (New-Object -ComObject Microsoft.Update.Session ).CreateUpdateSearcher()
($updateSearch.QueryHistory(0,$updateSearch.GetTotalHistoryCount())| ?{$_.ResultCode -eq 2}|Sort-Object -Property Date -Descending).Date|Select -First 1

For some more background into, quoting "https://stackoverflow.com/questions/33732541/powershell-how-to-get-date-of-last-windows-update-install-or-at-least-checked-f":
$Session = New-Object -ComObject Microsoft.Update.Session
$Searcher = $Session.CreateUpdateSearcher()
$HistoryCount = $Searcher.GetTotalHistoryCount()
# http://msdn.microsoft.com/en-us/library/windows/desktop/aa386532%28v=vs.85%29.aspx
$Searcher.QueryHistory(0,$HistoryCount) | ForEach-Object {$_}

This will list all updates which the system tried to install, including a timestamp (which on my system appears to be UTC) and a result code.
Those translate to:
0 = Not Started
1 = In Progress
2 = Succeeded
3 = Succeeded With Errrors
4 = Failed
5 = Aborted

If a patch failed to install several times, it is supposedly listed several times as well. I cannot confirm that, as I have no failed patches in my list.
It also appears that the large cumulative updates like the Creators Update resets the contents of the list. Mine only goes back to said Creators Update.
Either way, with a bit of scripting you can return a few more things, like the number of unique patches which have failed to install.

I am not sure if the status 0 could be used to determine how many patches the system knows about that are not installed yet.

The random segfaults continue. I can't get a backtrace using the method described in the Wiki - it never returns to gdb after crashing. Not sure if I am missing something?

Here's another segfault output (no idea if that helps at all):
*** Error in `netxmsd': corrupted double-linked list: 0x00007f33103c6710 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f339ec357e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x81f88)[0x7f339ec3ff88]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f339ec415d4]
/lib/x86_64-linux-gnu/libc.so.6(+0x2a315)[0x7f339ebe8315]
/lib/x86_64-linux-gnu/libc.so.6(+0x227fc)[0x7f339ebe07fc]
/lib/x86_64-linux-gnu/libc.so.6(+0x213a3)[0x7f339ebdf3a3]
/lib/x86_64-linux-gnu/libc.so.6(iconv_open+0x22a)[0x7f339ebdee2a]
/usr/lib/x86_64-linux-gnu/libnetxms.so.2(ucs4_to_ucs2+0x3a)[0x7f339ef9fa5a]
/usr/lib/x86_64-linux-gnu/libnetxms.so.2(_ZN11NXCPMessage3setEjhPKvbm+0x548)[0x7f339efb4758]
/usr/lib/x86_64-linux-gnu/libnxcore.so.2(_ZN6DCItem20fillLastValueMessageEP11NXCPMessagej+0x92)[0x7f339f4a7d52]
/usr/lib/x86_64-linux-gnu/libnxcore.so.2(_ZN20DataCollectionTarget25fillMessageInternalStage2EP11NXCPMessage+0x124)[0x7f339f4b9504]
/usr/lib/x86_64-linux-gnu/libnxcore.so.2(_ZN6NetObj11fillMessageEP11NXCPMessage+0x5e)[0x7f339f4e758e]
/usr/lib/x86_64-linux-gnu/libnxcore.so.2(_ZN13ClientSession12updateThreadEv+0x21c)[0x7f339f524dcc]
/usr/lib/x86_64-linux-gnu/libnxcore.so.2(_ZN13ClientSession19updateThreadStarterEPv+0x9)[0x7f339f525079]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f339d01d6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f339ecc482d]


Cheers

Hi,

Since the upgrade to 2.1-RC1, the NetXMS Management Console, including the web interface seems to be significantly slower than before.
Especially alert handling. Not sure if that's related to the new Zone column being added to it (and us having a lot of zones & alerts).

Has anyone else encountered/noticed this?

Cheers

Check the version of the Web UI as shown in the bottom right corner of the logon screen and compare it with the NetXMS server version you are running.
If they do not match, you will see this error.

Hi,

Would it be possible to add an "isPhone" flag to nodes?

For phones which do not support SNMP (or where the vendor has locked it down), this could maybe be passively determined via switches CDP/LLDP data during a topology poll? I can't see the device type when I check the LLDP table on a switch in NetXMS, but on the managed switches themselves, the data appears to be there.

Cheers

Hi,

I've been testing passive network discovery via proxy/zones and so far is working quite well.
However, when it detects a node that has neither an agent on it nor SNMP enabled to query for the hostname, it adds the node just by the IP address.
I can see in the logs that it is trying to resolve the IP to a hostname, but this appears to happen on the NetXMS server itself, not the proxy node of the zone through which the discovery happened?
This can lead to a rather large amount of not too useful nodes ending up in the system.

For now I just wrote a hook that basically sets anything to unmanaged that has neither an agent nor SNMP and ignore those systems.
But it would be nice for mapping purposes, if they would show with their correct hostnames as per local DNS.

Cheers

Hi,

I've been doing some testing with an informational trap which one of our systems generates every few minutes.

My first real excursion into SNMP traps, but I can't get the parameter to be passed using varbinds either.
It does not matter if I use POS:1, POS:2 or POS:3 (for the first and only varbind in this trap) and "Never convert value to hex string" makes no difference.

Setting up a mapping by object ID works perfectly fine.

Cheers

Hi,

Ok, I am pretty sure I stumbled into a bug in 2.1 with this issue.

When I move a node into the "Default" zone, which has Zone ID 0, it does not place the node into that zone.
Instead if places it into a different zone with Zone ID 4.
"4" happens to be the Object ID of the Default zone (not the Zone ID).

Looks like moving zones in 2.1 is linking up the wrong IDs?

That also explains the Invalid Zone ID errors we are seeing.
Our Object IDs are way higher than any Zone ID we ever assigned, so in almost all cases, it wouldn't be able to find a match at all - hence "Invalid Zone ID".

That's a bit of a problem for us right now, as we can't move nodes into the correct zones and nodes we previously tried to move into the Default zone for testing are stuck in a zone they don't belong in.

Cheers

Yes, that's correct.

Hi lindeamon,

Not sure if I got that right, as I don't do a lot with SNMP traps, but it looks like the Trap OID you have in your mapping is not the same as the trap you are receiving?
Your mapping is for .1.3.6.1.4.1.12356.100.1.3.0.999, but the Trap OID is .1.3.6.1.4.1.12356.101.2.0.505?
The event log seems to be referencing event [100057] (by ID, not by name - does that event still exist?), not fnTrapTest (with ID 100067)?

Cheers

Hi Victor,

after the crash, the debugger prompt did not re-appear.
It's just stuck showing me loads of lines in the following style:
[New Thread 0x7ffdd22b1700 (LWP 28753)]
These look pretty standard during NetXMS operation and not related to the actual crash.

The netxmsd process itself was still showing in the process list as well, but would not stop unless I sent a kill -9.
At that point, of course, the thread in gdb terminated as well and I could not run a backtrace.

Cheers