NetXMS Support Forum

Hi!

You should replace * with parser's name. By default parser name is file name (given in <file>), but you can override it with name attribute, like this:

<parser name="AppLog">
  <file>*Application</file>
  <rules>
    <rule>
      <severity>6</severity>
      <match>(SQL Server Scheduled Job)*(Message: The job failed)*</match>
      <event params="1">100025</event>
    </rule>
  </rules>
</parser>

and then use LogWatch.Parser.MatchedRecords(AppLog)

Best regards,
Victor

Hi!

There are new action type - "XMPP message". You can use it in a same way as SMS or email actions to send XMPP messages from event processing policy. It is also possible to execute debug console commands from XMPP-capable messenger (to do this you should map XMPP ID to user account by setting XMPP ID field in user properties, and give user "Execute commands via XMPP" right.

Best regards,
Victor

Hi all!

NetXMS version 1.2.11 is out. Changes since previous release:

- Thresholds can be defined as NXSL scripts
- XMPP messaging support
- "Do not save collected data to database" option for data collection items
- Added "follow" option to "download file" object tools
- New attribute "driver" for NXSL class "Node"
- Management console:
   - Stacked line charts implemented
   - Authentication by certificates supported by Java console
   - Russian translation improved
- Fixed issues: #16, #76, #385, #464, #469, #472

Best regards,
Victor

Должно быть исправлено в версии 1.2.11.

Hi!

Try to set debug level on server to 6 and watch for SMS driver messages when it sends SMS. Also, check what messages you got from SMS driver in server log on server startup.

Best regards,
Victor

Hi!

It probably should be something like this:

<match>(SQL Server Scheduled Job.*Message: The job failed.*)</match>

if you want to capture full text but match only messages with certain words in it.

Best regards,
Victor

It depends on your system. Most likely core generation is turned off, you can check it with ulimit command. If you experience crash often, you can just run netxmsd from within debugger, like this:

$ gdb /usr/local/bin/netxmsd
...
(gdb) run -D3

... it runs until crash ...

(gdb) bt

Best regards,
Victor

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