AppWorx, Dollar Universe and Sysload Community

  • Private Community

  • 1.  Has anyone seen frequent AwE-5103 Network Socket Errors?

    Posted Apr 29, 2014 09:37 AM
    This is an issue we've been seeing very freqently for a few months now.  What happens is the agents go down and the following error is written to the logfile:


    ErrorMsg: AwE-5103 network socket error 
    Details: Socket closed

    The only resolution so far has been to bounce AppWorx and Apache.  We are running AppWorx 8.0 SP10, as well as the Banner Agent.

    Has anyone seen this issue?  What was your fix?



  • 2.  Has anyone seen frequent AwE-5103 Network Socket Errors?

    Posted May 01, 2014 04:51 AM

    David

    Yes, I have.

    When we upgraded from AppWorx v7 to AM v8.0, we had this problem a lot.

    After many weeks working with support on logfiles, tweaking settings and timeout values, it was concluded that the new Java engine (replacing the old C-code) was more susceptible to period of high CPU utilisation and that no code fix was going to resolve the problem.

    Our master and primary local agent run on the same machine as our Oracle Retail ERP database and server for overnight batch processes. The application jobs that AppWorx is managing now cause AppWorx to stop responding.

    In the end, support found a script which they had used on another customer site and provided this script to us.

    It is a Unix wrapper script for the startso and stopso scripts, called startam_monitor and stopam_monitor which in turn call Perl script uc4_daemon_monitor.pl (also custom code from UC4), which stays running 24/7

    This Perl script periodically checks the status of the agents, and if finds they have stopped (which is what happens after AwE-5103), it restarts the agents. It will continue to do this if it falls over again (e.g. if CPU activity is still too high).

    While it does not fix the underlying problem, it does mean that there is no more than a 5-minute delay before the UC4 engine starts more jobs in chains/queues.

    As this script was provided by UC4 rather than written by us, and I am therefore unsure on the copyright restrictions, I would suggest you contact support and quote the info I provided here, along with our support incident #204515

    Alan



  • 3.  Has anyone seen frequent AwE-5103 Network Socket Errors?

    Posted May 05, 2014 11:44 AM

    An incident has been opened with Automic Support regarding this issue.  After it has been resolved the answer will be posted here as well.



  • 4.  Has anyone seen frequent AwE-5103 Network Socket Errors?

    Posted Aug 11, 2014 09:57 AM

    The monitor script in that post was provided as a band-aid and did not resolve any problems.  Depending on the nature of the issue being experienced we may have more valid solutions.  To get an appropriate solution please open a support ticket with Automic Support.



  • 5.  Has anyone seen frequent AwE-5103 Network Socket Errors?

    Posted Feb 13, 2017 12:29 PM
    I am also experiencing the same issue while opening Appworx from local desktop, but able to open through other windows server (RDP). 
    Can anyone help?


  • 6.  Has anyone seen frequent AwE-5103 Network Socket Errors?

    Posted Feb 15, 2017 12:48 PM
    Hello Deepak,

    This thread was opened for AwE-5103 Network Socket Errors seen when an Agent goes down. However, from you description, it sounds as if you are referring to the same error resulting from opening the AM java client(GUI). Is this correct? Can you please elaborate on the issue you are experiencing?

    Do you know if there is a firewall in place that may be stopping you from opening the client, assuming this is the issue you are running into?

    regards,
    Phearith


  • 7.  Has anyone seen frequent AwE-5103 Network Socket Errors?

    Posted Jun 02, 2017 09:14 AM
    Phearith Mao said:
    Hello Deepak,

    This thread was opened for AwE-5103 Network Socket Errors seen when an Agent goes down. However, from you description, it sounds as if you are referring to the same error resulting from opening the AM java client(GUI). Is this correct? Can you please elaborate on the issue you are experiencing?

    Do you know if there is a firewall in place that may be stopping you from opening the client, assuming this is the issue you are running into?

    regards,
    Phearith
    If we need to open a new thread, please do so, but I am getting this error when opening the GUI client which does seem odd because normally I see it when an agent is not responsive. Please help. Thanks!