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

We have a strange thing going on here 00000071 ERROR: Could not find a source for updated packages

Hello all,

on a large part of our clients we can see this behaviour  (several 100's of about 4500+ clients)

10/5/2010 6:51:25 PM 00000071  ERROR: Could not find a source for updated packages
10/5/2010 12:30:06 PM 00000000  Updated successfully                    
 10/5/2010 11:30:08 AM 00000071  ERROR: Could not find a source for updated packages
  10/3/2010 1:20:44 PM  00000000  Updated successfully                    
   10/3/2010 12:27:48 PM 00000071  ERROR: Could not find a source for updated packages
   10/3/2010 8:42:38 AM 00000000  Updated successfully                   

The server is online all the time and can be reached from all locations.

This results in a lot of helpdesk tickets , user report a red cross on the programm icon.

Does anyone have an idea what this can be ?

Regards,

René

:5303


This thread was automatically locked due to age.
Parents
  • HI,

    I have a few questions:

    Are all those clients updating from the same server?

    The same CID\Distribution point?

    Is that server also the Sophos Management Server? 

    How many distribution points do you have on this server, the number of Sxxx directories in the SophosUpdate share is a good indication.  

    Does the SUM maintain file shares on other machines?

    Are the updating policies the same for machines that are working vs those that are not and the iconn.cfg file in the config directory of AutoUpdate are the same on a working vs non working machine?

    Could it be too much contention for the resource and maybe some fail to connect at times, this seems intermittent based on the logs.  This error means it failed to find any packages which suggests it almost failed to connect although I'd have thought you'd have errors to that effect to in the logs.

    If you have to use a single share to service all those machines, I would suggest putting it on a dedicated file server/filer to host the CID\distribution point, maybe even putting a local SUM on the machine as the churn of SUM can be quite high if maintain a lot of subscriptions.  If they have to live on the same server as the management server, I would consider using a web share using IIS/Apache, you can then change the updating policy to reference a http update path.

    Thanks,

    Jak

    :5305
Reply
  • HI,

    I have a few questions:

    Are all those clients updating from the same server?

    The same CID\Distribution point?

    Is that server also the Sophos Management Server? 

    How many distribution points do you have on this server, the number of Sxxx directories in the SophosUpdate share is a good indication.  

    Does the SUM maintain file shares on other machines?

    Are the updating policies the same for machines that are working vs those that are not and the iconn.cfg file in the config directory of AutoUpdate are the same on a working vs non working machine?

    Could it be too much contention for the resource and maybe some fail to connect at times, this seems intermittent based on the logs.  This error means it failed to find any packages which suggests it almost failed to connect although I'd have thought you'd have errors to that effect to in the logs.

    If you have to use a single share to service all those machines, I would suggest putting it on a dedicated file server/filer to host the CID\distribution point, maybe even putting a local SUM on the machine as the churn of SUM can be quite high if maintain a lot of subscriptions.  If they have to live on the same server as the management server, I would consider using a web share using IIS/Apache, you can then change the updating policy to reference a http update path.

    Thanks,

    Jak

    :5305
Children
No Data