x Want to participate? Join the group to interact
  • State Verified Answer
  • +3 person also asked this people also asked this
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 146 subscribers
  • Views 7672 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
211
topics
418
replies
Sage Intelligence Reporting
121
topics
322
replies
Martin King-Turner

ECONNRESET Error in Batch Server

SOLVED
Posted By

Hi,

We are on V12 Patch 22, Syracuse 12.7.6.2 and regularly (2 or 3 times per day) experiencing an error with the batch server where tasks fail with an ECONNRESET error.  If this is a recurring task, we have to manually re-start the task with the 'Follow-up recur entry' menu on the Usage->Request Management screen.  Otherwise the task never recurs.

The task log always looks like this:

The Syracuse log always contains the following error:

This error only occurs with the batch server.  User sessions are all OK.

Any ideas?

Thanks,
Martin

Parents Reply Children
  • 0 in reply to JamesG-ACD

    We installed V12 p23 last weekend, together with Syracuse 12.8.2.2, MongoDB 4.0.18 & runtime 93.1.17 and, so far, we haven't had the issue since the upgrade.  Of course, it's only 4 days ago so too early to say for sure that the problem has gone away...

    What level of Syracuse and MongoDB are you on?

  • 0 in reply to Martin King Turner

    Thanks for the reply. I have Mongo 4.0.18, and for Syracuse, I have 12.8.0 installer, and X3 reports 12.8.0.44-0.

    I downloaded the P23 files from the KB page a while back, and didn't notice when we did the update that the runtime and adxadmin had been updated. I applied the updated versions last night which ultimately didn't help. At this moment I can't access the P23 KB article at all to see if I can get 12.8.2.2.

  • 0 in reply to Martin King Turner

    I did end up installing Syracuse 18.2.2 and runtime 93.1.19, but it didn't help. Our issue seemed to be more related to the total number of runtime connections; when it got above a certain number the crashes would start. I added an additional process server as well as adding some memory to the main runtime server, and thusfar the crashes have stopped.

*Community Hub is the new name for Sage City