Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 32 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 5282 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Update - internal server error

Tomas Beran

Hi all,

just curious if anyone noticed the behavior below. Many times I can see error below in /log/u2d.log:

DEBUG Oct 30 10:01:07 [7784]: Response body :
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"">www.w3.org/.../xhtml1-transitional.dtd">
<html xmlns="">http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>500 - Internal Server Error</title>
</head>
<body>
<h1>500 - Internal Server Error</h1>
</body>
</html>

Observation:

- on v17.5.13 it was about 50% of requests

- on v18.0.3 it is about 25% of all requests

Majority of incidents looks like:
DEBUG Oct 29 17:01:16 [6703]: --pkg_sysupdate_version = 2
DEBUG Oct 29 17:01:16 [6703]: Added new server : Host - eu-west-1.u2d.sophos.com., Port - 443
DEBUG Oct 29 17:01:16 [6703]: Added new server : Host - us-west-2.u2d.sophos.com., Port - 443
DEBUG Oct 29 17:01:16 [6703]: Added new server : Host - ap-northeast-1.u2d.sophos.com., Port - 443
DEBUG Oct 29 17:01:16 [6703]: Final query string is :
?&serialkey=XXXXX&deviceid=XXXXXX&fwversion=18.0.3.457&productcode=CN&appmodel=SF01V&appvendor=SO01&useragent=SF&oem=&pkg_sysupdate_version=2
DEBUG Oct 29 17:01:16 [6703]: Response code : 500

Do you see something similar or it just my problem with my installation?



This thread was automatically locked due to age.
  • 0 in reply to LHerzog

    XG is von 18 MR5 now. The errors remain but still change.

    Error 500 gone since April 15th

    Error 503 still very frequent - looks like 500 has only been replaced by 503

    Error 504 seems to have gone - last hit was on May 2nd

    XG430_WP02_SFOS 18.0.5 MR-5-Build586# grep "Response code : 500" /log/u2d.log | tail -5
DEBUG     Apr 15 14:01:15 [18754]: Response code : 500
DEBUG     Apr 15 15:31:22 [20569]: Response code : 500
DEBUG     Apr 15 16:01:10 [12279]: Response code : 500
DEBUG     Apr 15 16:31:12 [4451]: Response code : 500
DEBUG     Apr 15 17:31:17 [5846]: Response code : 500

XG430_WP02_SFOS 18.0.5 MR-5-Build586# grep "Response code : 503" /log/u2d.log | tail -5
DEBUG     May 13 17:01:24 [24024]: Response code : 503
DEBUG     May 13 23:31:27 [28909]: Response code : 503
DEBUG     May 14 05:01:32 [19773]: Response code : 503
DEBUG     May 14 06:01:30 [4707]: Response code : 503
DEBUG     May 14 09:01:32 [19482]: Response code : 503

XG430_WP02_SFOS 18.0.5 MR-5-Build586# grep "Response code : 504" /log/u2d.log | tail -5
DEBUG     Apr 29 11:01:23 [12079]: Response code : 504
DEBUG     Apr 29 12:01:40 [29693]: Response code : 504
DEBUG     Apr 29 12:31:37 [21336]: Response code : 504
DEBUG     Apr 29 13:01:33 [8856]: Response code : 504
DEBUG     May 02 08:01:10 [12940]: Response code : 504

  • 0 in reply to LHerzog_Central

    Support closed our support case and reported this as known issue without plans to fix.

    Development reference number:

    NC-68836

    Current Status:

    Closed

    Issue type:

    Defect

    The issue has been reviewed by our development team and unfortunately we do not have any plans to fix it in the foreseeable future. Therefore, we will be archiving your case at this time.

    At the moment the recommended settings should be kept at default i.e. 2 hours. The pattern update does not update several times in a day and the AV is getting updated every day. So once in a day would also suffice.

    My comments here:

    AV Update is not an issue. Though the errors in the log remain, even with the lowered pattern update frequency from 15 min to 120 min. So I just reverted it to our desired value of 15 min.

    I guess the Cloud Servers are just responding with errors on a regular basis and the reason is unknown.