10.9.1 Upgrade on BIOS boot mode

[cab3]

Anyone try the upgrade to 10.9.1 yet?  I did so on a test/clone VM and it seemed to go well, until the very end.  This instance has been running for some time and was installed in Legacy/BIOS boot mode.  The upgrade seems to detect this right, but after saying everything is fine, the system won't boot and you go into rescue mode:

2025-01-09 08:58:47 -0600     Performing post upgrade actions
2025-01-09 08:58:55 -0600     Detecting boot mode
2025-01-09 08:58:55 -0600 System is booted in BIOS/Legacy mode
2025-01-09 08:58:55 -0600     Installing GRUB 2
2025-01-09 08:58:55 -0600  The Boot Device is /dev/sda
Installing for i386-pc platform.
/usr/sbin/grub2-install: warning: ../grub-core/partmap/msdos.c:403:your core.img is unusually large.  It won't fit in the embedding area.
/usr/sbin/grub2-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-install: error: will not proceed with blocklists.
2025-01-09 08:59:14 -0600     Copying Grub files
2025-01-09 08:59:14 -0600     Generate GRUB configuration file
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done
2025-01-09 08:59:19 -0600     Cleaning up /boot/grub dir
2025-01-09 08:59:20 -0600 FIPS Mode was not enabled.
2025-01-09 08:59:21 -0600 post-update script successfully executed.
2025-01-09 08:59:21 -0600 sms-appliance-release-10.9.1-3 successfully installed.

I'm going to see what I can sort out, but figured I'd post here just to give others a potential heads-up.

[alexander-smg]

Mine completely blew up the VM, had to restore. Very bad so far

[cab3]

Luckily, I took a snapshot prior and was able to revert, and it was on a clone, so no permanent harm done.

[alexander-smg]

My reversion worked.

[James Martini]

The update to SMG 10.9.1 effectively installs an entirely new operating system and kernal. Unfortunately, SMG systems which have been in continuous use since version 10.7.3 and earlier may have an issue with the underlying /boot filesystem not having enough free space for the updated kernel and boot image. There also appear to be some network related issues on some KVM based systems related to the naming of the network interfaces. 

These issues are being actively investigated and will be documented in the Messaging Gateway 10.9 release notes and late breaking news KB as we move forward. As always, please read the release notes carefully prior to upgrading and be mindful of software update best practices.

If you have issues with the update to SMG 10.9.1, please do not hesitate to open a support case as this is likely to be a better path to resolution than the forums.

Thank you,
James Martini

[alexander smg]

Unclassified | Non classifié

10.9.1 breaks on install. yuk

[Cmy]

What is the correct  way to  upgrade  SMG  10.9.1 ?

[alexander-smg]

There really isnt a complete install guide with pics. For heaven sake, I dunno why.

[James Martini]

For most releases, the update can be performed from the Control Center web interface via the Administration > Version > Updates page.

Due to the nature of the SMG 10.9.0 > 10.9.1 update, the Control Center host should be updated from the admin command line using the update install command. Support generally recommends updating from the command line as a matter of general principle.

We also release PDF copies of our documentation for review as part of the software release process. These can be found at https://techdocs.broadcom.com/us/en/symantec-security-software/email-security/messaging-gateway/10-9-1/related-documents.html and include the Admin Guide, the Command Line Reference, the Installation Guide, and the Release Notes for the release in question.

As has been pointed out, we don't include a lot of pictures in these documents so some reading is required but that is feedback that I can take to our documentation team.

[reza akhlaghy]

We encounter the same problem. We had our current install since version 10.7 and disk size is 90GB. We upgraded to 10.9.1 and it fails and goes into rescue mode. So, I installed a new version 10.9 (now the disk becomes 125GB) and restore config, then upgrade and this time it works.

[IT Support Admin]

Looks like it got pulled for not doing enough extensive testing per the KB latest update. 

How can you update the entire underlying operating system and just make this a minor release-that alone seem bizarre, these are major updates in my opinion.

I will wait to hear other people's experience before I upgrade to the latest version from just one minor version back.

I typically wait 2-3weeks anyway and always take a snapshot of the control center and all scanners beforehand, we don't need to be bleeding edge over here but looking forward to TLS 1.3, etc. when it actually becomes stable for upgrade.

Lastly, I agree that it was not clear how to upgrade SMG control center OS from SMG terminal and wasn't aware of needing that link where it is all posted.

