NetXMS Support Forum

The screenshot Victor asked for was for the "Interfaces" tab underneath the Object details. Something like the one attached.

Just to confirm your question:
- your switch is in multiple VLANs and networks
- your switch shows under every one of those networks underneath "Entire Network"
- when you expand the switch under any of those networks, it shows all interfaces, every time
- You are expecting that the switch will only list the interfaces which are actually a part of those networks

I guess the answer is that NetXMS does not treat interfaces under Entire Network like that. It only confirms if the node itself is in the network.
When you expand the node, it will list all child objects, e.g. interfaces. There is no filtering applied.

If the above is correct, I suggest submitting a feature request to filter interfaces listed on nodes under Entire Network to only show if the interfaces themselves are a part of the selected network.

Cheers,
Tursiops

I am not aware of a tool that will create tables for you at present.
Setting one up however is a relatively quick process, assuming you know what you are looking for.

My process tends to be as follows:

• Determine the Index in the table (I've encountered several in the past where the actual Index was not really an Index).
• Determine which other OIDs you want to collect
  Some tables will likely contain a lot more information than you need/want, the first screenshot is an example of that.
• Create Table DCI
• Under General, set Index OID as Parameter (second screenshot)
• Under Columns, add the other OIDs, one by one (third screenshot)

Attached screenshots are for a Cisco WAP (which happens to be one of those "Index != Index" ones, hence the parameter does not end on 1, but 4).

That would make sense then. We're using 2.1-M2 as well.

At present we detect when the Agent crashes and restart the service automatically.
(That doesn't always work either, as we also use quite a few ExternalParameters which call PowerShell. For some reason sometimes a PowerShell process will just keep running and lock port 4700. So when NetXMS stops, it can not start again until the PowerShell process in question is terminated. But that's probably a different issue to the Event Log one.)

Appears the issue is related to DCI Tables.
All segfault backtraces mention DCTable.
I then ran netxmsd with -D9 option for testing and found several prepare statements for a DCI Table prior to the crash - but no completed sync.

I had such an issue in the past with a template for Intel Modular servers. When I could not determine the underlying cause, I "simply" switched all tables in all templates to instances and the system had been stable since. Appears I missed one: a single template (for a Netgear ReadyNAS) with a single device bound to it still had DCI tables in use.
It appears the NAS performed an automatic firmware upgrade to version 6.6.1 and within an hour NetXMS started crashing. It is not clear if the template for the NAS had not been applied until after the upgrade (auto-apply rules) or if the upgrade simply triggered something in the SNMP responses that caused the crashes of the server.

Since I disabled the DCI Tables, the server has not crashed (around 90 minutes of uptime now, over 6 times as long as the longest interval between crashes before that). It looks like there is some kind of issue within the DCI table code that can lead to segfaults and server crashes.

I am currently restarting netxmsd in a loop via bash script, i.e. it crashes, it starts again. segfaults are written into separate files each time.
Based on that, it's currently crashing every 7-15 minutes. I've attached another text file with five more segfaults (I skipped the memory map part for these).

Is there anything else I can do/provide to help resolve these crashes?

Ok, Using LD_PRELOAD=/lib/x86_64-linux-gnu/libSegFault.so netxmsd -q -D4 worked. Assuming the result is what is expected.

Attached a screenshot of the last few lines of standard debug logging and the segfault output.
It doesn't tell me anything, but hopefully it helps in determining what's going on...

Hi,

On Friday evening, our NetXMS server started segfaulting. I can't pin down what's causing it, but I basically can't run it for more than maybe 15-20 minutes before it crashes again.
I tried to follow the instructions given at https://wiki.netxms.org/wiki/Running_NetXMS_under_debugger to obtain a backtrace, but the result is that the netxmsd service stops responding and so does gdb, i.e. it never returns to the gdb prompt and I can't get a trace. I basically have to open another session and kill the gdp process itself. If I kill netxms, gdb is no longer attached to the process and I can't get a trace either.

Anything else I can try to get that elusive backtrace?

Cheers

Hi,

I've started testing Windows Event Log monitoring via NetXMS.
Created a basic logwatch file looking for two particular backup related events.
In general, this works ok - except sometimes the agent will just crash when a matching event is found.
The matching event is not recorded on the NetXMS server, but I can see the message in the Windows Event Log.
The agent at that point requires a manual restart, which works just fine.
I've automated the restart part and can confirm that any such crash occurs at the same time as one of the two backup messages is logged.
The same event an hour later then works fine.

I have been unable to find a pattern here, it seems completely random. An agent can run for days or just hours.
If the logwatch syntax was at fault, it should either not work or crash every time - but it doesn't.

Not sure if anyone else has seen something like this?

Cheers

Does a DCI called "Status" exist on the node?
I know this used to be an internal DCI that was added for any node automatically, but it isn't in newer versions.

You may have to create a script DCI providing the result of $node->status for what you are trying to achieve.
See https://wiki.netxms.org/wiki/NXSL:NetObj for possible values.

Hi,

I've started putting some location data into NetXMS and also installed an Android agent to test Geolocation History.
The server is currently running 2.1-M1.

Using this left me with a few of questions:
- When I add containers to a map (I've added locations to containers as they represent entire sites including multiple devices) and right-click on a container in the map, NetXMS allows me to do some very basic things like "Status Map" or "Software Inventory". I can't do Summary Tables, Event Log or Syslog. However, if I do in fact select any of the available options first, the second time around I suddenly have all other options available to me as well. This was reproducible, presumably a bug?

- Is it possible for NetXMS to automatically obtain the longitude/latitude of a device from a given address rather than having to rely on a GPS receiver or manually entering the data? Guess using the Java API would work for this (having it integrated would of course be nice touch)?

- If I do have multiple containers (or nodes) at the same location, I can only see one in the map. I can't hover and maybe select one of the other ones or click through them. I can't even see that there is more than one container/node at the location. Not sure if that's something that could be implemented?

Cheers

Scratch that, configuration issue at our end.
A second template was applied which collects the same data - except that template had a 5 minute interval set. 

I'd use a transformation script to filter out the known bad values.

Something like
if ($1 == 99.0) return null;
else return $1;

The above would replace the 99.0 with null. Technically still "bad data" and I admit I did not test using null (I tend to set "0" or some descriptive error, depending on what I'm collecting).

To remove data already collected, you either have to either clear the collected data (which will wipe your good data along with it) or go into your database, locate the bad values and remove them.

Hope this helps.

Hi,

Using 2.1-M1, I noticed that DCIs which are set to poll at the default interval are polling every 5 minutes - except our DefaultDCIPollingInterval is configured as 60 seconds.

Originally I assumed this was due to the rather high poller queue, so delays were expected, but after fixing that, the DCI results started coming in exactly every five minutes (as opposed to 5-6 minutes).

Is that some (new?) lower limit on DCI pollers?

EDIT: This is causing some issues for us, as alerts which used to be triggered after 60 threshold violations are now no longer alerting after an hour, but after 5 hours. Changing the DefaultDCIPollingInterval to 120 doesn't seem to have made a difference - all default DCIs are still checking every 5 minutes.

Cheers

Hi,

I noticed that when I do a search in Syslog, it appears reasonably fast.
But if I select a device, right-click and select Syslog it can take forever to load anything.

So I had a look at the database and found the table only has an index on the msg_timestamp (and msg_id) column, but not the source_object_id one.
Of course I could add one manually (and did for now, which sped things up significantly), but that might cause issues with future NetXMS database upgrades down the track?

Cheers

Hi Marco,

You can right click on the graph, select Properties, then change the Y Axis Range.
However, I believe this is limited to 2^31 as the highest value it will accept, if you enter something higher, the results will not be as expected. Not sure if that's only if you're using 32bit Java and Console. Haven't checked with the web interface.

Alternatively you can simply zoom in on the part you want to see in detail (I think that only works in the console, not the web interface).

Hope that helps