NetXMS Support Forum

Hi!

Can you ensure that core dump is generated, and provide me with crash backtrace? You can get backtrace from codedump by running

gdb netxmsd core

(replace netxmsd and core with actual path to netxmsd binary and core file)

then at (gdb) prompt enter

bt

Best regards,
Victor

Hi!

seems that for some reason one of the data collection tables was not created. Try to create it manually as following:

CREATE TABLE idata_360 (item_id integer not null,idata_timestamp integer not null,idata_value varchar(255) null);

Then create index on it. Depending on your database:

PostgreSQL:

CREATE INDEX idx_idata_360_timestamp_id ON idata_360(idata_timestamp,item_id);


MS SQL:

CREATE CLUSTERED INDEX idx_idata_360_id_timestamp ON idata_360(item_id,idata_timestamp);

Other databases:

CREATE INDEX idx_idata_360_id_timestamp ON idata_360(item_id,idata_timestamp);

Best regards,
Victor

Hi!

I cannot reproduce this problem. Just build test setup with two servers and they are able to forward events. Can you please provide appropriate parts from logs of both servers running at debug level 6? Also, what is exact versions and platforms for those two servers?

Best regards,
Victor

Несколько получателей можно давать, разделяются точкой с запятой.

По отсылке писем на группу - идея хорошая, я добавлю.

Поскольку Ping3 не дает информацию о статусе интерфейса через SNMP, NetXMS использует ICMP ping. По логам видно, что используется прокси - проверьте, что там загружен субагент ping.nsm.

Hi!

config.log may help. You can send it to [email protected]. Now I suspect problems with iconv on your server. Java console and our network communication protocol uses UCS-2, but native wide characters for Linux is UCS-4, so we use iconv for UCS-2/UCS-4 conversion.

Best regards,
Victor

I just build new test server with fresh PostgreSQL database, and everything seems to work. My DB settings are like yours:

root@debian7-x64:~/netxms# psql -h 127.0.0.1 -U netxms
Password for user netxms:
psql (9.1.11)
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
Type "help" for help.

netxms=> \l
                                  List of databases
   Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges   
-----------+----------+----------+-------------+-------------+-----------------------
netxms    | netxms   | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
           |          |          |             |             | postgres=CTc/postgres
template1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
           |          |          |             |             | postgres=CTc/postgres
(4 rows)

netxms=>

I enter characters with umlauts in few different places (see screenshot).

Are you sure you didn't make any mistake when installing unicode version? Also, can you check how these texts really stored in database (for example, in actions table)?

Best regards,
Victor

Hi!

What is your database settings? It is recommended to use UTF-8 encoding in PostgreSQL.

Best regards,
Victor

Hi!

You can just recompile server with UNICODE support and connect to same database. It should work just fine.

Best regards,
Victor

When you set time interval in dashboard graph properties, if it's set to "1 minute" it means "for last one minute", not "every minute". If you had setting like this, then you actually request data for last one minute, and collecting data once per minute you only got one data point in that interval - so no line was drawn.

Best regards,
Victor

Very strange. Still seems to be network problem to me, but I have to know more about actual network topology. You can contact me directly if you wish to continue debugging and don't want to share this information on the forum.

Best regards,
Victor

From screenshot it looks like chart for 1 minute (19:54:50 to 19:55:50). Is it really what you want to display? If yes, are you sure you collect data often enough?

Best regards,
Victor

Hi!

System will generate events in case anything goes wrong with the node - you can handle these events and create alarms, send notifications, etc. Most important events are following:

SYS_NODE_DOWN - entire node is down (NetXMS server cannot communicate using any allowed means)
SYS_NODE_UNREACHABLE - NetXMS server cannot communicate with the node because of intermediate router failure
SYS_NODE_UNMANAGED - someone put node into unmanaged state
SYS_NODE_UNKNOWN - status of the node is unknown
SYS_IF_DOWN - network interface is down
SYS_IF_UNKNOWN - status if network interface is unknown (usually because of disconnected agent)
SYS_IF_DISABLED - network interface was disabled
SYS_SERVICE_DOWN - network service is down
SYS_SERVICE_UNKNOWN - network service state cannot be determined (usually because of agent failure)
SYS_AGENT_UNREACHABLE - NetXMS agent is unreachable
SYS_SNMP_UNREACHABLE - SNMP agent is unreachable
SYS_DCI_UNSUPPORTED - DCI goes to "unsupported" state
SYS_SCRIPT_ERROR - NXSL script execution error
SYS_SMTP_FAILURE - server was unable to sent e-mail notification
SYS_SMS_FAILURE - server was unable to sent SMS notification

Best regards,
Victor

Добавил новый атрибут "driver" - будет доступен после обновления на 1.2.11.

From configuration poll it seems that you connected some Cisco router, not Windows machine with agent. Either you made some mistake or I didn't understand initial question correctly.

Best regards,
Victor