SLES11 SP4 notification while patching OES11 SP3 and OES2015 SP1


Hi Everyone, Just a heads up.  As you may know SLES11 SP4 went out of general support at the end of March 2019. Now, if you try to patch any OES version based on that like OES11 SP3 or OES2015 SP1, you may receive an pop-up notification like the below.  It’s informational in nature and …

+read more

The post SLES11 SP4 notification while patching OES11 SP3 and OES2015 SP1 appeared first on Cool Solutions. Madhan


7018416: Clear cache on SUSE Manager Proxy

proxyclient3:/etc/ssl/certs # zypper ref -s

All services have been refreshed.

Repository ‘SLES11-SP4-Pool for x86_64’ is up to date.

Retrieving repository ‘SLES11-SP4-SUSE-Manager-Tools x86_64’ metadata []

Warning: Digest verification failed for file ‘updateinfo.xml.gz’


expected 0fe3250dcca441ff3ec9d5935982e7e12af3690d

but got bca670744a56453e847c669b705bb7939a2c399e

Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.

However if you made certain that the file with checksum ‘bca6..’ is secure, correct

and should be used within this operation, enter the first 4 characters of the checksum

to unblock using this file on your own risk. Empty input will discard the file.

Unblock or discard? [bca6/? shows all options] (discard):


7018396: GroupWise Mobility Web Admin console is blank after updating SLES12 SP

This document (7018396) is provided subject to the disclaimer at the end of this document.


GroupWise Mobility Service 18

GroupWise Mobility Service 2014 R2

SUSE Linux Enterprise Server 12


  • Applying a Service Pack to any version of SLES12 (e.g. SLES12 to SLES12 SP1 or SLES12 SP2 to SLES12 SP3) running any version of GMS (e.g. GMS 14.2.2 or GMS 18.0.0) breaks GMS Dashboard
    • e.g. After upgrading from SLES12 with GMS 14.2.1-237 to SLES12 SP2 with GMS 14.2.1-270 the dashboard was no longer working
    • e.g. After applying SLES12 SP3 to SLES12 SP2 with GMS 18.0.1-280 the dashboard displayed but remained unpopulated (no graphics/counters)
  • GMS Dashboard is blank or empty
  • Clicking anywhere in admin console freezes


A script has been provided for download, that contains instructions on its use to fix this issue. See
A future version of Mobility will have this issue fixed out of the box.

Additional Information

Script readme still refers to only GMS14 and only SLES12 FCS to SP1 or SP2. This is scheduled to be updated.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


7014247: How to upgrade SLES for SAP Applications 11 SP2 to SP3

This document (7014247) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 11 for SAP Applications


A system running SLES for SAP Applications 11 Service Pack 2 should be upgraded to Service Pack 3.


Important note: Aftercompleting any form of update, run the command “rcrpmconfigcheck”, then look at the contents of the file /var/adm/rpmconfigcheck.This file contains a list of configuration files that could not beupdated automatically. These files must be checked and theconfigurations adjusted manually.

Procedure for upgrading from SLES / SLED 11 SP2There are different supported ways for updating a SUSE LinuxEnterprise 11 system to SP3 level. Users can either update to SP3 byusing the online update tools to install the respective patches or update using the SP3 installation media.

For installing SP3 via the respective patches, the following toolsare supported:

  • 1) YaST (“yast2 wagon”)
  • 2) zypper

Alternatively, the full SP3 media (DVD ISOimage) can be downloaded and one of the following procedures can be used, especially in caseof environments without network access:

  • 3) by booting from SLES for SAP 11 SP3 media

Update to SP3 via patches

Attention: The update process has to be done completely frombeginning to reboot. There is only a limited chance to revert changes.Furthermore, the server has to be connected online during thewhole update process.

Users have to makesure to have the system registered. If this is not done already, it can either be registered by using the “Novell Customer CenterConfiguration” module in YaST or by using the suse_register commandlinetool. This will add update sources to the system.