The upgrade notification when different than previous multiple versions at a minimum should indicate where to look for further detail when obviously people have been upgraded for years a different way regardless of what is suggested than what is required now.

Appreciate the support efforts regardless-but writing a few words and providing the links without having to poke around Google or Broadcom posts would not take much effort and more easily clarify for your customers. Don't assume every customer knows since document wording buried in some link for years states 'they suggest doing it method X', when many have been upgrading via method Z for years!

I'll stay tuned, in the meantime, and let me manager know SMG latest minor version release with a brand new underlying Linux OS got pulled per too many issues their customers experienced. 

[alexander-smg]

Of course you agree with my assessment. I run the largest smg cluster. I love the product. But even 10.9.1 still cant pull more than 1000 logs. Not good

[Cmy]

I  tried  today  to upgrade as  usual  before  but  update  check and  update  downloads  commands  give  error  as  described  in the  article below.

https://knowledge.broadcom.com/external/article/385400

What is the  correct  way to  upgrade SMG to the  10.9.1 ?   I  did not  find a  step by step  document ,  anyone   find it ?

[alexander-smg]

There aint any. This upgrade is going very badly for many. However, if successful, the updates are worth it. Just that you cant get more than 1000 entries of audit logs in UI. boooooooooo

[Art_P]

Alexander is not a Broadcom employee and does not actually have any information on the installation status of Messaging Gateway. To date, we have only had cases regarding the "update download" and "update check" commands, which is addressed in the Release Notes and the previously referenced Article, and a couple of cases related to boot partition size.

The boot partition size issue is related to appliances that were originally installed prior to 10.7.0 and have been upgraded over time. These older systems have a smaller boot partition that is too small for current version updates and results in a "kernel panic". This is an issue that has existed with previous versions, here is the article regarding the error:

Kernel panic following update to Messaging Gateway on Hyper-V

The article references Hyper-V, but I believe this issue may occur for other platforms as well. If we can confirm other platforms, we will update the article.

------------------------------
---------------------------------------------
Support Engineer
* Integrated Cyber Defense Exchange
* Messaging Gateway
* Packet Shaper
Symantec Enterprise Division
Broadcom Software
------------------------------

[alexander-smg]

Hi, yes I am very aware of the installation status. There are numerous issues. There needs to be a guide created with pictures to show this new install procedure.

[Art_P]

If you, or anyone, encounters errors with the installation process, please open a technical support case so we can help you resolve the issue. The current support cases we have seen related to 10.9.1 are as I previously mentioned. If we determine any new issues it will be updated in the Late Breaking News article for 10.9 (which should be updated shortly for the 10.9.1 release):

Messaging Gateway 10.9 release notes and late breaking news

------------------------------
---------------------------------------------
Support Engineer
* Integrated Cyber Defense Exchange
* Messaging Gateway
* Packet Shaper
Symantec Enterprise Division
Broadcom Software
------------------------------

[alexander-smg]

Please create a pictured install process and make it public. Opening up support cases takes too much time.

thanks

[alexander-smg]

I am aware please make a pictured process for this new install.

[Thomas Anderson]

Please read the release notes, it's all in there.

A short synopsis (but *don't depend on this, read and follow the release
notes*!):

*- MAKE SURE YOU ARE AT 10.9.*0* BEFORE STARTING THE *UPGADE* PROCESS!!*

- Take a backup (of course)

- On any boxes that contain a *GUI* (*BCC* and *Stand Alone Quarantine*),
use the *CLI *command to update install.

- Once the BCC has been upgraded, you may use the GUI to upgrade the
attached scanners.

As noted, we are replacing the entire OS as well as updating the product.
Due to compatibility issues across the different OS's the "update check"
and and "update download" are not working for this upgrade.

The update and OS replacement has been extensively tested on all supported
hardware and virtual platforms.
The instructions in the *release notes *are a result of that testing and
are intended to help customers avoid any known issues that were
encountered.

On Fri, Jan 10, 2025 at 10:21 AM alexander-smg via Broadcom <
[e-mail]> wrote:

