Text only | Text with Images

NetXMS Support Forum

English Support => General Support => Topic started by: bdefloo on February 05, 2014, 12:50:14 PM

Title: Request timed out
Post by: bdefloo on February 05, 2014, 12:50:14 PM
Hi,

Since upgrading to v1.2.11 I've been getting more "Request timed out" errors in the management console when doing various changes. (applying templates, creating a container, moving nodes, ...)

It doesn't always happen, andsometimes the operation goes through anyway, other times I have to do it again or it only succeeds partially (eg 3 out of 20 nodes are in the template, the others aren't)

Has something changed that could be causing resource locks or delays?

Thanks!

Kind regards,
bdefloo
Title: Re: Request timed out
Post by: possamai on February 05, 2014, 05:32:26 PM
same here.. it queues the request and finally it times out..
Title: Re: Request timed out
Post by: Victor Kirhenshtein on February 05, 2014, 05:53:22 PM
What database you are using?

Best regards,
Victor
Title: Re: Request timed out
Post by: bdefloo on February 05, 2014, 06:08:31 PM
Hi,

I have NetXMS x64 and MS SQL 2012 Express x64 on a Windows 2008 R2 server.
Title: Re: Request timed out
Post by: Marco Incalcaterra on February 05, 2014, 06:31:30 PM
Same here on Windows 2003 R2 x64 with MSSQL 2008 R2

Best regards,
Marco
Title: Re: Request timed out
Post by: ditonet on February 06, 2014, 12:59:31 AM
I noticed same problem on Win XP and SQLite database.
Usually on dashboard's charts.
Status line shows small progress bar and message 'Get DCI value for history graph' if I remember correctly.

Regards, Grzegorz.

EDIT: Forgot to mention, NetXMS ver. 1.2.11 and corrected message text.
Title: Re: Request timed out
Post by: Peter Sentveld on February 06, 2014, 09:05:24 AM
Same here. "Cannot terminate alarm: Request timed out", lots.

CentOS, mysql, NetXMS 2.11.

Regards,
  Peter.
Title: Re: Request timed out
Post by: opcenter1218 on February 12, 2014, 02:18:25 PM
Same issues as everything is describing. Whenever we try to delete more than a handful of alarms we get the error message popup but after a refresh the alarms go away. Very annoying but still functional.

Client Version: 1.2.11
Microsoft SQL Database
Title: Re: Request timed out
Post by: possamai on February 12, 2014, 04:07:08 PM
connection with the client gets completely messed up here.. I have to kill my client and reconnect a freshly started one to continue working.
Happens a lot when changing settings in Business Services as well.
Title: Re: Request timed out
Post by: Victor Kirhenshtein on February 17, 2014, 03:13:30 PM
Please try version 1.2.12. We have fixed lot of bugs here, hopefully timeout problem will be gone.

Best regards,
Victor
Title: Re: Request timed out
Post by: possamai on February 18, 2014, 01:12:52 PM
hmm.. looks like it's solved  :D
At least for me it is.
So far no more requests timed out anymore.
Title: Re: Request timed out
Post by: lindeamon on February 19, 2014, 10:55:29 AM
had this problem with 1.2.11 x64 2k8 srv and pgsql.
upgraded just now to 1.2.12, will check...
Title: Re: Request timed out
Post by: opcenter1218 on February 19, 2014, 10:39:13 PM
After upgrading to 1.2.12 we've been experiencing the issue below in management console and web portal.

"Cannot synchronize alarm list: Broken pipe
Broken pipe"

It generates the event "SYS_THREAD_HANG", Thread "Syncer Thread" is not responding

Restarting the client or refreshing the web browser clears the issue temporarily.



The previous "Request timed out" issue from 1.2.11 seems to be resolved.

Title: Re: Request timed out
Post by: mjcig on February 21, 2014, 06:53:45 PM
To add we are seeing a similar issue.. we are running 1.2.12 compiled for Linux using ODBC. The database is MS SQL 2012. With the past three releases we did not experience the management console timing out, but did see intermittent issues with the alarm browser and syncing the alarms.

With the new release 1.2.12, we are seeing the client session establish and then 15 minutes later the session time out.

Here is what the log is showing....
[21-Feb-2014 09:20:47.600] [DEBUG] [CLSN-0] Server time zone: CST-06CDT
[21-Feb-2014 09:20:48.176] [DEBUG] [CLSN-0] User [email protected] authenticated
[21-Feb-2014 09:20:51.350] [DEBUG] [CLSN-0] listLibraryImages: category=*ANY*
........
[21-Feb-2014 09:35:53.465] [DEBUG] [CLSN-0] RecvNXCPMessageEx: receive timeout
[21-Feb-2014 09:35:53.465] [DEBUG] *Locks* All locks for session 0 removed
[21-Feb-2014 09:35:53.465] [DEBUG] [CLSN-0] Session closed

Has a new feature been added to time out any client sessions after 15 minutes or based on a configuraiton that I need to review?

Appreciate the help
Title: Re: Request timed out
Post by: Victor Kirhenshtein on February 21, 2014, 09:15:27 PM
Hi!

There is hard-coded read timeout on server side, which is used to detect dead sessions. Normally it should not happen, because client sends keep-alive messages once per minute. However, there is a bug in 1.2.12 which prevents client from sending these messages, and so inactive session terminated after 15 minutes. I already fix this bug, and after 1.2.13 release problem should be gone.

Best regards,
Victor
Title: Re: Request timed out
Post by: mjcig on February 21, 2014, 09:25:30 PM
Great thanks for the quick reply.

Is the fix available in the source snapshot by chance?
Title: Re: Request timed out
Post by: Victor Kirhenshtein on February 21, 2014, 10:07:18 PM
Yes, it is available (you can get current sources by cloning git repository http://git.netxms.org/public/netxms.git and switching to branch "develop"). But it is client side change, and building console may be non-trivial task (you will need Maven for building client library and Eclispe 3.7 with right set of plugins listed in src/java/eclipse_addons.txt for building console).

Best regards,
Victor
Text only | Text with Images