1) Update by using YaST and/or Update Applet

  • Start the Online-Update module (YOU) from the YaST control center.
  • Check, if all available patches that are named “You update for Software update stack” are installed. If this is not the case, those patches will automatically be preselected. Press ‘Accept’ to apply those updates. Among others, this will install updates of libzypp, satsolver, yast2-wagon, yast2-pkgbindings, etc.After installing those, YOU will restart itself.
  • Now it is possible to install all other updates that are availablefor SLE for SAP 11 SP2. The system needs to be rebooted afterwards, because the kernel and/or other important system components are updated.
  • Thetray applications kupdateapplet or gnome-packagekit will display amessage that a distribution upgrade is available and start the YaST2module ‘wagon’ on request. If the gnome desktop is being used, but thegnome-packagekit applet is not started automatically on login, go aheadas follows:
    • Press ALT-F2 and run ‘gconf-editor’.
    • In here, select ‘apps’ -> ‘gnome-packagekit’ -> ‘force_get_update_login’.
    • Afterthe next login the gnome-packagekit will start automatically and openup a message that a distribution upgrade is available.
  • As an alternative to using the tray application open up a root shell and run ‘/usr/sbin/wagon &’.
  • to manually start yast wagon you can also open a root shell and execute ‘yast2 wagon’
  • yast2-wagon contains a workflow to upgrade the system to the next Service Pack level. On the welcome page press “Next”.
  • yast2-wagon will do an automatic self update if needed.
  • Inthefollowing dialogue select how to migrate. Select “CustomerCenter” if the update repositories should be used, or select “Custom URL”if you want to specify the update source manually (see the respectivesection below). In most cases “Customer Center” should be the rightchoice. If you want to review the repositories changes yourself,additionally select “Check Automatic Repository Changes”. Click “Next”.
  • Are-registration of the system against the Novell Customer Center will be done. During the registrationprocess the appropriate SP3 update catalogs (SLE11-SP3-SAP-Pool, SLE11-SP3-SAP-Updates, SLES11-SP3-Pool, etc.) will be added. TheSLES for SAP 11 SP1/SP2 catalogs will be removed. Click “Next”.
  • The successdialog-popup at the end informs about which repositories were added (clickon the “Details” Button). A detailed list of the repos can be found further down in this document in the “Update via zypper” section.
  • Ifyou have selected “Check Automatic Repository Changes”, the list ofrepositories will be displayed, providing the opportunity to manuallyenable/disable/add/delete repositories. Klick “Ok” when finished.
  • A proposal screen (named “Distribution Updrade Settings”) is now listed with the following sections:
    • Add-On Products: Third Party add-on products can be added here.
    • UpdateOptions: This shows what will happen with the product. Temporarymigration products (e.g. SUSE_SLES-SP3-migration) will be removed, realproducts (e.g. SUSE_SLES) will be upgraded. Further, it can be selected, if all packages should be downloaded before upgrading (this is the default) or if the packages should be downloaded and installed one by one.
    • Packages: shows some statistics about rpm packages to update, to install and to remove.
    • Backup: some backup options.
  • Please note: If you changed your mind and want to abort the upgrade to SP3,click “Back” then “Abort”. In this case a rollback is triggered tobring the system back to SLE 11 SP2 level. Further the migrationproducts are removed, a re-registration is performed and the newlyadded repositories are removed.
  • To continue the upgrade to SP3 press “Next” -> “Start Update”.
  • The following steps are executed:
    • The update of the rpm packages is performed.
    • SuSEconfig is executed.
    • A message to reboot the system is displayed (Press “Ok”).
    • Aregistration of the final SP3 product(s) takes place. Please note that only the SLE 11 SP3 catalogs need to stay enabled.
  • After a reboot the system is on SP3 level.
1.1) Using a “Custom URL” for updating with YaST
  • Start yast2 wagon as stated above.
  • In the “Update method” dialogue select “Custom URL”.
  • Alist of repositories will be displayed, providing the opportunity tomanually enable/disable/add/delete repositories. In here it is possible to manually adjust installation- and update repositories.
  • Add the SP3 update source(s). This can either be the SP3 installation media or the new SP3 repositories (SP3-Pool and SP3-Updates).
  • Klick “Ok” when finished and continue with the “Distribution Upgrade Settings” dialogue as stated above.

2) Update by using zypper

  • Open a root shell.
  • Run ‘zypper ref -s’ to refresh all services and repositories.
  • Run ‘zypper update -t patch’ to install package management updates (same as “zypper patch”)
  • Now it is possible to install all available updates for SLES for SAP 11 SP2: run ‘zypper update -t patch’ again.
