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 …
The post SLES11 SP4 notification while patching OES11 SP3 and OES2015 SP1 appeared first on Cool Solutions. Madhan
For anyone who is interested in Advanced Authentication integration with the Client for Open Enterprise Server, and/or has been using the first phase of Advanced Authentication integration that was delivered in March 2017 with Client for Open Enterprise Server 2 SP4 (IR6): A public beta build of the Client for Open Enterprise Server 2 SP4 …
The post Client for Open Enterprise Server 2 SP4 (IR11 Beta) is available with enhanced integration with Advanced Authentication appeared first on Cool Solutions. iajesh
Fresh installs of SLES for SAP Applications produce the following os-release syntax and products.d contents:-
————————————————————————————————————————————
# cat /etc/os-release
NAME=”SLES”
VERSION=”12″
VERSION_ID=”12″
PRETTY_NAME=”SUSE Linux Enterprise Server 12″
ID=”sles”
ANSI_COLOR=”0;32″
CPE_NAME=”cpe:/o:suse:sles:12″
/etc/products.d # ls -l
total 16
-rw-r–r– 1 root root 2705 Oct 14 2014 SLES.prod
-rw-r–r– 1 root root 2839 Apr 23 2015 SLES_SAP.prod
lrwxrwxrwx 1 root root 13 Apr 3 15:41 baseproduct -> SLES_SAP.prod
-rw-r–r– 1 root root 1598 Oct 2 2014 sle-ha.prod
——————————————————
# cat /etc/os-release
NAME=”SLES_SAP”
VERSION=”12-SP1″
VERSION_ID=”12.1.0.1″
PRETTY_NAME=”SUSE Linux Enterprise Server for SAP Applications 12 SP1″
ID=”sles_sap”
ANSI_COLOR=”0;32″
CPE_NAME=”cpe:/o:suse:sles_sap:12:sp1″
/etc/products.d # ls -l
total 8
-rw-r–r– 1 root root 2854 Mar 15 2017 SLES_SAP.prod
lrwxrwxrwx 1 root root 13 Apr 3 15:05 baseproduct -> SLES_SAP.prod
——————————————————
# cat /etc/os-release
NAME=”SLES_SAP”
VERSION=”12-SP2″
VERSION_ID=”12.2″
PRETTY_NAME=”SUSE Linux Enterprise Server for SAP Applications 12 SP2″
ID=”sles_sap”
ANSI_COLOR=”0;32″
CPE_NAME=”cpe:/o:suse:sles_sap:12:sp2″
/etc/products.d # ls -l
total 8
-rw-r–r– 1 root root 3080 Mar 30 2017 SLES_SAP.prod
lrwxrwxrwx 1 root root 13 Apr 3 13:11 baseproduct -> SLES_SAP.prod
——————————————————
# cat /etc/os-release
NAME=”SLES”
VERSION=”12-SP3″
VERSION_ID=”12.3″
PRETTY_NAME=”SUSE Linux Enterprise Server 12 SP3″
ID=”sles”
ANSI_COLOR=”0;32″
CPE_NAME=”cpe:/o:suse:sles_sap:12:sp3″
/etc/products.d # ls -l
total 8
-rw-r–r– 1 root root 2972 Jul 24 2017 SLES_SAP.prod
lrwxrwxrwx 1 root root 13 Apr 3 12:31 baseproduct -> SLES_SAP.prod
——————————————————
# cat /etc/os-release
NAME=”SLES”
VERSION=”15″
VERSION_ID=”15″
PRETTY_NAME=”SUSE Linux Enterprise Server 15″
ID=”sles”
ID_LIKE=”suse”
ANSI_COLOR=”0;32″
CPE_NAME=”cpe:/o:suse:sles:15″
linux-mpxw:~ #
/etc/products.d # ls -l
total 28
-rw-r–r– 1 root root 3185 May 30 05:23 SLES_SAP.prod
lrwxrwxrwx 1 root root 13 Oct 31 11:46 baseproduct -> SLES_SAP.prod
-rw-r–r– 1 root root 3197 May 30 05:23 sle-ha.prod
-rw-r–r– 1 root root 1892 May 30 05:23 sle-module-basesystem.prod
-rw-r–r– 1 root root 2264 May 30 05:23 sle-module-desktop-applications.prod
-rw-r–r– 1 root root 2315 May 30 05:23 sle-module-sap-applications.prod
-rw-r–r– 1 root root 2351 May 30 05:23 sle-module-server-applications.prod
——————————————————
This leaves us with the question ‘How do we identify the ‘base product’ of a server?”.
The correct way to do this is is by examining the contents of /etc/product.d directory (and look at which product file the link ‘baseproduct’ is pointing too).
I am pleased to announce the availability of a shiny and new ZENworks Reporting 6.4. This release comes with the following key things: New Jaspersoft 6.4.3 Reporting engine Update of underlying Appliance OS to SLES 12 SP3. New capabilities in Dashboards including support for hyperlinks in Dashlets and new formatting and editing options. New capabilities …
The post ZENworks Reporting 6.4 is now available! appeared first on Cool Solutions. gvikram
This document (7023378) is provided subject to the disclaimer at the end of this document.
clamclient:~ # freshclam -v
Current working dir is /var/lib/clamav
Max retries == 3
ClamAV update process started at Wed Sep 26 14:46:50 2018
Using IPv6 aware code
Querying current.cvd.clamav.net
TTL: 931
Software version from DNS: 0.100.1
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.100.0 Recommended version: 0.100.1
DON’T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
main.cvd version from DNS: 58
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cvd version from DNS: 24983
daily.cld is up to date (version: 24983, sigs: 2100133, f-level: 63, builder: raynman)
bytecode.cvd version from DNS: 327
bytecode.cld is up to date (version: 327, sigs: 91, f-level: 63, builder: neo)
clamclient:~/PTF-2018-Sep-07-09:38:00 # echo $?
1
According to man (1) freshclam, the exit status should be zero if the database was successfully refreshed or up-to-date.
Reported to Engineering
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.
This document (7023375) is provided subject to the disclaimer at the end of this document.
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.
This document (7023373) is provided subject to the disclaimer at the end of this document.
Subscription Management Tool
Error: Unable to request next job: 500 Access to ‘http’ URIs has been disabled-
The above error will also show on the Client when the smt-agent command is launched manually.
– On SUSE Linux Enterprise Server (SLES) 11 based Clients run:
# cp -p /etc/suseRegister.conf /etc/suseRegister.conf.BCK
– On SLES 12 and 15 based Clients run:
# cp -p /etc/SUSEConnect /etc/SUSEConnect.BCK
Then edit the file and change “http” for “https” (without the quotation marks) in the “url” line, so after the change the line should look as follows:
– On SLES 11 based Clients:
url=https://<YOUR-SMT-FQDN-HERE>/center/regsvc
– On SLES 12 and 15 based Clients:
url: https://<YOUR-SMT-FQDN-HERE>/
Save the changes and exit the editor.
Finally run the smt-agent command on the Client to check if the error is still showing up:
# smt-agent
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.
Warning: Digest verification failed for file ‘updateinfo.xml.gz’
[/var/cache/zypp/raw/susemanager:sles11-sp4-suse-manager-tools-x86_64qmNNht/repodata/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):
Download the following RPM file to the server running SUSE Linux Enterprise Server 15. It is not required that the system (the source system) be registered with SUSE Customer Center (SCC).
Install the RPM:
After installation run the interactive script and follow the on screen instructions:
NOTE: It is required to have your email address as well as a valid registration key for SUSE Linux Enterprise Server for SAP Applications (the target system) at hand.
# sudo /usr/sbin/Migrate_SLES_to_SLES-for-SAP.sh
NOTE: In case packages are installed that have dependencies against IBM Java, it may be needed to reinstall them at the end of the procedure.
A reboot of the system is not necessary unless packages which require a reboot are also installed from the newly added channels.
This document (7023356) is provided subject to the disclaimer at the end of this document.
zypper rm plymouth plymouth-dracut
zypper in blog blog-plymouthmkinitrd
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.