> There aint any. This upgrade is going very badly for many. However, if
> successful, the updates are worth it. Just that you cant get more than...
> -posted to the "Messaging Gateway" community
> [image: Broadcom] <https: community.broadcom.com>
> Messaging Gateway
> <https: community.broadcom.com symantecenterprise communities community-home digestviewer?communitykey=bba1e9dc-0c56-4fb5-9e3d-ef7f0d79b7ee>
> Post New Message <[e-mail]>
> Re: 10.9.1 Upgrade on BIOS boot mode
> <https: community.broadcom.com symantecenterprise discussion 1091-upgrade-on-bios-boot-mode#bm2cb89f10-2cc8-452e-b8eb-4ab924528a6c>
> Reply to Group
> <[e-mail]?subject=re:+10.9.1+upgrade+on+bios+boot+mode> Reply
> to Sender
> <https: community.broadcom.com symantecenterprise communities all-discussions postreply?messagekey=2cb89f10-2cc8-452e-b8eb-4ab924528a6c&ListKey=c7074c2b-e593-418f-9d9e-0567f9e41e52&SenderKey=2c58ebd1-fafc-484a-90f6-259496c972b0>
> [image: alexander-smg]
> <https: community.broadcom.com network members profile?userkey=2c58ebd1-fafc-484a-90f6-259496c972b0>
> Jan 10, 2025 1:21 PM
> alexander-smg
> <https: community.broadcom.com network members profile?userkey=2c58ebd1-fafc-484a-90f6-259496c972b0>
> There aint any. This upgrade is going very badly for many. However, if
> successful, the updates are worth it. Just that you cant get more than 1000
> entries of audit logs in UI. boooooooooo
>
> *Reply to Group Online
> <https: community.broadcom.com symantecenterprise communities all-discussions postreply?messagekey=2cb89f10-2cc8-452e-b8eb-4ab924528a6c&ListKey=c7074c2b-e593-418f-9d9e-0567f9e41e52>*
> *Reply to Group via Email
> <[e-mail]?subject=re:+10.9.1+upgrade+on+bios+boot+mode>*
> *View Thread
> <https: community.broadcom.com symantecenterprise discussion 1091-upgrade-on-bios-boot-mode#bm2cb89f10-2cc8-452e-b8eb-4ab924528a6c>*
> *Recommend
> <https: community.broadcom.com:443 symantecenterprise discussion 1091-upgrade-on-bios-boot-mode?messagekey=2cb89f10-2cc8-452e-b8eb-4ab924528a6c&cmd=rate&cmdarg=add#bm2cb89f10-2cc8-452e-b8eb-4ab924528a6c>*
> *Forward
> <https: community.broadcom.com symantecenterprise communities all-discussions forwardmessages?messagekey=2cb89f10-2cc8-452e-b8eb-4ab924528a6c&ListKey=c7074c2b-e593-418f-9d9e-0567f9e41e52>*
> *Flag as Inappropriate
> <https: community.broadcom.com symantecenterprise discussion 1091-upgrade-on-bios-boot-mode?markappropriate=2cb89f10-2cc8-452e-b8eb-4ab924528a6c#bm2cb89f10-2cc8-452e-b8eb-4ab924528a6c>*
>
> -------------------------------------------
> Original Message:
> Sent: 1/9/2025 4:41:00 PM
> From: Cmy
> Subject: RE: 10.9.1 Upgrade on BIOS boot mode
>
> I tried today to upgrade as usual before but update check and
> update downloads commands give error as described in the article
> below.
>
> knowledge.broadcom.com/external/article/385400
>
> What is the correct way to upgrade SMG to the 10.9.1 ? I did not
> find a step by step document , anyone find it ?
>
>
>
>
>
> You are subscribed to "Messaging Gateway" as [e-mail].
> To change your subscriptions, go to My Subscriptions
> <http: community.broadcom.com preferences?section=Subscriptions>. To
> unsubscribe from this community discussion, go to Unsubscribe
> <http: community.broadcom.com higherlogic egroups unsubscribe.aspx?userkey=a0cd617b-8881-4510-8b5e-9bef710b50d4&sKey=KeyRemoved&GroupKey=c7074c2b-e593-418f-9d9e-0567f9e41e52>.
>
>
> Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
> refers to Broadcom Inc. and/or its subsidiaries.
>
> Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
> <https: www.broadcom.com company legal privacy-policy> | Cookie Policy
> <https: www.higherlogic.com legal privacy> | Supply Chain Transparency
> <https: www.broadcom.com company citizenship governance-and-ethics#supply>
> | Terms of Use <http: termsandconditions>
>


