NetXMS Support Forum

From this log it seems that new node was not created. Can you remove all duplicate nodes except node with ID 100 and start server again? Also, please send me result of configuration poll for that node and output of ifconfig -a.

Best regards,
Victor

netsvc subagent need libcurl, and so it will only built if libcurl development package is installed. Try to install libcurl-devel package and run configure and make again.

Best regards,
Victor

Hi!

Yes, it could be added. Nobody requests this before

Best regards,
Victor

Hi!

Most likely server has a problem detecting interfaces of server nodes. Can you please provide information about the OS server is running on, result of configuration poll for server node, and output of server starting at debug level 7 (up to message "Server initialization completed")?

Best regards,
Victor

Hi!

Seems that both Windows and Debian packages was built with netsvc subagent omitted. I'll build both versions a bit later and post a download link.

Best regards,
Victor

So basically almost everything is working. CDP may be empty if nobody in the network sends CDP packets except that switch.

Yes, you can send dump by mail.

Best regards,
Victor

Hi!

Most of the functionality should work out of the box. Driver is needed to provide VLAN information and picture of physical ports. Ideally would be to get output of full SNMP walk (starting .1).

Best regards,
Victor

А под каким пользователем работает сервис NetXMS Core? Пользователь должен входить в группу Administrators для работы с raw сокетами.

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