Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 4 subscribers
  • Views 5002 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

Up2Date not updating on UTM boxes in Canada

JRoy

Hello All,

 

I'm seeing multiple UTM boxes in Canada receiving a (status=500 Internal Server Error) when attempting to run updates either through automatic or manual.  

Does anyone have any information on this or is anyone else seeing this?

 

Thanks 

 



This thread was automatically locked due to age.
Parents
  • 0

    What do you see in the Up2Date log when this occurs?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hi Bob,

     

    This is from the log.

     

    no HA system or cluster node
    Starting Up2Date Package Downloader
    patch up2date possible
    Could not connect to Authentication Server 54.214.16.252 (code=500 500 Internal Server Error).
    Could not connect to Authentication Server 107.21.214.248 (code=500 500 Internal Server Error).
    id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
    no HA system or cluster node
    Starting Up2Date Package Downloader
    patch up2date possible
    id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
     
    Pattern version sitting at 138653 when a new pattern version (139000) is available
     
    This is being seen on multiple UTMs. 
     
    Thanks Bob
  • 0 in reply to JRoy

    That happens, but you see "Authentication successful" a few lines later, so you know the process started.  This is just the UTM being

    The pattern version looks good to me - that will be different on UTMs configured differently.  What do you see if you do the following as root at the command line?

    /sbin/audld.plx --nosys --trigger

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0 in reply to JRoy

    That happens, but you see "Authentication successful" a few lines later, so you know the process started.  This is just the UTM being

    The pattern version looks good to me - that will be different on UTMs configured differently.  What do you see if you do the following as root at the command line?

    /sbin/audld.plx --nosys --trigger

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML