NetXMS Support Forum

Hi,

please check object ID for MAINCR_GSX (you can find it on overview tab), then run the following command on NetXMS server command line:

nxadm -c "show topology <id>"

(replace <id> with actual node ID) and post it's output.

Best regards,
Victor

Hi,

what is your idata writer queue size? You can check it in server debug console with command "show queue". If you have historical graph for idata queue please also share it.
Also, how many DCIs you have? You can check it in server debug console with command "show stats".

Best regards,
Victor

Hi,

looks like server is locked on sending object updates to one of user sessions. We encounter same issue in another installation recently and already changed object update notification mechanism in current development branch, so there are good chance that upgrade to 2.2.9 will fix your issue.

Best regards,
Victor

Hi,

load on thread pool MAIN is definitely not normal. Could you please capture thread stack traces using attached script (you will need gdb installed)?

Best regards,
Victor

I was able to reproduce this issue. It is fixed in development branch and fix will be included into next release.

Best regards,
Victor

Hi,

could you please provide all steps to reproduce server crash? Or provide crash dump of the server?

Best regards,
Victor

Hi,

I don't think that currently it is possible without direct DB write. I can make an easy change to PushDCIData function to accept timestamp (or create separate function) to make such transformations possible.

Best regards,
Victor

Looks like you have MIB called AT-SMI-MIB missing. Check that you have MIB file with .txt extension starting with

AT-SMI-MIB DEFINITIONS ::= BEGIN

Best regards,
Victor

Добавим - скорее всего не в виде встроенной карты, а показа маркера в навигационном приложении по умолчанию. Сейчас есть функция "navigate to" для нод с выставленноми координатами.

Hi,

it's not possible yet.

Best regards,
Victor

Hi,

it's problem with reading data from database, not with storing. It is caused by bug in MariaDB client library https://jira.mariadb.org/browse/CONC-281. It is supposed to be fixed in latest client version, but could be not. Our MariaDB driver has check for client version that activates workaround - maybe it erroneously assumes version number where this issue was fixed. You can try to find the following lines in src/db/dbdrv/mariadb/mariadb.cpp:


/* workaround for MariaDB C Connector bug CONC-281 */
if (mysql_get_client_version() < 100209)  // for any client before 10.2.9
{
    mysql_stmt_store_result(hStmt->statement);
}


and comment out version check so it will look like this:

/* workaround for MariaDB C Connector bug CONC-281 */
//if (mysql_get_client_version() < 100209)  // for any client before 10.2.9
{
    mysql_stmt_store_result(hStmt->statement);
}


then recompile MariaDB driver.

Best regards,
Victor

Hi,

currently it's not possible. Starting with 2.2.8 complete event information in XML format stored in event log table, but not yet available in UI. In next release we will provide access to that information.

Best regards,
Victor

Hi,

MIB browser will show whatever MIBs are installed in your system. If you need more AT MIBs, just install them onto the server as described and you should see them in MIB browser.

Topology displayed depends on information received from switches. If they report correct information through any standard topology MIB (LLDP, CDP, etc.) then correct topology will be displayed.

Best regards,
Victor

Hi,

Error message "Table 'metadata' already exists" suggests that you are trying to initialize same database after unsuccessful initialization attempt, so it is not possible to determine root cause. Please drop existing database, create a new one, run nxdbmgr init once, and post it's output.

Best regards,
Victor

Hi,

there could be multiple reasons for that - firewall issues, no SNMP devices within subnets (needed for passive discovery), etc. Active discovery can take long time if subnets are big. You can try to set debug level to 6 and check messages with DiscoveryPoller prefix.

Best regards,
Victor