--

Tom Anderson

Director of Development | Ex ignorantia ad sapientum

Symantec Enterprise Division | e tenebris ad lucem!

415.307.1673 | - someone famous I’m sure

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.

[Andrey Fyodorov]

So, regarding the issue of not having enough free space for the update, how much free space is needed? And how exactly can we check whether we have enough free space?

[cab3]

This wasn't really a filesystem space issue as much as a partition size issue from some early installs, and the size limitations from Grub and other components that simply wouldn't fit in the older sized partitions.  

As earlier, I am not a Broadcom employee and do not speak on behalf of them, and am simply sharing my personal experience in hopes it may help others.

[B Baker]

"Just that you cant get more than 1000 entries of audit logs in UI."

Is there a place we can add and vote for ideas to be included in upcoming releases?  It would be great to get beyond this limit, even if searches take longer.

[alexander-smg]

I have been asking for 10 years

[B Baker]

Right after I asked, I found the ideas section...but if you've been asking for that long...

[alexander-smg]

Put one in for me as well. 10 years of more than 1000 UI audit logs. Thanks again

[James Martini]

Messaging Gateway provides a number of means of accessing and searching the message audit logs: Search from the control center, search from command line via malquery (which is unlimited), search via REST API, and remote logging of audit data to syslog compliant SIEMs or log aggregators.

The fundamental issue here is that audit logging was not designed to be a general reporting or bulk data retrieval feature. It's purpose is to allow administrators to identify individual or small groups of messages to address any questions regarding how Messaging Gateway processed the messages. We recognize that it does provide a convenient means of collecting statistics on SMG mail processing but we have some built in reports which should address those needs in a more scalable way.

If there is a business need for expanded audit log searching, we always recommend remote logging of audit data to an external logging solution since SMG is primarily an email security solution rather than an email reporting solution.

[alexander-smg]

I cannot do remote logging, and I have 10 gateways, I cannot malquery 10 times?!? Also, I have so much email, a 1000 results in not enough. Also, the audit logs cannot do per sec date range. Only minutes.

hmmmm

[Thomas Anderson]

which sounds like you are an ideal candidate to use the REST API to get the data you need without impacting your active BCC session, which would be on hold while the system is reaching out to 10 scanners to collect the data you you are looking for.

[alexander-smg]

The perfect solution is grabbing like 10000 results. Like fortimail, ironport, exo, can.

[Art_P]

The article you referenced contains a link to the Release Notes. The Release Notes provides the steps to upgrade. The command line update command is "update install", it is just the related "update download" and "update check" commands that do not work.

So, follow the Release Notes steps and update with "update install"

------------------------------
---------------------------------------------
Support Engineer
* Integrated Cyber Defense Exchange
* Messaging Gateway
* Packet Shaper
Symantec Enterprise Division
Broadcom Software
------------------------------

[Thomas Anderson]

Please read the Release Notes, as the issue regarding "update check" and
"update download" as well as the instructions to perform and upgrade are
covered.

On Fri, Jan 10, 2025 at 10:19 AM Cmy via Broadcom <[e-mail]> wrote:

