NetXMS Support Forum

DCI LogWatch.Parser.xxx ne rabotajut poka. A v buduschem nado budet ukazivat' imja parsera (konfiguracionnogo faila).

Hi!

It seems that I have fixed the problem. Attached is logwatch.nsm for Windows x64. Could you please try it?

Best regards,
Victor

Hi!

Could you please post your parser configuration file? It may be just one rule which is not working.

Best regards,
Victor

Attached.

Best regards,
Victor

Hello!

For now, I have patched nxhttpd so "Alarms" page in web UI refreshes periodically. See this topic: https://www.netxms.org/forum/index.php/topic,780.msg3676.html#msg3676.

Best regards,
Victor

Hello!

I have patchet nxhttpd so "Alarms" page will refresh automatically every 15 seconds, and so session should not timeout. Replace file src/nxhttpd/alarm.cpp with attached one and recompile. Let me know if you need recompiled Windows binary of nxhttpd.
Hope this helps!

Best regards,
Victor

A pochemu v pervom sluchae bil katalog netxms-0.2.31, a vo vtorom - netxms-0.2.27? Ja patch delal dlja versii 0.2.31.

Zamenite src/server/core/netinfo.cpp na prilozennij. Dolzno pomoch'.

In general, steps are following:

1. create CSCPMessage object
2. fill it with necessary variables and set correct command code
3. create raw message (CSCP_MESSAGE) vith CSCPMessage::CreateMessage method
4. send raw message to agent as usual
5. receive response using RecvNXCPMessage function
6. create CSCPMessage object from received raw message
7. read variables from message object

Best regards,
Victor

Hi!

It's really difficult to estimate release time for this feature. We start working on it some time ago (it's called "zoning" in NetXMS), but then development was suspended. In a short time we plan to release stable version 1.0 and focus on developing 1.1 branch. This feature definitely will appear only in 1.1, if I will have enough resources - withing 6 month.

Best regards,
Victor

During some polls server may not close connection to agent gracefully, which cause this error on agent side. We will fix this in next version. For now, you can safely ignore these errors.

Best regards,
Victor

Yes, it could be encrypted, and in that case you should provide correct encryption context. However, if you are not using encryption, you can simple pass NULL.

Best regards,
Victor

CSCP is an old name for NXCP, and it's partially replaces in the code. In latest versions, there are no RecvCSCPMessage() function, only RecvNXCPMessage() - but it's the same function anyway.

Best regards,
Victor

Явно выраженного перекоса в сторону одной из таблиц нет. Можно почистить event log, но это всего лишь 34MB, не думаю что это решит проблему. Попробуйте включить slow query log в MySQL (http://dev.mysql.com/doc/refman/5.1/en/slow-query-log.html) - попробуем посмотреть, какие именно запросы тормозят, и будем их оптимизировать.

Hi!

You should create CSCPMessage object from CSCP_MESSAGE structure filled by RecvNXCPMessage function. After that, you can access to variables inside message via GetVariableXxx methods of class CSCPMessage. If you getting parameter's value from agent, you should be interested in variables VID_RCC - DWORD holding response code, and VID_VALUE - received value as string.

Best regards,
Victor