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

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.
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to the Community! 

    I see the same logs on my LAB firewall running on 17.5 MR14. 

    Do you have any upstream firewall with IPS or web filtering configured on it? 

    Can you provide the last few lines of the following commands? 

    • grep -i "Response code : 200" u2d.log
    • grep -i "Response code : 500" u2d.log

    On my firewall, I see a response code 500 when the firewall cannot connect to the update server.

    Thanks,

  • adding my log lines here:

    XG v18 is behind SG.

    DEBUG     Oct 30 00:06:02 [16613]: Response code : 200
    DEBUG     Oct 30 00:19:19 [31367]: Response code : 200
    DEBUG     Oct 30 00:21:03 [1070]: Response code : 200
    DEBUG     Oct 30 00:36:04 [17494]: Response code : 200
    DEBUG     Oct 30 00:49:20 [31146]: Response code : 200
    DEBUG     Oct 30 00:51:05 [480]: Response code : 200
    DEBUG     Oct 30 01:06:06 [18291]: Response code : 200
    DEBUG     Oct 30 01:19:21 [32015]: Response code : 200
    DEBUG     Oct 30 01:21:07 [1229]: Response code : 200
    DEBUG     Oct 30 01:36:08 [16633]: Response code : 200
    DEBUG     Oct 30 01:49:21 [30204]: Response code : 200
    DEBUG     Oct 30 01:51:08 [32071]: Response code : 200
    DEBUG     Oct 30 02:06:09 [15880]: Response code : 200
    DEBUG     Oct 30 02:19:22 [29901]: Response code : 200
    DEBUG     Oct 30 02:21:10 [31892]: Response code : 200
    DEBUG     Oct 30 02:36:10 [15396]: Response code : 200
    DEBUG     Oct 30 02:49:23 [28781]: Response code : 200
    DEBUG     Oct 30 02:51:11 [30762]: Response code : 200
    DEBUG     Oct 30 03:06:12 [15108]: Response code : 200
    DEBUG     Oct 30 03:19:24 [29982]: Response code : 200
    DEBUG     Oct 30 03:21:13 [32156]: Response code : 200
    DEBUG     Oct 30 03:36:14 [16447]: Response code : 200
    DEBUG     Oct 30 03:49:25 [30428]: Response code : 200
    DEBUG     Oct 30 03:51:15 [32407]: Response code : 200
    DEBUG     Oct 30 04:01:11 [10516]: Response code : 200
    DEBUG     Oct 30 04:06:16 [16727]: Response code : 200
    DEBUG     Oct 30 04:19:26 [30670]: Response code : 200
    DEBUG     Oct 30 04:21:17 [434]: Response code : 200
    DEBUG     Oct 30 04:36:17 [17263]: Response code : 200
    DEBUG     Oct 30 04:49:27 [31262]: Response code : 200
    DEBUG     Oct 30 04:51:18 [1021]: Response code : 200
    DEBUG     Oct 30 05:06:19 [17189]: Response code : 200
    DEBUG     Oct 30 05:19:28 [31552]: Response code : 200
    DEBUG     Oct 30 05:21:20 [1029]: Response code : 200
    DEBUG     Oct 30 05:36:21 [16374]: Response code : 200
    DEBUG     Oct 30 05:49:29 [29016]: Response code : 200
    DEBUG     Oct 30 05:51:22 [30958]: Response code : 200
    DEBUG     Oct 30 06:06:22 [15020]: Response code : 200
    DEBUG     Oct 30 06:19:30 [29217]: Response code : 200
    DEBUG     Oct 30 06:21:23 [31849]: Response code : 200
    DEBUG     Oct 30 06:36:24 [16428]: Response code : 200
    DEBUG     Oct 30 06:49:30 [29875]: Response code : 200
    DEBUG     Oct 30 06:51:24 [32619]: Response code : 200
    DEBUG     Oct 30 07:01:33 [10099]: Response code : 200
    DEBUG     Oct 30 07:06:26 [15970]: Response code : 200
    DEBUG     Oct 30 07:19:30 [29655]: Response code : 200
    DEBUG     Oct 30 07:21:27 [32166]: Response code : 200
    DEBUG     Oct 30 07:36:28 [17068]: Response code : 200
    DEBUG     Oct 30 07:49:31 [300]: Response code : 200
    DEBUG     Oct 30 07:51:29 [3595]: Response code : 200
    DEBUG     Oct 30 08:06:30 [25328]: Response code : 200
    DEBUG     Oct 30 08:19:32 [7870]: Response code : 200
    DEBUG     Oct 30 08:21:31 [10197]: Response code : 200
    DEBUG     Oct 30 08:36:32 [27272]: Response code : 200
    DEBUG     Oct 30 08:49:32 [11590]: Response code : 200
    DEBUG     Oct 30 08:51:32 [14358]: Response code : 200
    DEBUG     Oct 30 09:06:34 [2462]: Response code : 200
    DEBUG     Oct 30 09:19:33 [20560]: Response code : 200
    DEBUG     Oct 30 09:21:35 [23510]: Response code : 200
    DEBUG     Oct 30 09:31:36 [4234]: Response code : 200
    DEBUG     Oct 30 09:36:36 [10723]: Response code : 200
    DEBUG     Oct 30 09:49:33 [27430]: Response code : 200
    DEBUG     Oct 30 09:51:37 [30424]: Response code : 200
    DEBUG     Oct 30 10:06:38 [18443]: Response code : 200
    DEBUG     Oct 30 10:19:33 [2595]: Response code : 200
    DEBUG     Oct 30 10:21:39 [5462]: Response code : 200
    DEBUG     Oct 30 10:36:39 [24977]: Response code : 200
    DEBUG     Oct 30 10:49:34 [9744]: Response code : 200
    DEBUG     Oct 30 10:51:40 [12784]: Response code : 200
    DEBUG     Oct 30 11:06:41 [1314]: Response code : 200
    DEBUG     Oct 30 11:19:34 [20785]: Response code : 200
    DEBUG     Oct 30 11:21:42 [23397]: Response code : 200
    DEBUG     Oct 30 11:36:43 [10597]: Response code : 200
    DEBUG     Oct 30 11:49:34 [28632]: Response code : 200
    DEBUG     Oct 30 11:51:44 [31561]: Response code : 200
    DEBUG     Oct 30 12:06:45 [20203]: Response code : 200
    DEBUG     Oct 30 12:19:35 [5309]: Response code : 200
    DEBUG     Oct 30 12:21:46 [8332]: Response code : 200
    DEBUG     Oct 30 12:36:47 [28999]: Response code : 200
    DEBUG     Oct 30 12:49:36 [13929]: Response code : 200
    DEBUG     Oct 30 12:51:48 [16822]: Response code : 200
    DEBUG     Oct 30 13:06:49 [4142]: Response code : 200
    DEBUG     Oct 30 13:19:37 [21187]: Response code : 200
    DEBUG     Oct 30 13:21:50 [23859]: Response code : 200
    DEBUG     Oct 30 13:36:51 [10623]: Response code : 200

    DEBUG     Oct 30 00:01:09 [9968]: Response code : 500
    DEBUG     Oct 30 00:31:27 [12606]: Response code : 500
    DEBUG     Oct 30 01:01:18 [12483]: Response code : 500
    DEBUG     Oct 30 01:31:19 [11512]: Response code : 500
    DEBUG     Oct 30 02:01:03 [10156]: Response code : 500
    DEBUG     Oct 30 02:31:05 [9737]: Response code : 500
    DEBUG     Oct 30 03:01:27 [9146]: Response code : 500
    DEBUG     Oct 30 03:31:10 [10625]: Response code : 500
    DEBUG     Oct 30 04:31:37 [11337]: Response code : 500
    DEBUG     Oct 30 05:01:06 [11178]: Response code : 500
    DEBUG     Oct 30 05:31:04 [10540]: Response code : 500
    DEBUG     Oct 30 06:01:07 [8902]: Response code : 500
    DEBUG     Oct 30 06:31:21 [10711]: Response code : 500
    DEBUG     Oct 30 07:31:15 [10700]: Response code : 500
    DEBUG     Oct 30 08:01:22 [17748]: Response code : 500
    DEBUG     Oct 30 08:31:06 [21296]: Response code : 500
    DEBUG     Oct 30 09:01:07 [27622]: Response code : 500
    DEBUG     Oct 30 10:01:36 [11730]: Response code : 500
    DEBUG     Oct 30 10:31:16 [18278]: Response code : 500
    DEBUG     Oct 30 11:01:19 [25882]: Response code : 500
    DEBUG     Oct 30 11:31:12 [3602]: Response code : 500
    DEBUG     Oct 30 12:01:23 [12427]: Response code : 500
    DEBUG     Oct 30 12:31:22 [21569]: Response code : 500
    DEBUG     Oct 30 13:01:29 [29717]: Response code : 500
    DEBUG     Oct 30 13:31:34 [4114]: Response code : 500

  • Hi,

    originally I thought it is an issue fixed in v18.
    NC-58229 [Authentication] Sophos AV and Avira AV Pattern updates failing

    https://community.sophos.com/xg-firewall/b/blog/posts/xg-firewall-v18-mr3

    Yes, the XG now behind another FW, but not inspected. Just firewall. I've not noticed any DROPs in it's log.

    The statistics for October 29:
    192 - all connections
    143 - response code 200
    49   - response code 500

    So this is one problem - almost 25% connections fails.

    The second is that even if connection is sufficient, the response from servers is that there is no any update. For example Avira was updated last time on October 29, 19:30.

    ...
    Wed Oct 28 10:59:33 2020 New updated patterns are now at /content/savi_1.00/1.0.16233
    Wed Oct 28 12:15:46 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411503
    Wed Oct 28 12:16:20 2020 pt_dload_checker: New updated patterns are now at /content/geoip_1.00/2.0.002
    Wed Oct 28 12:16:30 2020 pt_dload_checker: New updated patterns are now at /content/ips_16.0/18.17.57
    Wed Oct 28 12:19:15 2020 pt_dload_checker: New updated patterns are now at /content/sslvpn_1.01/1.0.008
    Wed Oct 28 12:32:33 2020 pt_manual_install: New updated patterns are now at /content/apfw_1.00/11.0.014
    Wed Oct 28 21:10:30 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411516
    Thu Oct 29 03:28:30 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411520
    Thu Oct 29 12:31:29 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411527
    Thu Oct 29 14:02:29 2020 pt_dload_checker: New updated patterns are now at /content/savi_1.00/1.0.16237
    Thu Oct 29 14:47:29 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411528
    Thu Oct 29 15:02:30 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411529
    Thu Oct 29 15:47:30 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411530
    Thu Oct 29 16:48:31 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411531
    Thu Oct 29 16:49:11 2020 pt_dload_checker: New updated patterns are now at /content/ips_16.0/18.17.58
    Thu Oct 29 17:03:32 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411532
    Thu Oct 29 17:33:30 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411533
    Thu Oct 29 19:04:29 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411534
    Thu Oct 29 19:34:32 2020 pt_dload_checker: New updated patterns are now at /content/avira_4.00/1.0.411535
    Fri Oct 30 05:23:30 2020 pt_dload_checker: New updated patterns are now at /content/savi_1.00/1.0.16239
    END

    Thanks

  • Tomas please also read this.

    maybe it is related

  • Right, so the irregular updates seems as known problem. Thanks for reference.

  • FormerMember
    0 FormerMember in reply to Tomas Beran

    Hi ,

    This seems to be related to an ID that our support team is already investigating (NC-64992). I would suggest you create a support case and reference the ID (NC-64992) and please share your support case number with me so that I can follow up.

    Thanks,

  • Hi Patel,

    I think that there are two different issues.

    1. 500 internal server error
    I see ~25% of such responses from remote servers.

    2. signatures not updated
    Even if ~75% of connections got 200 OK response code the servers do not send the information about available update -> so update of signatures.
    This is probably the NC-64992.

  • just adding a recent log of error 500.

    DEBUG     Nov 11 16:01:27 [18790]: --serial = C4207AHxxxxxxxxxx
    DEBUG     Nov 11 16:01:27 [18790]: --deviceid = 6d848b4deb568be680axxxxxxxxxxxxxxxx
    DEBUG     Nov 11 16:01:27 [18790]: --fwversion = 18.0.1.396
    DEBUG     Nov 11 16:01:27 [18790]: --productcode = CN
    DEBUG     Nov 11 16:01:27 [18790]: --model = XG430
    DEBUG     Nov 11 16:01:27 [18790]: --vendor = WP02
    DEBUG     Nov 11 16:01:27 [18790]: --pkg_sysupdate_version = 11
    DEBUG     Nov 11 16:01:27 [18790]: Added new server : Host - eu-west-1.u2d.sophos.com., Port - 443
    DEBUG     Nov 11 16:01:27 [18790]: Added new server : Host - us-west-2.u2d.sophos.com., Port - 443
    DEBUG     Nov 11 16:01:27 [18790]: Added new server : Host - ap-northeast-1.u2d.sophos.com., Port - 443
    DEBUG     Nov 11 16:01:27 [18790]: Final query string is :
    ?&serialkey=C4207AHxxxxxxxxxx&deviceid=6d848b4deb568be680axxxxxxxxxxxxxxxx&fwversion=18.0.1.396&productcode=CN&appmodel=XG430&appvendor=WP02&useragent=SF&oem=&pkg_sysupdate_version=11
    DEBUG     Nov 11 16:01:28 [18790]: Response code : 500
    DEBUG     Nov 11 16:01:28 [18790]: Response body :
    <?xml version="1.0" encoding="iso-8859-1"?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
             "http://www.w3.org/TR/xhtml1/DTD/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>
    
    DEBUG     Nov 11 16:01:28 [18790]: Response length : 369
    ERROR     Nov 11 16:01:28 [18790]: Received invalid top level tag html, expecting Up2Date
    ERROR     Nov 11 16:01:28 [18790]: FATAL : Error in parsing response, exiting.

    last try before and next try 10 min later was OK

  • There is a case open here about this: 03331743 since 11.11.2020

    After several useless ping-pong mails* with support one is today asking for remote access. I'm excited when this will happen and what he is about to find.

    *
    11/11/2020 7:32 AM case creation
    11/12/2020 6:46 Sophos: PM My name is xxxxx xxxx and I am one of Manager’s with Sophos. I was reviewing the Case 03331743 and I sincerely apologize for the lack of progress on this. Please do help me with the best time to reach you and I’ll ensure one of our engineer connects with you at the earliest.
    11/12/2020 11:49 PM Me: sent my phone# and working hours, regardless of already written in the case.
    11/24/2020 10:36 PM Sophos: Just a quick email to see if there is an update on this case. Can you provide some information regarding any developments with the case or if the reported issue has now been resolved? (comment: seriously?)
    11/30/2020 7:44 PM ME: the issue is still happening. attached log snippets
    12/07/2020 21:45 PM Sophos: We highly recommend a live remote session should you require assistance to troubleshoot your issue. If you want to schedule a remote session with myself, could you please share your availability for live remote session in this complete week.
    
    
    

    In the meantime I found out that the issue may be related due to a timeout happening when downloading a 380MB file because it is always the same behaviour:

    DEBUG     Dec 08 13:55:45 [21381]: Received location : https://d3tusa5dvomhzy.cloudfront.net/HW/HW-18.0.3_MR-3.SF300-457.sig

    which has 381 MB (399.932.970 Bytes)

    DEBUG     Dec 08 14:01:10 [29517]: Added new server : Host - eu-west-1.u2d.sophos.com., Port - 443
    DEBUG     Dec 08 14:01:10 [29517]: Added new server : Host - us-west-2.u2d.sophos.com., Port - 443
    DEBUG     Dec 08 14:01:10 [29517]: Added new server : Host - ap-northeast-1.u2d.sophos.com., Port - 443
    DEBUG     Dec 08 14:01:10 [29517]: Final query string is :
    ?&serialkey=xxxxxxxxxx&deviceid=xxxxxxxxxxxxx&fwversion=18.0.1.396&productcode=CN&appmodel=XG430&appvendor=WP02&useragent=SF&oem=&pkg_sysupdate_version=11

    Followed by the error 500
    DEBUG     Dec 08 14:01:10 [29517]: Response code : 500

    500 - Internal Server Error

    ERROR     Dec 08 14:01:10 [29517]: Received invalid top level tag html, expecting Up2Date
    ERROR     Dec 08 14:01:10 [29517]: FATAL : Error in parsing response, exiting.

    Issue is happening regularly every 30 minutes now will let a tcpdump run next time to see the actual URL thats beiing accessed

    Line 267856: DEBUG     Dec 07 00:01:21 [28475]: Response code : 500
    Line 268129: DEBUG     Dec 07 00:31:05 [11219]: Response code : 500
    Line 268340: DEBUG     Dec 07 01:01:07 [23335]: Response code : 500
    Line 268551: DEBUG     Dec 07 01:31:19 [2994]: Response code : 500
    Line 268762: DEBUG     Dec 07 02:01:29 [14308]: Response code : 500
    Line 268973: DEBUG     Dec 07 02:31:30 [25316]: Response code : 500
    Line 269184: DEBUG     Dec 07 03:01:15 [3722]: Response code : 500
    Line 269395: DEBUG     Dec 07 03:31:05 [13987]: Response code : 500
    Line 269668: DEBUG     Dec 07 04:01:20 [25615]: Response code : 500
    Line 269910: DEBUG     Dec 07 04:31:10 [3462]: Response code : 500
    Line 270121: DEBUG     Dec 07 05:01:10 [14014]: Response code : 500
    Line 270332: DEBUG     Dec 07 05:31:39 [25225]: Response code : 500
    Line 270543: DEBUG     Dec 07 06:01:04 [3833]: Response code : 500
    Line 270754: DEBUG     Dec 07 06:31:19 [18814]: Response code : 500
    Line 270965: DEBUG     Dec 07 07:01:05 [29434]: Response code : 500
    Line 271238: DEBUG     Dec 07 07:31:26 [10069]: Response code : 500
    Line 271449: DEBUG     Dec 07 08:01:27 [22041]: Response code : 500
    Line 271660: DEBUG     Dec 07 08:31:33 [10273]: Response code : 500
    Line 271902: DEBUG     Dec 07 09:01:03 [1163]: Response code : 500
    Line 272113: DEBUG     Dec 07 09:31:07 [29410]: Response code : 500
    Line 272324: DEBUG     Dec 07 10:01:06 [24461]: Response code : 500
    Line 272535: DEBUG     Dec 07 10:31:10 [17562]: Response code : 500
    Line 272806: DEBUG     Dec 07 11:01:10 [16643]: Response code : 500
    Line 273048: DEBUG     Dec 07 11:31:15 [19218]: Response code : 500
    Line 273290: DEBUG     Dec 07 12:01:26 [13690]: Response code : 500
    Line 273532: DEBUG     Dec 07 12:31:02 [6477]: Response code : 500
    Line 273774: DEBUG     Dec 07 13:01:06 [31070]: Response code : 500
    Line 274016: DEBUG     Dec 07 13:31:24 [23044]: Response code : 500
    Line 274227: DEBUG     Dec 07 14:01:12 [14938]: Response code : 500
    Line 274438: DEBUG     Dec 07 14:31:16 [5401]: Response code : 500
    Line 274649: DEBUG     Dec 07 15:01:17 [29776]: Response code : 500
    Line 274860: DEBUG     Dec 07 15:31:07 [23001]: Response code : 500
    Line 275102: DEBUG     Dec 07 16:01:24 [15599]: Response code : 500
    Line 275313: DEBUG     Dec 07 16:31:32 [2538]: Response code : 500
    Line 275524: DEBUG     Dec 07 17:01:16 [21825]: Response code : 500
    Line 275735: DEBUG     Dec 07 17:31:18 [2331]: Response code : 500
    Line 276006: DEBUG     Dec 07 18:01:04 [15035]: Response code : 500
    Line 276217: DEBUG     Dec 07 18:31:18 [25311]: Response code : 500
    Line 276428: DEBUG     Dec 07 19:01:25 [322]: Response code : 500
    Line 276868: DEBUG     Dec 07 20:01:27 [13090]: Response code : 500
    Line 277079: DEBUG     Dec 07 20:31:39 [18078]: Response code : 500
    Line 277290: DEBUG     Dec 07 21:01:01 [22800]: Response code : 500
    Line 277501: DEBUG     Dec 07 21:31:14 [27078]: Response code : 500
    Line 277712: DEBUG     Dec 07 22:01:15 [31768]: Response code : 500
    Line 277923: DEBUG     Dec 07 22:31:32 [4067]: Response code : 500
    Line 278134: DEBUG     Dec 07 23:01:31 [8008]: Response code : 500
    Line 278345: DEBUG     Dec 07 23:31:15 [11973]: Response code : 500
    Line 278556: DEBUG     Dec 08 00:01:01 [18441]: Response code : 500
    Line 278798: DEBUG     Dec 08 00:31:05 [24050]: Response code : 500
    Line 279040: DEBUG     Dec 08 01:01:06 [29495]: Response code : 500
    Line 279511: DEBUG     Dec 08 02:01:28 [7297]: Response code : 500
    Line 279722: DEBUG     Dec 08 02:31:33 [12902]: Response code : 500
    Line 279933: DEBUG     Dec 08 03:01:15 [17085]: Response code : 500
    Line 280144: DEBUG     Dec 08 03:31:36 [21530]: Response code : 500
    Line 280355: DEBUG     Dec 08 04:01:10 [23939]: Response code : 500
    Line 280566: DEBUG     Dec 08 04:31:07 [27678]: Response code : 500
    Line 280777: DEBUG     Dec 08 05:01:29 [31835]: Response code : 500
    Line 280988: DEBUG     Dec 08 05:31:16 [4278]: Response code : 500
    Line 281199: DEBUG     Dec 08 06:01:05 [8504]: Response code : 500
    Line 281410: DEBUG     Dec 08 06:31:23 [13632]: Response code : 500
    Line 281652: DEBUG     Dec 08 07:01:23 [19441]: Response code : 500
    Line 281894: DEBUG     Dec 08 07:31:18 [24947]: Response code : 500
    Line 282105: DEBUG     Dec 08 08:01:28 [32531]: Response code : 500
    Line 282316: DEBUG     Dec 08 08:31:18 [12045]: Response code : 500
    Line 282527: DEBUG     Dec 08 09:01:20 [1652]: Response code : 500
    Line 282738: DEBUG     Dec 08 09:31:05 [25643]: Response code : 500
    Line 283009: DEBUG     Dec 08 10:01:25 [20632]: Response code : 500
    Line 283251: DEBUG     Dec 08 10:31:11 [8139]: Response code : 500
    Line 283462: DEBUG     Dec 08 11:01:30 [27757]: Response code : 500
    Line 283673: DEBUG     Dec 08 11:31:30 [10791]: Response code : 500
    Line 283884: DEBUG     Dec 08 12:01:25 [2672]: Response code : 500
    Line 284417: DEBUG     Dec 08 13:01:21 [2635]: Response code : 500
    Line 284628: DEBUG     Dec 08 13:31:11 [15625]: Response code : 500
    Line 284839: DEBUG     Dec 08 14:01:10 [29517]: Response code : 500
    

    update: URL cannot be seen as this is SSL traffic. At least the sessions to the Sophos AWS cloud servers were all OK without errors.

  • I have similar output, 500 error code each half a hour or 1 hour.

    Anyway the own signatures updates had improved a much and works better now without any change on my side.
    Occasionally some updates are missed, but in general OK.

    But unfortunately now the last update I have is from yesterday after 4pm.

    So I would guess they have some issue with servers as the behavior improved and now updates stopped for some time.
    Plus still 500 errors. Hmmm ...