> I tried today to upgrade as usual before but update check and update
> downloads commands give error as described in the article... -posted to the
> "Messaging Gateway" community
> [image: Broadcom] <https: community.broadcom.com>
> Messaging Gateway
> <https: community.broadcom.com symantecenterprise communities community-home digestviewer?communitykey=bba1e9dc-0c56-4fb5-9e3d-ef7f0d79b7ee>
> Post New Message <[e-mail]>
> Re: 10.9.1 Upgrade on BIOS boot mode
> <https: community.broadcom.com symantecenterprise discussion 1091-upgrade-on-bios-boot-mode#bm322e3a3b-1fd8-4833-816d-01944d0155d9>
> Reply to Group
> <[e-mail]?subject=re:+10.9.1+upgrade+on+bios+boot+mode> Reply
> to Sender
> <https: community.broadcom.com symantecenterprise communities all-discussions postreply?messagekey=322e3a3b-1fd8-4833-816d-01944d0155d9&ListKey=c7074c2b-e593-418f-9d9e-0567f9e41e52&SenderKey=8b9840c9-d109-46f4-9397-66ea17d8d23b>
> [image: Cmy]
> <https: community.broadcom.com network members profile?userkey=8b9840c9-d109-46f4-9397-66ea17d8d23b>
> Jan 10, 2025 1:19 PM
> Cmy
> <https: community.broadcom.com network members profile?userkey=8b9840c9-d109-46f4-9397-66ea17d8d23b>
>
> I tried today to upgrade as usual before but update check and
> update downloads commands give error as described in the article
> below.
>
> knowledge.broadcom.com/external/article/385400
>
> What is the correct way to upgrade SMG to the 10.9.1 ? I did not
> find a step by step document , anyone find it ?
>
> *Reply to Group Online
> <https: community.broadcom.com symantecenterprise communities all-discussions postreply?messagekey=322e3a3b-1fd8-4833-816d-01944d0155d9&ListKey=c7074c2b-e593-418f-9d9e-0567f9e41e52>*
> *Reply to Group via Email
> <[e-mail]?subject=re:+10.9.1+upgrade+on+bios+boot+mode>*
> *View Thread
> <https: community.broadcom.com symantecenterprise discussion 1091-upgrade-on-bios-boot-mode#bm322e3a3b-1fd8-4833-816d-01944d0155d9>*
> *Recommend
> <https: community.broadcom.com:443 symantecenterprise discussion 1091-upgrade-on-bios-boot-mode?messagekey=322e3a3b-1fd8-4833-816d-01944d0155d9&cmd=rate&cmdarg=add#bm322e3a3b-1fd8-4833-816d-01944d0155d9>*
> *Forward
> <https: community.broadcom.com symantecenterprise communities all-discussions forwardmessages?messagekey=322e3a3b-1fd8-4833-816d-01944d0155d9&ListKey=c7074c2b-e593-418f-9d9e-0567f9e41e52>*
> *Flag as Inappropriate
> <https: community.broadcom.com symantecenterprise discussion 1091-upgrade-on-bios-boot-mode?markappropriate=322e3a3b-1fd8-4833-816d-01944d0155d9#bm322e3a3b-1fd8-4833-816d-01944d0155d9>*
>
> -------------------------------------------
> Original Message:
> Sent: Jan 09, 2025 01:07 PM
> From: cab3
> Subject: 10.9.1 Upgrade on BIOS boot mode
>
> Anyone try the upgrade to 10.9.1 yet? I did so on a test/clone VM and it
> seemed to go well, until the very end. This instance has been running for
> some time and was installed in Legacy/BIOS boot mode. The upgrade seems to
> detect this right, but after saying everything is fine, the system won't
> boot and you go into rescue mode:
>
> 2025-01-09 08:58:47 -0600 Performing post upgrade actions2025-01-09 08:58:55 -0600 Detecting boot mode2025-01-09 08:58:55 -0600 System is booted in BIOS/Legacy mode2025-01-09 08:58:55 -0600 Installing GRUB 22025-01-09 08:58:55 -0600 The Boot Device is /dev/sdaInstalling for i386-pc platform./usr/sbin/grub2-install: warning: ../grub-core/partmap/msdos.c:403:your core.img is unusually large. It won't fit in the embedding
> area./usr/sbin/grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged../usr/sbin/grub2-install: error: will not proceed with blocklists.2025-01-09 08:59:14 -0600 Copying Grub files2025-01-09 08:59:14 -0600 Generate GRUB configuration fileGenerating grub configuration file ...Adding boot menu entry for UEFI Firmware Settings ...done2025-01-09 08:59:19 -0600 Cleaning up /boot/grub dir2025-01-09 08:59:20 -0600 FIPS Mode was not enabled.2025-01-09 08:59:21 -0600 post-update script successfully executed.2025-01-09 08:59:21 -0600 sms-appliance-release-10.9.1-3 successfully installed.
>
> I'm going to see what I can sort out, but figured I'd post here just to
> give others a potential heads-up.
>
>
>
>
> You are subscribed to "Messaging Gateway" as [e-mail].
> To change your subscriptions, go to My Subscriptions
> <http: community.broadcom.com preferences?section=Subscriptions>. To
> unsubscribe from this community discussion, go to Unsubscribe
> <http: community.broadcom.com higherlogic egroups unsubscribe.aspx?userkey=a0cd617b-8881-4510-8b5e-9bef710b50d4&sKey=KeyRemoved&GroupKey=c7074c2b-e593-418f-9d9e-0567f9e41e52>.
>
>
> Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
> refers to Broadcom Inc. and/or its subsidiaries.
>
> Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
> <https: www.broadcom.com company legal privacy-policy> | Cookie Policy
> <https: www.higherlogic.com legal privacy> | Supply Chain Transparency
> <https: www.broadcom.com company citizenship governance-and-ethics#supply>
> | Terms of Use <http: termsandconditions>
>


