8 Replies Latest reply: Jan 9, 2013 6:46 AM by iain.gardiner RSS

    Connection timeouts to wpm.webwasher.com

    iain.gardiner

      Over last couple of days I have periodically been getting the following errors on my MWGs.

       

      Here's today's log from one box.

       

      [2013-01-08 00:09:40.259 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 00:40:02.763 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 01:10:25.231 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 01:40:47.723 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 02:11:10.227 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 02:41:32.735 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 03:11:55.247 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 08:13:51.871 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 08:44:14.423 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 09:14:36.987 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

      [2013-01-08 09:44:59.523 +00:00] [Coordinator] [UpdateProcessConnectUpdateServer] Error occured while sent update request to update server: 'wpm.webwasher.com' caught exception: 'COSErrException' with errorcode: '110', message:'errno: 110 - 'Connection timed out''. [CClusterUpdater::SendUpdateRequest]

       

      Does this point to an issue on my side or just McAfee server being busy?

       

      Cheers

        • 1. Re: Connection timeouts to wpm.webwasher.com
          luca.scamoni

          wpm.webwasher.com answers to 3 different IPs:

          nslookup wpm.webwasher.com

          Server:         127.0.0.1

          Address:        127.0.0.1#53

           

          Non-authoritative answer:

          Name:   wpm.webwasher.com

          Address: 217.172.176.61

          Name:   wpm.webwasher.com

          Address: 78.47.213.146

          Name:   wpm.webwasher.com

          Address: 80.237.238.80

           

          telnet 217.172.176.61 443

          Trying 217.172.176.61...

          Connected to wpm.webwasher.com (217.172.176.61).

          Escape character is '^]'.

           

          telnet 78.47.213.146 443

          Trying 78.47.213.146...

          Connected to wpm.webwasher.com (78.47.213.146).

          Escape character is '^]'.

           

          telnet 80.237.238.80 443

          Trying 80.237.238.80...

           

          So only 1 out of 3 IPs seems not to respond. I'd say its a  problem on McAfee side...

          but you could easily work around it...

          • 2. Re: Connection timeouts to wpm.webwasher.com
            asabban

            Hi Luca,

             

            you are right, one of the three servers behind wpm.webwasher.com is unreachable. The hosting company is currently analyzing what happened and is trying to restore the system. You should only see random errors, because MWG maintains a list of multiple servers and tries all of them. In your case it might be that MWG has the broken server in the list first, so it tries this one, fails, then tries another and succeeds. I am not sure if MWG remembers which server was down, but I would not be surprised if it parses the list it knows permanently.

             

            You should check in the GUI when you have received the last updates for AV and URL Filter. If that is not too much in the past there is no need to worry.

             

            Best,

            Andre

            • 3. Re: Connection timeouts to wpm.webwasher.com
              iain.gardiner

              Thanks for your responses.

               

              Yes i'm up todate so no real issue.

               

              Cheers

              • 4. Re: Connection timeouts to wpm.webwasher.com
                iain.gardiner

                Famous last words!!

                 

                Our boxes in one of our sites has failed to download the URL filter for over 9 hrs. It is set to check every 30mins. They are on URL filter version 37739

                 

                Extract from logs:

                [Coordinator] [UpdateProcessDownloadFailedBadCode] Failed to download file: 'updates/urlfilter/lists-smartfilter-xl/37740/b744fe2f21cbd7aa4fef12b24a1bce00/ sfcontrol.37741', while host: 'mwg-update.mcafee.com' sent back HTTP-Code: '404'.   [CHTTPUpdateClient::DownloadFile]

                [2013-01-09 10:41:00.622 +00:00] [Coordinator] [UpdateProcessDownloadFileFailed] Failed to download file: 'updates/urlfilter/lists-smartfilter-xl/37740/b744fe2f21cbd7aa4fef12b24a1bce00/ sfcontrol.37741' from host: 'mwg-update.mcafee.com'.   [CClusterUpdater::DownloadUpdateFiles]

                 

                Boxes in my other site are not having this issue, they are on URL filter version 37740

                 

                ???

                • 5. Re: Connection timeouts to wpm.webwasher.com
                  luca.scamoni

                  Right now, resolving wpm.webwasher.com returns only two IP addresses and they both respond correctly

                  Check to see if they're resolving correctly and in case flush your DNS cache

                  I also got errors over the last few hours but right now it's all green

                   

                  BR

                  • 6. Re: Connection timeouts to wpm.webwasher.com
                    iain.gardiner

                    Now managed to update to 37743 on the boxes that were failing so I guess there was a problem with 37741 which was the next available file when the boxes next did their update.

                    • 7. Re: Connection timeouts to wpm.webwasher.com
                      asabban

                      Hello,

                       

                      the hoster which had problems was not able to restore the data on our update server, so we are currently re-creating it. Therefore we have removed this IP from the DNS round robin, as Luca stated. At the moment MWG will cache the response, even when it points to a failing server, which may cause problems when you resolved to the broken IP. A restart of MWG or flushing of DNS caches should help.

                       

                      We planned to add a change in the future where MWG will ask DNS for wpm.webwasher.com and will then try all three IP addresses one after each other, while at the moment it only tries the first host. This should eliminate the problem in the future.

                       

                      Best,

                      Andre

                      • 8. Re: Connection timeouts to wpm.webwasher.com
                        iain.gardiner

                        Not having any issues with wpm today. I think this morning's issue must have been down to bad data files.

                         

                        Cheers