News:

We really need your input in this questionnaire

Main Menu
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

#5326
Hi!

I have found a system where I was able to reproduce this problem. And yes, it was solved by switching to non-blocking sockets for client connections. I made necessary changes in svn trunk, and version 1.2.2 will contain this fix. Changes are minimal - see diff below:


Modified: trunk/src/server/core/client.cpp

===================================================================

--- trunk/src/server/core/client.cpp  2012-06-20 17:39:09 UTC (rev 6534)

+++ trunk/src/server/core/client.cpp  2012-06-20 20:25:43 UTC (rev 6535)

@@ -195,6 +195,7 @@

       }



       errorCount = 0;     // Reset consecutive errors counter

+              SetSocketNonBlocking(sockClient);



       // Create new session structure and threads

       pSession = new ClientSession(sockClient, (struct sockaddr *)&servAddr);

@@ -287,6 +288,7 @@

       }



       errorCount = 0;     // Reset consecutive errors counter

+              SetSocketNonBlocking(sockClient);



       // Create new session structure and threads

       pSession = new ClientSession(sockClient, (struct sockaddr *)&servAddr);



Modified: trunk/src/server/core/session.cpp

===================================================================

--- trunk/src/server/core/session.cpp 2012-06-20 17:39:09 UTC (rev 6534)

+++ trunk/src/server/core/session.cpp 2012-06-20 20:25:43 UTC (rev 6535)

@@ -393,7 +393,8 @@

    {

       if ((iErr = RecvNXCPMessageEx(m_hSocket, &pRawMsg, m_pMsgBuffer, &msgBufferSize,

                                             &m_pCtx, (pDecryptionBuffer != NULL) ? &pDecryptionBuffer : NULL,

-                                                                                           INFINITE, MAX_MSG_SIZE)) <= 0) {

+                                                                                           900000, MAX_MSG_SIZE)) <= 0)  // timeout 15 minutes

+              {

          DebugPrintf(5, _T("RecvNXCPMessageEx failed (%d)"), iErr);

          break;



Best regards,
Victor
#5327
Кружочки отключаются в локальном меню object browser'а (см. скриншот) или нажатием Ctrl+F3 (Object Browser должен быть активен).
#5328
Hi!

It's not possible now. I have it in my TODO list. I know, that's really annoying :)

Best regards,
Victor
#5329
General Support / Re: Using Custom Events
June 19, 2012, 07:47:15 PM
Hi!

Implemented in 1.2.2.

Best regards,
Victor
#5330
Feature Requests / Re: SOAP/XML Polling
June 19, 2012, 05:22:15 PM
Hi!

So far we don't have such plans - we just don't have enough resources.

Best regards,
Victor
#5331
Feature Requests / Re: SNMP Trap Monitor
June 19, 2012, 05:17:14 PM
Hi!

I agree that it's needed. It's not difficult, just need to do this for every view. Added to TO-DO list :)

Best regards,
Victor
#5332
А это на любых темплейтах проишодит, или на каком-то конкретном?
#5333
Да, это известный глюк. В 1.2.2 будет поправлено.
#5334
В следующий раз попробуйте запустить

nxmc -clean

тоже может помочь.
#5335
General Support / Re: nxmc access
June 18, 2012, 01:24:14 PM
Hi!

Default login is admin and default password is netxms.

Best regards,
Victor
#5336
Hi!

You cannot exclude hosts from the poll. However, you can ignore down events in specific time interval by using appropriate filter script in event processing policy.

Best regards,
Victor
#5337
General Support / Re: About Duplicate Nodes
June 15, 2012, 12:25:47 PM
Hi!

This should be fixed already in 1.2.1. Can you try version 1.2.1?

Best regards,
Victor
#5338
General Support / Re: Is it a bug?
June 15, 2012, 12:25:09 PM
Hi!

Yes, you are absolutely right. I fixed that in a trunk.

Best regards,
Victor
#5339
Hi!

1. Did you enable zoning support globally (by setting EnableZoning server configuration parameter to 1)?

2. Did you enable built-in syslog server? Also, if you are running NetXMS server on Linux, it's built in syslog server may conflict with system's syslog server by attempting to use same UDP port 514. Check server's log on startup for errors.

Best regards,
Victor
#5340
General Support / Re: remote actions not working?
June 12, 2012, 11:14:47 PM
Hi!

You should not prefix action name with "Action:" in action configuration on server side, use just action name, VarnishReload in your case.

Best regards,
Victor