Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 21 replies
  • Subscribers 12 subscribers
  • Views 3623 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

UTM Up2date 9.716 released

Alan Brand

Remember the days when a new update instantly created a discussion, often extending on several pages with hundreds of participants?

For now it seems to be very quiet here - so let me ask if any body has already installed it with more or less success?

I have it on 4 instances now with no notable issues, but however I never ran in one of the issues mentioned in the release notes.



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

    Today after upgrading Cluster to 9.716 all RED are unable to reconnect.

    2023:08:03-14:34:43 schxxxxxx-utm-2 red_server[17884]: [R20xxxxxxxxxxxF] Config has changed, re-read confd firmware versions
2023:08:03-14:34:46 schxxxxxx-utm-2 red_server[17884]: [R20xxxxxxxxxxxF] Curl command to push config for RED ID R20xxxxxxxxxxxF failed with error code 6, retry in 60 seconds
2023:08:03-14:35:06 schxxxxxx-utm-2 red_server[29097]: SELF: New connection from 84.xx.xx.x7 with ID R20xxxxxxxxxxxF (cipher AES256-GCM-SHA384), rev1
2023:08:03-14:35:06 schxxxxxx-utm-2 red_server[29097]: R20xxxxxxxxxxxF: Device config was not yet uploaded with the current firmware version '1-1261-6de2a4c19-b1551d2'
2023:08:03-14:35:06 schxxxxxx-utm-2 red_server[29097]: R20xxxxxxxxxxxF: Connection is refused as device config was not yet uploaded.
2023:08:03-14:35:06 schxxxxxx-utm-2 red_server[29097]: R20xxxxxxxxxxxF: Sending json message {"data":{},"type":"DEVICE_CONFIG_NOT_YET_UPLOADED_TO_PROV"}

    Ideas?

    Thanks,


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte

    Hi Dirk,

    we have updated to version 9.716 today and have also observed the error you described.

    After about 90 minutes, however, the RED devices were suddenly and unexpectedly accessible without our intervention.
    We could not determine the cause for the behavior.

    Has the error also disappeared in your case?

  • 0 in reply to Egino Natzel

    Don't know if devices are back online.

    But we discovered the RED-broker-server (red.astaro.com) can't be resolved from Germany.

    Now i can resolve the name again. 


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte

    Homeoffice Users with RED devices were running normally after update to 9.716 last week.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to PhilippRusch

    Hi Philipp,

    seems the UTM uploads the config directly after upgrade again.

    With DNS problem today, UTM are unable to do this and RED-connection is refused.

    12 locations were offline. Hope this is cured tomorrow.

    PS: Within seconds we reached Sophos Support... and after a short time we were able to isolate the upload problem. It gets better.


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte

    Good to know your experience with support.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

Reply Children
No Data
Unfiltered HTML