NetXMS Support Forum

Hi!

NetXMS shows all interfaces reported by device. You may also see logical interfaces (like software loopbacks). To configure data collection for interface, right click on interface you want to monitor and choose "Create data collection items" from menu. Collected data will be displayed in last values for interface's node object.

Best regards,
Victor

Hi,

so far our analysis shows that root of the problem is that some internal data structures are not initialized properly (if you are familiar with C++ - it seems that constructor for global instance of AlarmManager class is not called), although it is not clear why this happens. I try your binaries on CentOS 6.3 (closest that I can find) and it works as expected. Is it an option to do system upgrade to latest versions of kernel and glibc and try again? If this will not help, I'll re-write alarm manager initialization and provide you with intermediate build for testing.

Best regards,
Victor

You can gdnerate events using nxevent command line tool.

Best regards,
Victor

Hi,

I'll check this. Anyway, MIB compilation is a last step, so even if it fails, all new binaries are already in place. You can delete offending MIB file and run MIB compiler manually. You got same error after building 1.2.3 because this MIB file was already copied into MIB directory by 1.2.16 installer.

Best regards,
Victor

Hi,

you can do this using agent and parameter File.Size with recursive option set to on. For example, to monitor total size of all files under /home/user, add the following DCI:

File.Size(/home/user,*,1)

For reference, full description of File.Size is below:

File.Size(path, pattern, recursive, size, age)
where
    path    : path to directory or file to check
    pattern : pattern for file name matching
    recursive : recursion flag; if set to 1 or true, agent will scan subdirectories
    size      : size filter; if < 0, only files with size less than abs(value) will match;
                          if > 0, only files with size greater than value will match
    age       : age filter; if < 0, only files created after now - abs(value) will match;
                          if > 0, only files created before now - value will match

all arguments except path are optional.

Same syntax is for File.Count, which will return number of files instead of size.

Best regards,
Victor

Hi,

it seems one of the most mysterious bugs we've ever encounter. I've done load tests with lot of alarm generation and termination, and system works as expected. Seems it is some rare combination of events and/or environment. Is it possible to get remote access to your system to debug it in place? Alternatively, can you try to get core dump after crash (most likely it will note be generated by default, you'll have to enable it with ulimit) and sent to us along with compiled binaries? If you run it as virtual machine and can provide a VM image it also could help us with debugging.

Best regards,
Victor

Looks like some bug either in console or server cause incorrect severity value in the rule, and then this severity was copied into all matching alarms. I'll do additional source code checks to find out the root cause. But your configuration should be good now.

Best regards,
Victor

Hi,

I think yes, it should be very simple change.

Best regards,
Victor

Hi!

can you please provide full valgrind log (assuming there are more records then you post already)? Those errors logged looks like consequences of some memory corruption that happened before.

Best regards,
Victor

Yes, actually actions in object tools does not support parameters. Entire string interpreted as action name. I'll register this as a bug.

Best regards,
Victor

Additional subnets can be visible if you have nodes with interfaces in both allowed and disallowed subnets. NetXMS will create subnet object for each interface. It is not related to network discovery - same rules work when you add nodes manually. If you absolutely dislike those subnets, you can create configuration poll hook script that will remove unwanted subnet objects right after creation.

Best regards,
Victor

Чтобы удалить все узлы и собранные данные, надо:

1. Удалить все таблицы с названиями, начинающимися на idata_ и tdata_.

2. Очистить таблицы:

nodes
subnets
interfaces
nsmap
object_custom_attributes
network_services
dct_node_map
trusted_nodes
items
dc_tables
dc_table_columns
dct_column_names
dct_thresholds
dct_threshold_conditions
dci_schedules
raw_dci_values
event_log
thresholds
alarms
alarm_notes
alarm_events
syslog
snmp_trap_log

Возможно еще некоторые таблицы, зависит от того, какие типы объектов использовались. После этого надо запустить проверку базы:

nxdbmgr check

Но самое надежное это пересоздать базу, сделав предварительно экспорт шаблонов и правил, а затем импорт в чистую базу.

Во всех трех дампах исполнялся код, связанный с обновлением списка алармов. Насколько много активных алармов и как часто они меняются?

Maybe idea to match messages based on hostname field was initially wrong and we should just revert to matching by source IP (or at least give IP based matching higher priority)?

Best regards,
Victor

Hi,

can you please show how rule number 37 in event processing policy looks like?

Best regards,
Victor