M370 12.5.2 U1

Hi,

I have upgraded a M370 cluster to 12.5.2U1 and see this on the master:

Jan 17 21:22:06 2020 Webshop-HA1 local3.debug systemd: Verifying : /etc/proxy/metadata .. [OK]
Jan 17 21:22:06 2020 Webshop-HA1 local3.debug systemd: Installing : /lib/bdcore.so .. [OK]
Jan 17 21:22:06 2020 Webshop-HA1 local3.debug systemd: Installing : /tmp/bd.xml .. [OK]
Jan 17 21:22:06 2020 Webshop-HA1 local3.info systemd: Installing package: proxy-bdudp(12.1.3#610678) .. [OK]
Jan 17 21:22:06 2020 Webshop-HA1 local3.err sigd[3611]: cluster_sync_system_package: cluster package sync failed, reason=''
Jan 17 21:22:06 2020 Webshop-HA1 local3.err sigd[3611]: failed to install package
Jan 17 21:22:06 2020 Webshop-HA1 local3.err sigd[2512]: update process exited abnormally

Seems it fails to upgrade proxy-bdudp(12.1.3#610678) ??

Regards
Robert

Comments

  • James_CarsonJames_Carson WatchGuard Representative

    Hi @RVilhelmsen
    It looks like one of the cluster members failed to update the gateway AV engine by itself. It might have tried to do this while it was the backup master, or it might not have been able to reach the download server it was trying to connect to.

    Can you please check the subscription services tab on each of your firewalls? (You'll need to go to firebox system manager, and once logged in, go to tools, cluster, connect to member.)

    Try going to the subscription services tab. Under Gateway Anti-Virus, you should see a history button, click it.

    Check to see if it's updated properly since:

    For example, mine says:
    1/16/20 11:26:27 PM GMT 20200116.1353 Success Update success
    1/17/20 4:27:26 PM GMT 20200117.715 Success Update success
    1/17/20 9:27:21 PM GMT 20200117.1142 Success Update success
    1/18/20 6:28:48 PM GMT 20200118.832 Success Update success
    1/19/20 5:29:52 PM GMT 20200119.824 Success Update success
    1/20/20 5:32:04 PM GMT 20200120.754 Success Update success
    1/20/20 11:31:29 PM GMT 20200120.1206 Success Update success

    If you're stuck on an old version since that date, please open a support case (use the link on the top right of the page.) Support can then assist in looking into this for you.

    Thank you,

    -James Carson
    WatchGuard Customer Support

  • Thanks.

    Both members look fine, so it must have been a issue at boot time.

    29-01-20 07:23:14 CET   20200128.2045   Success Update success
    29-01-20 07:23:14 CET   20200128.2045   Success Update success
    29-01-20 01:23:13 CET   20200128.1445   Success Update success
    28-01-20 23:23:21 CET   20200128.1245   Success Update success
    28-01-20 23:23:21 CET   20200128.1245   Success Update success
    28-01-20 00:23:22 CET   20200127.1328   Success Update success
    28-01-20 00:23:22 CET   20200127.1328   Success Update success
    27-01-20 19:24:01 CET   20200127.940    Success Update success
    27-01-20 19:24:01 CET   20200127.940    Success Update success
    24-01-20 23:23:04 CET   20200124.1245   Success Update success
    24-01-20 23:23:04 CET   20200124.1245   Success Update success
    
Sign In to comment.