Hi all, an help!
If I test a my table query with nxget.exe with this command:
nxget.exe -l ipmymachine -T -w 30 query_test
I have this result:
Received too large message CMD_REQUEST_COMPLETED (15703016 bytes)
408: Request timeout
It's possible to increase the message limit?
thanks,
Claudio.
Anybody can help me?! Victor?! ::)
Many thanks Victor! You are very kind! 
ok there were two problem, the first was the timeout to 4000 ms, my query use 8 seconds for work, but there is another problem:
My query return to much data for the agent: 150 rows.
If I use top 20 rows, it works but I need the real result..
Now with the agent in cmd (and the AgentCommandTimeout for test setted to 90000 ms) I have this log (after 1min and 1 sec from the table query request):
Session disconnected by timeout (last activity timeout is ....)
If I test my query with nxget.exe with this command:
nxget.exe -l ipmymachine -T -w 30 query_test
I have this result:
Received too large message CMD_REQUEST_COMPLETED (15703016 bytes)
408: Request timeout
It's possible to increase the message limit?
thanks,
Claudio.
the log (name of query and ip are fictional):
can somebady help me? very thanks!!
[13-Apr-2016 09:45:28.649] [session:6] Requesting table "query_test1"
[13-Apr-2016 09:45:32.643] [session:6] Message receiving error (MSGRECV_CLOSED)
[13-Apr-2016 09:45:32.643] Incoming connection from 192.168.7.1
[13-Apr-2016 09:45:32.643] Connection from 192.168.7.1 accepted
[13-Apr-2016 09:45:32.659] [session:7] Server ID set to 2B865D6C80000D2D
[13-Apr-2016 09:45:32.659] 0 SNMP targets received from server 2B865D6C80000D2D
[13-Apr-2016 09:45:32.659] 0 data collection elements received from server 2B865
D6C80000D2D
[13-Apr-2016 09:45:32.659] Data collection for server 2B865D6C80000D2D reconfigu
red
[13-Apr-2016 09:45:32.659] [session:7] Requesting table "query_test1"
[13-Apr-2016 09:45:33.548] [session:0] Session with 192.168.7.1 closed
[13-Apr-2016 09:45:36.653] [session:7] Message receiving error (MSGRECV_CLOSED)
[13-Apr-2016 09:45:36.653] Incoming connection from 192.168.7.1
[13-Apr-2016 09:45:36.653] Connection from 192.168.7.1 accepted
[13-Apr-2016 09:45:36.668] [session:0] Server ID set to 2B865D6C80000D2D
[13-Apr-2016 09:45:36.668] 0 SNMP targets received from server 2B865D6C80000D2D
[13-Apr-2016 09:45:36.668] 0 data collection elements received from server 2B865
D6C80000D2D
[13-Apr-2016 09:45:36.668] Data collection for server 2B865D6C80000D2D reconfigu
red
[13-Apr-2016 09:45:36.668] [session:0] Requesting table "query_test1"
[13-Apr-2016 09:45:37.011] [session:6] Session with 192.168.7.1 closed
[13-Apr-2016 09:45:37.105] [session:1] Session with 192.168.7.1 closed
[13-Apr-2016 09:45:40.662] [session:0] Message receiving error (MSGRECV_CLOSED)
[13-Apr-2016 09:45:40.662] Incoming connection from 192.168.7.1
[13-Apr-2016 09:45:40.662] Connection from 192.168.7.1 accepted
[13-Apr-2016 09:45:40.662] [session:1] Server ID set to 2B865D6C80000D2D
[13-Apr-2016 09:45:40.678] 0 SNMP targets received from server 2B865D6C80000D2D
[13-Apr-2016 09:45:40.678] 0 data collection elements received from server 2B865
D6C80000D2D
[13-Apr-2016 09:45:40.678] Data collection for server 2B865D6C80000D2D reconfigu
red
[13-Apr-2016 09:45:40.678] [session:1] Requesting parameter "query_test2"
[13-Apr-2016 09:45:44.671] [session:1] Message receiving error (MSGRECV_CLOSED)
Hi, I updated netxms to 2.0.3 version but the problem is the same..
I lose the result of DCI TABLE query, not for all my queries but for a query that return a lot of rows as result ( es. 150 rows)
Not ever, but too often, the result data are not reliable.
I start the agent in cmd command with the log at 5 level and I could see that the agent request the query but the result is an error:
MSGRECV_CLOSED
and the result list of the query table is empty.
Hi all,
I have a Table DCI, when the result is with more than ..for example 150 rows, the agent can't recover the data, it retries the operation with the same result and at the end, the agent restarts itself and after it jumps the dci table.
This with the netxms 1.7 version, you know if this problem it's resolved with the 2.3 version?
Thanks a lot!
Claudio.
Thank you Alex, after a lot of days during which I tried it, I can tell that it works fine!
Claudio.
Thank you so mutch!!!
I try it!
Hi all,
Sometimes, my DCI probe stops to communicate, (not writes history and accordingly doesn't catch events and alarms...).
If I restart the relative agent it comes back to write history. Depends on what?
Now the IMPORTANT question: How can I monitoring the stop of a DCI probe, throwing an alert?
There is another probe for this? or a threshold script to use in the original probe?
Thanks,
Claudio.
Hi all! I think no, but it is possible to have a table of tables in a dashboard?
(A table for each row)
Thanks,
Claudio.
Yes it does!!
(seem my words!!!)
Thanks so much multix!!
(I'm sorry if I didn't find the link by myself but I have tried without results! many many thanks)
Ok, many tanks tomaskir!
Claudio.
Hi, in the netxms-2.0-RC1(Windows 64) version, the Legacy NetXMS Console (NetXMS\bin\nxcon.exe) is not present right? it is expected in the future?
thanks,
Claudio.
Hi all! any news?! ::)
thanks a lot!
Hi!
It's possible to filter an event and relative alarm and action in event processing, by the time of the event?
I mean:
I want to catch an activation event for a service down in the event processing policy and send a mail as server action and it is easy, but I want that the alarm is not start and so the mail doesn't send in the night, when the service is put down by scheduler task.
It is possible? and how? (in the filtering section? by a script? if yes, how?)
Many thanks!
Claudio.
Yeah! very thanks Victor!
I will do the upgrade in few days.
Claudio
Hi Victor! Thanks a lot for the reply!
I tryed with your method, I did all but at the last I discovered a problem! the PushDCIData is Since: 2.0-M1 and I have the 1.17 version!!
There is a older(similar) PushDCIData function that I can use in the 1.17 version?
I will change to the 2.0, but not in these days...
I solved updating situations in the action and creating a DCI with read it and do trasformation script, but the PushDCIData is very util for a lot of application, It help me in the 1.17 version...
For the future...in the past I updated my system from the 1.16 to the 1.17 version and it was very easy, from the 1.17 to 2.0 is similar or more difficult? the operations to do are the same?
Thanks,
Claudio.
Hi, I know how to do a log parser and catch the first or other parameters in the event message, but I need to know how use the parameter (%1) of the log parser in a chart in a dashboard.
First: is possible? and how?
Thankyou!!!
Yeah It works!
I installed the Ms SQL 2008 Native Client in another node(for safety not in the same with the 2012 client) and the query works fine!
I look forward for the 2.0-M1 agent and in the meantime I thankyou!
Any update of this please?