(As a sidenote: if you want to use the above command in a script for an unattended upgrade, the command would be: “zypper –non-interactive patch –auto-agree-with-licenses –with-interactive”)
  • Now the installed products contain information about distribution upgradesand which migration products should be installed to perform themigration. Read the migration product informations from/etc/products.d/*.prod and install them. Use the followingcommand:
  • zypper se -t product | grep -h — “-migration” | cut -d| -f2
  • A sample output could be as follows:
  • Install these migration product:
    • zypper in -t product SUSE_SLES_SAP-SP3-migration
  • run ‘suse_register -d 2 -L /root/.suse_register.log’ to register theproducts in order to get the corresponding SP3 Update repositories.
  • Run ‘zypper ref -s’ to refresh services and repositores.
  • Check the repositories using ‘zypper lr’. Important: if needed, disable the SP1/SP2 Pool/Core/Updates repositories manually and enable the new SP3 repositories:
    • zypper mr –disable <repo-alias>
    • zypper mr –enable <repo-alias>
  • The following repositories should be made available (please note this list contains the HAE add-on product):

  • SLES4SAP:~ # zypper lr -E

    # | Alias | Name | Enabled | Refresh


    1 | SLES-for-SAP-Applications 11.2.2-1.5 | SLES-for-SAP-Applications 11.2.2-1.5 | No | No

    2 | nu_novell_com:SLE11-HAE-SP3-Pool | SLE11-HAE-SP3-Pool | Yes | Yes

    3 | nu_novell_com:SLE11-HAE-SP3-Updates | SLE11-HAE-SP3-Updates | Yes | Yes

    4 | nu_novell_com:SLE11-SP2-WebYaST-1.3-Pool | SLE11-SP2-WebYaST-1.3-Pool | Yes | Yes

    5 | nu_novell_com:SLE11-SP2-WebYaST-1.3-Updates | SLE11-SP2-WebYaST-1.3-Updates | Yes | Yes

    6 | nu_novell_com:SLE11-SP3-SAP-Pool | SLE11-SP3-SAP-Pool | Yes | Yes

    7 | nu_novell_com:SLE11-SP3-SAP-Updates | SLE11-SP3-SAP-Updates | Yes | Yes

    8 | nu_novell_com:SLES11-SP3-Pool | SLES11-SP3-Pool | Yes | Yes

    9 | nu_novell_com:SLES11-SP3-Updates | SLES11-SP3-Updates | Yes | Yes
  • Then perform a dist upgrade by using the following command (example including the HAE add-on product)
    • zypper dup –from SLE11-HAE-SP3-Pool –from SLE11-HAE-SP3-Updates –from SLE11-SP2-WebYaST-1.3-Pool –from SLE11-SP2-WebYaST-1.3-Updates –from SLE11-SP3-SAP-Pool –from SLE11-SP3-SAP-Updates –from SLES11-SP3-Pool –from SLES11-SP3-Updates

      #add more SP3 catalogs here if needed, e.g. in case other add-on products are installed
  • zypper will report that it will delete the migration product and update themain products. Confirm the message to continue updating the rpm packages.
  • After the upgrade is finished, register the newproducts again:
    • suse_register -d 2 -a -a regcode-sles=insert_valid_regcode -L /root/.suse_register.log
  • Reboot the system

Update to SLES for SAP 11 SP3 via patches by using Subscription Management Tool for SUSE Linux Enterprise

As an alternative to downloading the updates for each singleclient system from the Novell update server, it is possible to useSubscription Management Tool for SUSE Linux Enterprise to mirror theupdates to a local server.

This tool acts as Novell CustomerCenter proxy both for client registrations and as software updaterepository. The SMT documentation at gives an overview of its features as well as instructions on how to implement it.

Update via using a SLES for SAP Applications 11 SP3 installation media

Please obtain the ISO images from

3) Update by booting from a SLES for SAP Applications 11 SP3 media

To start the standard update via DVD, reboot thecomputer with this medium in it’s DVD drive. Perform a systemupdate instead of a fresh installation. To achive this, select”Installation” -> Select language and keyboard layout -> Agree tothe License -> Select “Update an Existing System” instead of “New Installation”.

3.1) Update by booting off a SP3 network installationsource

It is also possible to provide the installation media vianetwork. The SLES for SAP 11 Service-Pack 3 media contains a complete product. So it can beadded to an installation server in the same way as every other SUSELINUX Enterprise product. The procedure on how to setup an installationserver and on how to addthe service pack is described in the product documentation. For SLES 11 havea look into chapter 14.2 of the deployment guide. The document isavailable online under

To start the update, go ahead as follows:

  • A bootable medium is needed to initialize the process. Booting vianetwork/PXE is also possible. For PXE boot configuration examples seechapter 14.3 in the SLES 11 deployment guide (online available at ).
  • Boot the machine and choose “Installation”.
  • Changethe installation source via the “F4” key and enter the IP and path to the installation source or select “SLP” if this protocol is configuredon your installation server.
  • Select “System Update” instead of performing a “New Installation”.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


7022381: zypper migration with LTSS repo results in “No migration available”

Remove the LTSS repository with SUSEConnect:

SUSEConnect -d -p SLES-LTSS/12.1/x86_64

Refresh the repository list:

zypper ref –services

The LTSS repository should not be present:

zypper lr

# | Alias | Name | Enabled | GPG Check | Refresh


1 | SMT-http_sles12s1_suse:SLES12-SP1-Pool | SLES12-SP1-Pool | Yes | (r ) Yes | No

2 | SMT-http_sles12s1_suse:SLES12-SP1-Updates | SLES12-SP1-Updates | Yes | (r ) Yes | Yes

Now the migration to SLES12-SP2/SP3 is available:

zypper migration

Executing ‘zypper refresh’

Repository ‘SLES12-SP1-Pool’ is up to date.

Repository ‘SLES12-SP1-Updates’ is up to date.

All repositories have been refreshed.

Executing ‘zypper –no-refresh patch-check –updatestack-only’

Loading repository data…

Reading installed packages…

0 patches needed (0 security patches)

Available migrations:

1 | SUSE Linux Enterprise Server 12 SP3 x86_64

2 | SUSE Linux Enterprise Server 12 SP2 x86_64



  • No Related Posts