Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#6646
General / Re: problem with development
December 09, 2009, 12:43:52 PM
You don't need command 0x0097 to read information from agent. You should use CMD_GET_PARAMETER (0x0041) and set name of the parameter to variable VID_PARAMETER (85). Agent will reply with command CMD_REQUEST_COMPLETED (0x001D). First, check variable VID_RCC (28). If it contains 0, then value of requested parameter will be in variable VID_VALUE (21). For example:

CSCPMessage msg;

msg.SetCode(CMD_GET_PARAMETER);
msg.SetId(requestId);
msg.SetVariable(VID_PARAMETER, "Agent.Version");

<send message and get response into CSCPMessage *response>

DWORD rcc = response->GetVariableLong(VID_RCC);
if (rcc == ERR_SUCCESS)
{
   char buffer[256];
   response->GetVariableStr(VID_VALUE, buffer, 256);
   // Now buffer contains value of requested parameter
}

Best regards,
Victor
#6647
General Support / Re: Not able to connect Database
December 09, 2009, 12:37:41 PM
Hi!

Try to connect to database with MySQL command line client:

mysql -h localhost -u netxms -p netxms

and check error messages.

Best regards,
Victor
#6648
Попробуйте так:

<parser>
   <file>*System</file>
   <rules>
      <rule>
         <source>Cissesrv</source>
         <id>24578</id>
      </rule>
      <rule>
         <source>Cissesrv</source>
         <id>24581</id>
      </rule>
      <rule>
         <source>Cissesrv</source>
         <match>(.*)</match>
         <event params="1">100017</event>
      </rule>
   </rules>
</parser>
#6649
Добрый день!

Настройками этого добиться нельзя, надо исправлять консоль. Постараюсь сделать к следующему релизу.
#6650
DCI LogWatch.Parser.xxx ne rabotajut poka. A v buduschem nado budet ukazivat' imja parsera (konfiguracionnogo faila).
#6651
Hi!

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

Best regards,
Victor
#6652
Hi!

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

Best regards,
Victor
#6653
General Support / Re: Timeout of web login
December 02, 2009, 11:04:35 PM
Attached.

Best regards,
Victor
#6654
General Support / Re: Alarm viewer and some questions
December 02, 2009, 01:29:24 AM
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
#6655
General Support / Re: Timeout of web login
December 02, 2009, 01:27:02 AM
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
#6656
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.
#6657
Zamenite src/server/core/netinfo.cpp na prilozennij. Dolzno pomoch'.
#6658
General / Re: problem with development
December 01, 2009, 11:46:48 AM
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
#6659
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
#6660
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