Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 1490 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

Firewall sending many "new firmware" notifications today

LHerzog

Hi,

a SFOS 19.0.1 Firewall is sending notifications via mail and system log about new firmware today. They are much too frequent.

Probably something has gone bad while you were pushing the firmware to new machines.

When I logged on the notification popup was definitely about 19.5. MR1  - not 19.0.2. I dismissed the message and ticked: do not show again. That was at about 14:00 today.

In the firmware menu there is only the update to 19.0.2 shown.

manual search brings "No upgrades available"



This thread was automatically locked due to age.
  • 0 in reply to LHerzog

    and that is the new event in applog now containing the 19.5.2 firmware

    Feb 27 15:27:53Z apiInterface:: Deleting Entity and Event for legacy mode base operation
    Feb 27 15:27:54Z Request type = 1
    Feb 27 15:27:54Z apiInterface:versionsupported: true.
    Feb 27 15:27:54Z apiInterface:request mode -> 2705.
    Feb 27 15:27:54Z apiInterface:Current ver :::'1900.1'
    Feb 27 15:27:54Z apiInterface:entityjson::::::::HASH(0x9769760)
    Feb 27 15:27:54Z Info:: Transaction will not be rolled back for opcode get_firm_list. If any operation fails, request is part of multiple request :
    Feb 27 15:27:54Z   Current firmware is HW-19.5.1_MR-1.SF300-278.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
     Feb 27 15:27:54Z upgrade pop-up will be displayed
    Feb 27 15:27:54Z apiInterface:: Deleting Entity and Event for legacy mode base operation
    Feb 27 15:27:55Z Request type = 1
    Feb 27 15:27:55Z apiInterface:versionsupported: true.
    Feb 27 15:27:55Z apiInterface:request mode -> 557.
    Feb 27 15:27:55Z apiInterface:Current ver :::'1900.1'
    Feb 27 15:27:55Z apiInterface:entityjson::::::::system::systemgraph=HASH(0xa0e0650)
    Feb 27 15:27:55Z Info:: Transaction will not be rolled back for opcode garner:get_xml. If any operation fails, request is part of multiple request :
    Feb 27 15:27:55Z
    Feb 27 15:27:55Z
    Feb 27 15:27:55Z

    XG430_WP02_SFOS 19.0.1 MR-1-Build365# grep "Current firmware is " applog.log
    Feb 27 08:51:20Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 10:05:09Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 10:36:46Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 13:52:30Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 13:52:56Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 13:57:33Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 13:59:18Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 14:16:24Z   Current firmware is HW-19.5.1_MR-1.SF300-278.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 14:30:31Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 14:30:42Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 14:31:08Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 14:54:17Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 14:57:59Z   Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 15:27:34Z   Current firmware is HW-19.5.1_MR-1.SF300-278.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig
    Feb 27 15:27:54Z   Current firmware is HW-19.5.1_MR-1.SF300-278.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig

  • 0 in reply to LHerzog

    Generally speaking: This seems to be a known issue within the load balancing platform of the Sophos u2d servers. 

    Sophos is working on it to resolve this problem, and it mainly occurs in this situation, if your firewall can potentially have two different releases (like V19.5 and V19.0). 

    To resolve this, you would have to upgrade to one of both or wait, until the infrastructure team of SFOS resolves this. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Thanks   I have not seen this behaviour on the other firewalls we have.

    Does that log make sense to you? Current firmware is HW-19.0.2_MR-2.SF300-472.sig skip_firmware is HW-19.0.2_MR-2.SF300-472.sig

    With current firmware I would think of what is actually installed. And that is 19.0.1_MR1.

    Of course an update is planned and scheduled but until then, I disabled the mail notifications.

  • 0 in reply to LHerzog

    That is an expected message. It does not mean, what is installed, instead, what is offered by the u2d. 

    __________________________________________________________________________________________________________________

  • +1 in reply to LuCar Toni

    the notification loop just stopped after 2 HA failovers for other reasons. the ha-failover included a reboot of the machine.

Unfiltered HTML