--

Tom Anderson

Director of Development | Ex ignorantia ad sapientum

Symantec Enterprise Division | e tenebris ad lucem!

415.307.1673 | - someone famous I’m sure

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.

[cab3]

As a matter of my own experimentation over the last couple days, what I found is that if you're in a case where you had an "old" install, which could have any space constraints, the approach that I took was to get to 10.9.0.  I also stood up a brand new image of 10.9.0 in a separate VM.  After that image was ready, I then took a complete backup of my previous Messaging Gateway via the integrated full-backup (keep in mind I'm doing this in a small environment, with a single combined installation) to external storage.  I then restored the "new" image from that backup.  After that, I was able to go thru the "update install" process and the 10.9.1 image was successfully installed.

Caveats:  I am not a Broadcom employee, and do not speak on behalf of them.  This is what worked for me, and your individual mileage will vary based on your own environment and deployment.  My environment was set up some time back, and continually upgraded with new versions since, probably 10.5 if not earlier. 

[alexander-smg]

There are lots of issues with this install and really no clear instructions in the release notes that actually says to use update install. Etc.

[cab3]

Short of maybe adding a sentence to the end Upgrade Considerations snippet below that could say "To initiate the upgrade process, perform execute 'upgrade install' from a console or ssh connection." I didn't have too many complaints. 

I suspect that the "Known issues" may get a refresh with some guidance on upgrades from what I'll call "very early" versions that may have some partition/space limitations.  It'd have been nice if this was checked in a pre-check of some sort, but it wasn't hugely difficult to overcome, once I got access to install media (longer story).

Being a Product Manager myself, and having had to provide a similar OS upgrade process with my product to Rocky also, there's always going to be some corner cases that slip thru the testing.  I'm grateful for the timely engagement of Messaging Gateway Product and Support folks here that have been willing to lend a hand.  Kudos!

[alexander-smg]

I am glad to have helped in your endeavours.. take care

[Istvan Gogolak]

Hello,

update install, ok- smgcc, scanners....
After the upgrade, the following (scanners) errors appear in the log.

Scanners, But with the MTA engine, it writes an error in the log

MTA  Error OpenSSL 3.0.14+SL CCS-2.1.2.23
Has anyone encountered this error?

[Pierre-Alain Lautard]

Same error message here after the failed upgrade...

I have a case open since yesterday morning (13398) but support is definitely NOT helpful.

Last message from them is almost 24h ago... even though I have asked updates several times.

The guy even asked me why would I want to update my installation as I'm running 10.9.0 and it's good enough for him :p

[cab3]

Check out #31 above where I tried to outline what I did to rectify my issue, especially if you're upgrading from an initial install on a much earlier version, as I was.  I ended up deploying a 10.9.0 natively, created a backup on my running 10.9.0, and restored it onto the newly installed instance, switched IP addresses to have the newly deployed active, and then proceeded to snapshot the VM and run the "update install" which got me to 10.9.1 on the new OS.  I've seen issue after. 

Your mileage may vary and I am not speaking for or on behalf of Broadcom.  I am not a Broadcom Employee, nor do I play one on television. :)

[Pierre-Alain Lautard]

Hi,

did you manage to keep all settings, certificates, logs... ?

[cab3]

It certainly seemed to.  While I don't know your situation personally, if you're running in a virtualized environment, you should be able to snapshot at various points in the process to be able to apply a backup and doublecheck everything, and if not, revert your snapshots.  I did a full backup from my active system and then restored that same backup to my newly deployed (same version) system.  All of my quarantine, settings, etc. seemed fully intact; I didn't check for previous logs, etc. as I didn't really care about them that much just my settings and my local permit/deny settings, etc.  I'm certainly running a smaller environment than many here, but that's what worked for me.

[alexander smg]

Unclassified | Non classifi?

That full backup must have taken hours. Smg backups are super slow

[alexander smg]

Unclassified | Non classifi?

So what exactly is your issue???