Outbound httpS with HANA XS (part 1) – set up your HANA box to use SSL/TLS
Intro
Hi everyone, welcome to my first blog!
It’s the first one in a series, accompanying you on your journey with HANA. Starting with the basic setup of your HANA box to use in- and outbound HTTP calls via Secure Sockets Layer (SSL) / Transport Layer Security (TLS), the blogs will help you advance step by step until you end up designing and implementing a complete XS application that calls an external HTTPS service.
- Outbound httpS with HANA XS (part 1) – set up your HANA box to use SSL/TLS
- Outbound httpS with HANA XS (part 2) – set up the trust relation
- Outbound httpS with HANA XS (part 3) – call the https outbound service in XS server side JavaScript (xsjs)
This is a rather advanced topic in the area of SAP HANA XS. Along the way, some of you may discover things you have not heard of before, such as .xsjs, .xshttpdest and trust stores. I will try to keep things as simple as possible and and will also keep trying to stimulate the appetites of XS newbies. If you’re hungry and looking for a good point to start from, you can try walking the Road to HANA for Software Developers, until you reach the REST for your Models on the SAP HANA XS vista point.
So let’s get started with the encryption thing by first setting up your HANA box.
Prerequisites
Depending on your individual setup, you may need to get a larger or smaller number of files. The basic requirement is to be able to download the SAP cryptographic library. For a more complex scenario involving a certification authority, you will also need the relevant root certificates. In my example, I am simply leveraging the SAP infrastructure for this.
Files
I would have liked to provide all the necessary files in this blog. Due to legal constraints, however, I’m unfortunately not allowed to do so. Nevertheless, it’s fairly easy to get them at:
- SAP cryptographic library / sapgenpse (command line tool)
- SAP Trust Center Services -> Download Area -> SAP Cryptographic Library -> Linux on x86_64 64bit
- SAP root certificates
- Trust center services-> Download Area -> Root CertificatesSAPNetCA
OS access
You need to be able to copy files to and access the HANA box as <sid>adm.
So, who is going to sign for this?
If you want to use https, you will usually need to deal with certification authorities and public key infrastructures (if you are completely new to this topic, please refer to other resources to get started). Another (easier and often cheaper) way is to sign the certificates on your own. While the external signing ensures real security (and that nice green status color in your browser without the need to resort to any hacks), the self-signing may be what you are looking for if you want to get your development environment up and running as quickly as possible.
I am going to provide shortcuts for setting it up either way. Nevertheless, here is the official documentation in case you’re interested:
- HANA Security guide (chapter 4.3.3)
- HANA Administration guide (chapter 15.3) – will become important later on
The easy way – self signing
You just want to set up your development box, but you don’t have certificates of a CA (Certification Authority) or your very own CA? Or maybe you just want to get it done on the fast track? If so, this is the right place for you!
The following script (also attached), will do all the work for you. Just set some parameters at the beginning, copy the above mentioned files (in section ‘Prerequisites’) to the working folder on your HANA host and relax after starting the script.
So here is what you need to do:
- Create a working folder containing the following files
- setUpSapCryptoSelfSigned.sh (main execution script, see below or attachment)
- sapgenpse
- libsapcrypto.so
- Edit the script and adapt the following parameters according to your needs
- INSTANCE='<YOUR_HANA_SID>’
- INSTNO='<YOUR_HANA_INST_NO>’
- HOST='<YOUR_HANA_NETWORK_HOST_WITHOUT_DOMAIN>’
- copy the folder to the HANA server, make the files readable and the script executable for <sid>adm
- run the script as <sid>adm
This is what needs to be executed:
setUpSapCryptoSelfSigned.sh
#!/bin/bash
read -p 'You NEED to run this script as <sid>adm
&& you need to set the variables in the script
If this is not the case abort here (Ctrl+C)'
INSTANCE='<YOUR_HANA_SID>'
INSTNO='<YOUR_HANA_INST_NO>'
HOST='<YOUR_HANA_NETWORK_HOST_WITHOUT_DOMAIN>'
#example
#INSTANCE='TES'
#INSTNO='40'
#HOST='pall00539444a'
# bash does not provide DIR_SECURITY_LIB inside this subshell
DIR_SECURITY_LIB="/usr/sap/$INSTANCE/SYS/global/security/lib"
cp libsapcrypto.so $DIR_SECURITY_LIB
cp sapgenpse $DIR_SECURITY_LIB
mkdir $SECUDIR
# Create the trust store files
$DIR_SECURITY_LIB/sapgenpse gen_pse -p $SECUDIR/sapsrv.pse -x '' "CN=${HOST}"
$DIR_SECURITY_LIB/sapgenpse gen_pse -p $SECUDIR/sapcli.pse -x '' "CN=${HOST}"
$DIR_SECURITY_LIB/sapgenpse gen_pse -p $SECUDIR/SAPSSL.pse -x '' "CN=${HOST}"
echo "Please note that all of these PSE files are self signed. In a productive scenario you would have to sign them by a CA."
echo "Going to update Web dispatcher profile and restarting that process"
echo "
wdisp/ssl_encrypt = 0
ssl/ssl_lib = /usr/sap/$INSTANCE/SYS/global/security/lib/libsapcrypto.so
ssl/server_pse = SAPSSL.pse
icm/HTTPS/verify_client = 0
icm/HTTPS/forward_ccert_as_header = true
" >> /usr/sap/$INSTANCE/HDB$INSTNO/$HOST/wdisp/sapwebdisp.pfl
kill -9 `pidof sapwebdisp_hdb`
kill -9 `pidof hdbxsengine`
echo "Now you may proceed with setting up your XS applications as described at
http://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdf
(Chapter 3.6 - maintaining application security)'
"
echo "You can check whether the https setup was successfull via
https://$HOST:43$INSTNO/sap/hana/xs/admin/
- you may need to wait a little bit for a restart of some processes
- you need the according roles
check: Go to the trust manager. If there is no error message on the bottom of the screen you are all setup."
# DEBUGGING
#
# Reset the system (pls adapt the wdisp.pfl on your own (not a must))
# rm -f $DIR_SECURITY_LIB/*; rm -f $SECUDIR/*; kill -9 `pidof sapwebdisp_hdb`; kill -9 `pidof hdbxsengine`
#
# Troubleshooting SSL for HANA/XS
#
# check the traces (dev_wdisp and xsengine) for errors (either via HANA Studio > Administration perspective > Diagnosis Files or in /usr/sap/<SID>/HDB<instno>/<host>/trace).
# increase the trace-level for the HDB Web Dispatcher by adding icm/log_level = <level> (e.g. 2) to sapwebdisp.pfl in /usr/sap/<SID>/HDB<instno>/<host>/wdisp.
# increase the trace level: In HANA Studio, Administration perspective > Trace Configuration, Edit Configuration for "Database Trace" and change XSENGINE to e.g. INFO.
#Troubleshooting SSL for HANA/XS
# In HANA Studio, open the Administration perspective for the HANA system and set the following configuration parameters in indexserver.ini, section communication:
# sslcryptoprivder = sapcrypto
# sslkeystore = /usr/sap/<SID>/HDB<instno>/<host>/sec/SAPSSL.pse
# ssltruststore = /usr/sap/<SID>/HDB<instno>/<host>/sec/SAPSSL.pse
# sslvalidatecertificate = false
# sslvalidatecertificate should be set to false, as most of the internal systems won't resolve the hostnames properly.
That’s it.
As the script already told you, you can check if https is working by opening the following URL in your browser (please mind the s in https and the changed port):
https://<yourHostName>:43<InstanceNumber>
You should now see something like:
using Firefox
using Chrome
After adding a security exception (via ‘I understand the risks’ or ‘Proceed anyway’ – depending on your browser) you most likely will discover the XS engine welcome screen:
Don’t be surprised if your browser does not trust that 
connection – you did sign the certificates yourself. If you don’t like this, just go on with the next (optional) sub-chapter.
In any case, inbound https should be up and running now. 🙂
Would you like to watch this whole process in a video? Here you go:
Hacking that red status (optional)
If that red status annoys you, I can show you how to get rid of it. But it is a hack of sorts, so just don’t tell anyone about it. It does have some security drawbacks and it most likely has to be done for every user.
In a nutshell:
Export the certificate via your browser and import it as a trusted root certificate.
Using Chrome, this can be done via:
Export
- click the red symbol
- tab: connection
- ‘certificate information’
- tab: Details
- button: copy to file
Import
- call ‘ chrome://settings/search#certificates ‘
- click ‘manage certificates’
- tab: trusted root certification authorities
- button: import
- choose and import the exported file
Depending on your cache settings, you should be able to just restart Chrome and see the green icon.
The delegated way – ask the CA to sign it
Ok, so you already have a connection to a CA, are not too happy about the red symbols in your browser and dislike the hack above due to its security drawbacks? Furthermore, you’re familiar with the whole security thing, or at least know someone who is and who owes you a favor? Fine, so let’s go ahead and use that CA infrastructure to become more secure and make sure you’re really communicating with whom you think you should be!
The following script is an enhanced version of the script above. At least, it’s enhanced with regards to some setup aspects and the interactive signing question.
You will be asked to have your created certificates be signed by a CA while the script is running. If you need to have an external CA sign them, then I recommend running the script steps manually. In general, this may be the safer option. I have only been looking at the SAP internal frontend, and I’m sure most frontends will look different and the certificate names might also be different. Anyway. I hope the basic steps can help you get the installation up and running.
Regarding the configuration described above, you will additionally have to perform the following steps:
- have to copy the SAPNetCA.cer root certificate (or the root certificate, you plan to use) into your working folder
- configure additional parameters at the beginning of the script:
- INSTANCE='<YOUR_HANA_SID>’
- SIDADM='<YOUR_HANA_SIDADM>’
- INSTNO='<YOUR_HANA_INST_NO>’
- HOST='<YOUR_HANA_NETWORK_HOST>’
- DOMAIN='<YOUR_HANA_NETWORK_DOMAIN>’
- ORG='<YOUR_CERTIFICATE_ORGNANIZATION>’
- COUNTRY='<YOUR_CERTIFICATE_COUNTRY>’
- leave the PIN unset (see the next sub chapter for details)
- PIN=”
NOTE: if you are using root certificate other than SAPNetCA.cer, then you will need to adapt the script accordingly.
Once you’re done with all these steps, you can then go ahead and execute the ..CA.. script.
setUpSapCryptoCAsigned.sh
#!/bin/bash
read -p 'You NEED to run this script as <sid>adm
&& you need to set the variables in the script
If this is not the case abort here (Ctrl+C)'
#INSTANCE='<YOUR_HANA_SID>'
#SIDADM='<YOUR_HANA_SIDADM>'
#INSTNO='<YOUR_HANA_INST_NO>'
#HOST='<YOUR_HANA_NETWORK_HOST>'
#DOMAIN='<YOUR_HANA_NETWORK_DOMAIN>'
#ORG='<YOUR_CERTIFICATE_ORGNANIZATION>'
#COUNTRY='<YOUR_CERTIFICATE_COUNTRY>'
#example
#INSTANCE='TES'
#SIDADM='tesadm'
#INSTNO='40'
#HOST='pall00539444a'
#DOMAIN='pal.sap.corp'
#ORG='SAP'
#COUNTRY='DE'
# PIN does not increase security significantly and it's not possible to load the certificate into memory with one being set
PIN=''
# bash does not provide DIR_SECURITY_LIB inside this subshell
DIR_SECURITY_LIB="/usr/sap/$INSTANCE/SYS/global/security/lib"
cp libsapcrypto.so $DIR_SECURITY_LIB
cp sapgenpse $DIR_SECURITY_LIB
cp SAPNetCA.cer $DIR_SECURITY_LIB
mkdir $SECUDIR
##########################################
# sapssl
##########################################
# Create the SSL key pair and the certificate request in $SECUDIR
# This creates the Personal Security Environment (SAPSSL.pse) and the corresponding certificate request (SAPSSL.req).
$DIR_SECURITY_LIB/sapgenpse get_pse -p $SECUDIR/SAPSSL.pse -x $PIN -r $SECUDIR/SAPSSL.req "CN=${HOST}.${DOMAIN}, OU=${INSTANCE}, O=$ORG, C=$COUNTRY"
cat $SECUDIR/SAPSSL.req
read -p "
Now go to your signing CA (SAP also offers CA services where you can have test certificates signed instantly at
http://service.sap.com/Trust
https://websmp106.sap-ag.de/SSLTest
) and sign the certificate.
In the SAP in house case it works like this:
- Go to https://secsrvtest.wdf.sap.corp/TCS/cgi-bin/secuWPCA.pl
- paste the content from SAPSSL.req (printed above) to the text area
- leave SAPNetCA as CA
- select 'certify the cert. req.' as command
- submit
- Copy the resulting certificate from the output (everything including -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----)
to a new text file (here: SAPSSL.cert) and save it to '$SECUDIR'
( here: $SECUDIR/SAPSSL.cert ) .
-> Hit <ENTER> when finished
"
#Import the certificate into the PSE:
$DIR_SECURITY_LIB/sapgenpse import_own_cert -c $SECUDIR/SAPSSL.cert -p $SECUDIR/SAPSSL.pse -x $PIN -r $DIR_SECURITY_LIB/SAPNetCA.cer
#Create a Credential File to enable access for HDB (which runs as <sid>adm) to the PSE: Use
$DIR_SECURITY_LIB/sapgenpse seclogin -p $SECUDIR/SAPSSL.pse -x $PIN -O $SIDADM
# and make the credentials file read only for <sid>adm
chmod 600 $SECUDIR/cred_v2
##########################################
# sapsrv
##########################################
$DIR_SECURITY_LIB/sapgenpse get_pse -p $SECUDIR/sapsrv.pse -x '' -r $SECUDIR/sapsrv.req "CN=${HOST}.${DOMAIN}, OU=${INSTANCE}, O=$ORG, C=$COUNTRY"
cat $SECUDIR/sapsrv.req
read -p "
Now go to your signing CA (SAP also offers CA services where you can have test certificates signed instantly at
http://service.sap.com/Trust
https://websmp106.sap-ag.de/SSLTest
) and sign the certificate.
In the SAP in house case it works like this:
- Go to https://secsrvtest.wdf.sap.corp/TCS/cgi-bin/secuWPCA.pl
- paste the content from sapsrv.req (printed above) to the text area
- leave SAPNetCA as CA
- select 'certify the cert. req.' as command
- submit
- Copy the resulting certificate from the output (everything including -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----)
to a new text file (sapsrv.cert) and save it to '$SECUDIR'
( $SECUDIR/sapsrv.cert ) .
-> Hit <ENTER> when finished
"
#Import the certificate into the PSE:
$DIR_SECURITY_LIB/sapgenpse import_own_cert -c $SECUDIR/sapsrv.cert -p $SECUDIR/sapsrv.pse -r $DIR_SECURITY_LIB/SAPNetCA.cer
#Create a Credential File to enable access for HDB (which runs as <sid>adm) to the PSE: Use
$DIR_SECURITY_LIB/sapgenpse seclogin -p $SECUDIR/sapsrv.pse -x $PIN -O $SIDADM
##########################################
# sapcli.pse
##########################################
$DIR_SECURITY_LIB/sapgenpse gen_pse -p $SECUDIR/sapcli.pse -x '' "CN=${HOST}.${DOMAIN}, OU=${INSTANCE}, O=$ORG, C=$COUNTRY"
##########################################
# Configure the HDB Web Dispatcher for SSL
##########################################
echo "
wdisp/ssl_encrypt = 0
ssl/ssl_lib = /usr/sap/$INSTANCE/SYS/global/security/lib/libsapcrypto.so
ssl/server_pse = SAPSSL.pse
icm/HTTPS/verify_client = 0
icm/HTTPS/forward_ccert_as_header = true
" >> /usr/sap/$INSTANCE/HDB$INSTNO/$HOST/wdisp/sapwebdisp.pfl
kill -9 `pidof sapwebdisp_hdb`
kill -9 `pidof hdbxsengine`
echo "Now you may proceed with setting up your XS applications as described at
http://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdf
(Chapter 3.6 - maintaining application security)'
"
echo "You can check whether the https setup was successfull via
https://$HOST$DOMAIN:43$INSTNO/sap/hana/xs/admin/
- you may need to wait a little bit for a restart of some processes
- you need the according roles
check: Go to the trust manager. If there is no error message on the bottom of the screen you are all setup."
# DEBUGGING
#
# Reset the system (pls adapt the wdisp.pfl on your own (not a must))
# rm -f $DIR_SECURITY_LIB/*; rm -f $SECUDIR/*; kill -9 `pidof sapwebdisp_hdb`; kill -9 `pidof hdbxsengine`
#
# Troubleshooting SSL for HANA/XS
#
# check the traces (dev_wdisp and xsengine) for errors (either via HANA Studio > Administration perspective > Diagnosis Files or in /usr/sap/<SID>/HDB<instno>/<host>/trace).
# increase the trace-level for the HDB Web Dispatcher by adding icm/log_level = <level> (e.g. 2) to sapwebdisp.pfl in /usr/sap/<SID>/HDB<instno>/<host>/wdisp.
# increase the trace level: In HANA Studio, Administration perspective > Trace Configuration, Edit Configuration for "Database Trace" and change XSENGINE to e.g. INFO.
#Troubleshooting SSL for HANA/XS
# In HANA Studio, open the Administration perspective for the HANA system and set the following configuration parameters in indexserver.ini, section communication:
# sslcryptoprivder = sapcrypto
# sslkeystore = /usr/sap/<SID>/HDB<instno>/<host>/sec/SAPSSL.pse
# ssltruststore = /usr/sap/<SID>/HDB<instno>/<host>/sec/SAPSSL.pse
# sslvalidatecertificate = false
# sslvalidatecertificate should be set to false, as most of the internal systems won't resolve the hostnames properly.
After following the interactive part of the script and making sure the whole process has executed successfully, you should see a green status on your https connection (assuming you have also installed the relevant root CA into your browser):
Do you prefer to see these steps in a video? Here you go:
Using a PIN for the Trust Stores
Using a PIN for the Trust Stores is not a good idea. This is because the PIN mechanism works on file system level and once the Trust Store gets loaded into memory it is not possible to unlock a Trust Store anymore. As there furthermore is no great benefit in enhanced security I highly recommend not to set one at all.
Check the installation
To finally verify that you have not only successfully installed SSL but also maintained the trust store relations in the correct way, you should do the following:
- Assign your user the role ‘sap.hana.xs.admin.roles::TrustStoreAdministrator’
- go to https://<yourFQDN>:43<InstNo>/sap/hana/xs/admin/
- navigate to ‘Trust Manager’
If you do not see this:
Then everything is fine 🙂
Debugging
If you have issues running the script, you can find more information on how to wipe the stuff you just did at the end of each script. You’ll also find some hints on how to set trace levels for analyzing more hard-to-find issues. Then, of course, there’s also the official documentation….
- HANA Security guide (chapter 4.3.3)
- HANA Administration guide (chapter 15.3) – will become important later on
Last words
So that was easy, wasn’t it? 😉
Honestly, I really hope things worked out for you as smoothly as they did for me. The CA signing setup is not an easy thing to do and remote support might be very hard (are you happy providing me with your <sid>adm user?). Nevertheless, I’m happy to help in any way that I can.
Ready to use this setup?
Check out the followup blog available at:
Outbound httpS with HANA XS (part 2) – set up the trust relation
DISCLAIMER:
Please be aware that several processes will be restarted during the script execution (the hard way). This might disturb others also working on the same box.
These scripts have run smoothly wherever they were tested. Nevertheless, you should be aware of what you are doing and are fully responsible for any side effects to your own system. Good luck! 😉
I configure SSL as steps in HANA administration guide, it seems all things go well.
But when I opened XS trust manger view, I can see message "No valid SAP Crytpto configuration", do you have any suggestion?
Hi
which admin guide did you use? I had issues with the SP6 guide and that's why I created these Posts.
I would suggest you try to follow the steps as described right here.
Best regards
kc
Thank you for this detailed guide. I am trying to follow it, however, the $SECUDIR variable seems to be undefined. Could you please tell me which should be its value?
Best regards,
Florian
Hi,
/usr/sap/<SID>/HDB<instance_nr>/<hostname>/sec/
You have to create sec dir
After successfully enabling SSL (I can now access https://fqn.host:4300/sap/hana/xs/admin/), I still see in the XS Admin's Trust Manager the "No valid SAP Crypto configuration" message. Any advice on how to fix/debug this?
Thank you
Please run script metioned in this blog.
I have already ran the script, after setting $LD_LIBRARY_PATH and $SECUDIR variables.
Something wrong with configuration, you should check sap hana trace dev_webdisp first.
Everything looks OK in dev_webdisp trace file as the following line is present:
= Success -- SapCryptoLib SSL ready!
Also, the PSE file seems to be correctly loaded and, as I said earlier, I can successfully access the XS Admin XSJS application using HTTPS.
I have also added the following parameters in HANA Studio, but I still get the "No valid SAP Crypto configuration" message
# sslcryptoprivder = sapcrypto
# sslkeystore = /usr/sap/<SID>/HDB<instno>/<host>/sec/SAPSSL.pse
# ssltruststore = /usr/sap/<SID>/HDB<instno>/<host>/sec/SAPSSL.pse
# sslvalidatecertificate = false
Any other ideas?
Did you restart the instance?
Was there a problem logged to the console while the script was running?
There was no problem logged when I ran the script.
I restarted only the following two processes: kill -9 `pidof sapwebdisp_hdb`; kill -9 `pidof hdbxsengine` as mentioned in the script. Should I have also restarted something else?
The warning message disappeared after I did a full system restart. Thank you for the hint.
Hi
usually a restart of the processes is enough. I guess the UI had caches the message.
Merry Christmas
Thanks a lot for this blog. This was very helpful. 🙂
Hi all,
this is the change log to the update today:
- removed the use of a PIN for the trust stores
Best regards
kc
Hey, anybody any idea what this might be:
The hostname in the "CN=" part of the myhost 31007 xsengine 33783 XsIpConnection Error IPConnection.cpp(158)
Server's Certificate does not match the hostname that was passed in via SapSSLSetTargetHostname()
I applied a SAP Note but without success.
HANA XS Social Media API Call (Twitter, Facebook) HTTP Traffic
Hi David
to my knowledge Twitter and Facebook both only support OAuth. So you'll have to wait until HANA supports this one as well.
If this is not the case the error message seems to describe the issue pretty good to me. What I understand is: Your certification chain is not correct.
Please read the Blog and you'll end up with a running github scenario.
Best regards
kc
You just made my day! I switched from IP target host to dns and it worked, which came to my mind because you said the cert chain is invaled.
For oauth I reused some "code", so I get a xsjslib which did the oauth part.
Thanks.
David
Hey David
happy to hear it is working and thanks for the flowers 🙂
Did you use any publicly available lib to do the OAuth handling?
Best regards
kc
Hello,
no it is not a public libary. I hope there will be an official sap approach in the near future for oauth inside hana xs applications.
greetings
david
Hello,
I have tried to follow the above steps of self signing. Also I tried with the following guide http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b45687-0613-3110-7183-de49e84a35b0?QuickLink=index&… But could not get the https running. When i restarted the web dispatcher service, I got some errors in trace files saying
*** ERROR => secussl_Create_SSL_CTX(): PSE "/usr/sap/HA0/HDB00/inblrllssc29/sec/SAPSSL.pse": unable to use! [ssslsecu.c 1896]
[Thr 140624459200256] secussl_Create_SSL_CTX: SSL_CTX_set_default_pse_by_name() failed --
[Thr 140624459200256] secude_error 1824 (0x00000720) = "Wrong or Missing PIN for PSE"
[Thr 140624459200256] >> ---------- Begin of Secude-SSL Errorstack ---------- >>
[Thr 140624459200256] ERROR in SSL_CTX_set_default_pse_by_name: (1824/0x0720) Wrong or Missing PIN for PSE : "/usr/sap/HA0/HDB00/inblrllssc29/sec/SAPSSL.pse"
[Thr 140624459200256] ERROR in ssl_set_pse: (1824/0x0720) Wrong or Missing PIN for PSE : "/usr/sap/HA0/HDB00/inblrllssc29/sec/SAPSSL.pse"
[Thr 140624459200256] ERROR in af_open: (1824/0x0720) Wrong or Missing PIN for PSE : "/usr/sap/HA0/HDB00/inblrllssc29/sec/SAPSSL.pse"
[Thr 140624459200256] ERROR in secsw_open: (1824/0x0720) Wrong or Missing PIN for PSE : "/usr/sap/HA0/HDB00/inblrllssc29/sec/SAPSSL.pse"
[Thr 140624459200256] ERROR in sec_parse_PSEInfo_cont: (1824/0x0720) Wrong or Missing PIN for PSE : "/usr/sap/HA0/HDB00/inblrllssc29/sec/SAPSSL.pse"
[Thr 140624459200256] << ---------- End of Secude-SSL Errorstack ----------
[Thr 140624459200256] *** ERROR => SapISSLAddCredential(): Error SSSLERR_PSE_ERROR trying to create SERVER Credential
[Thr 140624459200256] *** ERROR => Initialization of SSL library failed -- NO SSL available!
[Thr 140624459200256] =================================================
[Thr 140624459200256]
[Thr 140624459200256] <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_PSE_ERROR
[Thr 140624459200256] *** ERROR => IcmServInitSSL: SapSSLInit (rc=-40):
Please help!!!
Thanks & Regards,
Mahendra
Hi Mahendra,
please remove the erroneous files and run the self signing script as described above.
Best regards
kc
has anybody tried to make this work on revision 72?
I'm trying to get this to work on revision 72, but i can't seem to get rid of the "No valid SAP Crypto configuration" message in the XS Engine Trust Manager.
The WebDispatcher is running https without problems, but the XS Engine doesn't seem to get it (yet). The entire HANA has been restarted a number of times since the config, so that's not the solution.
Hi,
are you sure you completely followed the script?
Especially the
part?
Best regards
Kai-Christoph
No, I did not. My problem seemed to consist of two parts:
1. I had named my PSE's different, but the XS Engine seems to look specifically for a file called sapsrv.pse a(although the WebDispatcher picks it up just fine).
2. I had PSE's with a PIN on it, and this is something HANA also does not like.
I'm rebuilding it now, but I seem to have a problem getting the CR's signed. I used the SAP Trust Center Services for that, but the SSL test certificate part does not seem to have been migrated to the new TCS website. I'll keep you advised of my progress.....
Update 23-07:
I've created PINless PSE's on the HANA side called sapsrv.pse and sapcli.pse (self-signed as the TCS service for test certificates seems to have been discontinued). This works to some extend, as the error message in the Trust Manager is gone and I can create stores successfully. What still doesn't work though is access from the Fiori Launchapd to the XS Engine. We've installed a WebDispatcher to handle all traffic to the Fiori frontend, backend and XS Engine, and I can see all three systems in de WebDispatchers admin pages. A call from the Launchpad (Embedded Search) to the XS Engine will result in a popup for logon on the XS Engine.
I got the following error
ERROR in unix_dlopen(): dlopen("libsapcrypto.so") FAILED:
"libsapcrypto.so: cannot open shared object file: No such file or directory"
Loading of shared library "libsapcrypto.so" failed!
You might need to define the shared library search path LD_LIBRARY_PATH
I'm using this script on sp9. Can someone help me with that
Hi Levent,
I could not reproduce your issue.
SP9 comes with a self signed configuration by default. For the CA case the script worked for me as well -> You need to adapt small things like the process name of the web dispatcher, but this isn't the issue you describe.
SP9 comes with the common crypto lib. This one is located at $DIR_EXECUTABLE.
I hope this helps!
If not, please be more specific on your issue.
Thanks and best regards
kc
i got the same error on sp8
Hi Levent,
I wrote the Post using SP7. A lot of people got it working on SP8 and SP9.
I am happy to help, but as I do not know what your issue is:
Please provide a detailed description on how to reproduce your issue.
Also include your revision build version and anything which might help.
Thank you and best regards
Kai
Hi Kai-Christoph,
I'm experiencing issues as well when i want to setup SSL on SP9.
I modified the script accordingly replacing the webdisp process with the new hdbwebdisspatcher , but the problem i have is that the hdbwebdispatcher disappear and is not started again after the kill -9 and i don't know how to restart it.
eve na HDB stop + HDB start does not change anything
what commad shall i use to restart the hdbwebdispatcher ?
many thanks
Denis
Hi Denis,
the web dispatcher is started by the HANA daemon automatically whenever the daemon recognizes one of the processes stopped operating.
If there is an issue with the startup of the web dispatcher, you need to look into it's log/trace file located at
/usr/sap/<INST>/HDB<INSTno>/<HOST>/trace
-> webdispatcher_.....trc
Best regards
kc
here is the output i found in the alert file , and in the trace file.
what's going on ? how do i fix this ?
thanks ,
best
Denis
more webdispatcher_alert_vhcalhdbdb.trc
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.431538 e webdispatcher webdispatcher.cpp(00485) : Trying to create webdispatcher.ini. Error: File already exists!
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.431683 e webdispatcher webdispatcher.cpp(00101) : Exception during startup!
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.431689 e webdispatcher webdispatcher.cpp(00102) : exception 1: no.306101 (spine/webdispatcher/webdispatcher.cpp:486)
Profile migration failed! Configuration already migrated!
exception throw location:
1: 0x00007f355baf6fa2 in WebDispatcher::WebDispatcherService::migrateProfile()+0x130 at webdispatcher.cpp:486 (hdbwebdispatcher)
2: 0x00007f355baf86d9 in WebDispatcher::WebDispatcherService::handleConfigurationDuringStartup()+0x5 at webdispatcher.cpp:227 (hdbwebdispatcher)
3: 0x00007f355baf91ef in WebDispatcher::WebDispatcherService::startup()+0x2b at webdispatcher.cpp:90 (hdbwebdispatcher)
4: 0x00007f355bb0a4a3 in nlsui_main+0x930 at TrexService.cpp:681 (hdbwebdispatcher)
5: 0x00007f35599d1083 in System::mainWrapper(int, char**, char**)+0x30 at IsInMain.cpp:202 (libhdbbasis.so)
6: 0x00007f35579cfc16 in __libc_start_main+0xe2 (libc.so.6)
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.440091 e webdispatcher webdispatcher.cpp(00103) : Web Dispatcher could not been started!
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720644 e webdispatcher webdispatcherlib.cpp(00036) : Closing shared library failed:
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.738796 e webdispatcher webdispatcher.cpp(00485) : Trying to create webdispatcher.ini. Error: File already exists!
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.738956 e webdispatcher webdispatcher.cpp(00101) : Exception during startup!
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.738960 e webdispatcher webdispatcher.cpp(00102) : exception 1: no.306101 (spine/webdispatcher/webdispatcher.cpp:486)
Profile migration failed! Configuration already migrated!
exception throw location:
1: 0x00007fb6061effa2 in WebDispatcher::WebDispatcherService::migrateProfile()+0x130 at webdispatcher.cpp:486 (hdbwebdispatcher)
2: 0x00007fb6061f16d9 in WebDispatcher::WebDispatcherService::handleConfigurationDuringStartup()+0x5 at webdispatcher.cpp:227 (hdbwebdispatcher)
3: 0x00007fb6061f21ef in WebDispatcher::WebDispatcherService::startup()+0x2b at webdispatcher.cpp:90 (hdbwebdispatcher)
4: 0x00007fb6062034a3 in nlsui_main+0x930 at TrexService.cpp:681 (hdbwebdispatcher)
5: 0x00007fb6040ca083 in System::mainWrapper(int, char**, char**)+0x30 at IsInMain.cpp:202 (libhdbbasis.so)
6: 0x00007fb6020c8c16 in __libc_start_main+0xe2 (libc.so.6)
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.747226 e webdispatcher webdispatcher.cpp(00103) : Web Dispatcher could not been started!
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739815 e webdispatcher webdispatcherlib.cpp(00036) : Closing shared library failed:
sid-hdb:/usr/sap/HDB/HDB00/vhcalhdbdb/trace>
and in the trace file :
more webdispatcher_vhcalhdbdb.30006.000.trc
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.258648 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.258708 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.258720 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.258730 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.258732 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.258733 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.258736 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.268735 w Environment Environment.cpp(00295) : Changing environment set SSL_WITH_OPENSSL=0
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.289023 i webdispatcher webdispatcher.cpp(00481) : A file named sapwebdisp.pfl has been detected. Configuration has to be migrate
d to webdispatcher.ini before first startup!
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.289178 i webdispatcher webdispatcherprofilemigrator.h(00090) : Profile Migration: Backup of sapwebdisp.pfl saved to wdisp/sapweb
disp_pfl_has_been_migrated_to_webdispatcher_ini.
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.289554 i webdispatcher webdispatcherprofilemigrator.h(00094) : Profile Migration: Content of sapwebdisp.pfl migrated to webdispa
tcher.ini.
[12732]{-1}[-1/-1] 2015-04-06 19:47:55.334888 i webdispatcher webdispatcher.cpp(00357) : Generated profile:
# This profile has been generated from webdispatcher.ini.
# Do not change this file! The Web Dispatcher has to be configured in webdispatcher.ini!
# Use the HANA Studio to configure the Web Dispatcher!
SAPSYSTEM=00
SAPSYSTEMNAME=HDB
DIR_INSTANCE=/usr/sap/HDB/HDB00/vhcalhdbdb
DIR_EXECUTABLE=/usr/sap/HDB/HDB00/exe
icm/HTTP/hdb_0=TRUE
wdisp/add_client_protocol_header=1
wdisp/HTTP/use_pool_for_new_conn=1
icm/max_sockets=($(icm/max_conn) * 2)
icm/req_queue_len=6000
icm/min_threads=10
icm/max_threads=500
mpi/total_size_MB=(min(0.06 * $(icm/max_conn) + 50, 2000))
mpi/max_pipes=($(icm/max_conn) * 2)
wdisp/HTTP/max_pooled_con=($(icm/max_conn))
wdisp/HTTPS/max_pooled_con=0
wdisp/add_xforwardedfor_header=true
icm/HTTPS/forward_ccert_as_header=true
icm/HTTP/max_request_size_KB=-1
wdisp/use_heap_for_mpis=true
wdisp/HTTP/esid_support=false
wdisp/HTTP/jsessionid_tab_support =false
ipc/sem_mon_off=true
icm/ccms_monitoring=false
wdisp/system_0=SID=$(SAPSYSTEMNAME), EXTSRV=http://localhost:3$(SAPSYSTEM)08, SRCURL=/
icm/security_log=LOGFILE=$(DIR_INSTANCE)/trace/dev_icm_sec,MAXSIZEKB=500
icm/max_conn=2000
icm/server_port_0=PROT=HTTP,PORT=80$(SAPSYSTEM),PROCTIMEOUT=600
icm/server_port_1=PROT=HTTPS,PORT=43$(SAPSYSTEM),PROCTIMEOUT=600
icm/HTTP/admin_0=PREFIX=/sap/hana/xs/wdisp/admin,DOCROOT=$(DIR_INSTANCE)/wdisp/admin,AUTHFILE=backend
[12732]{-1}[-1/-1] 2015-04-06 19:47:58.669105 w Environment Environment.cpp(00295) : Changing environment set IMSLERRPATH=/usr/sap/HDB/HDB00/exe//
[12732]{-1}[-1/-1] 2015-04-06 19:47:58.669128 w Environment Environment.cpp(00295) : Changing environment set IMSLSERRPATH=/usr/sap/HDB/HDB00/exe//
[12732]{-1}[-1/-1] 2015-04-06 19:47:58.881384 i webdispatcher webdispatcher.cpp(00453) : Developer Trace will be written to: /usr/sap/HDB/HDB00/vhcalhdbdb/trace/webdis
patcher_vhcalhdbdb.30006_dev_webdisp
[12732]{-1}[-1/-1] 2015-04-06 19:47:58.882375 i webdispatcher webdispatcher.cpp(00098) : Service startup
[12747]{-1}[-1/-1] 2015-04-06 19:47:58.882572 i webdispatcher webdispatcher.cpp(00661) : Starting Web Dispatcher with following arguments: hdbwebdispatcher pf=/usr/sap
/HDB/HDB00/vhcalhdbdb/tmp/temp_sapwebdisp_do_not_change.pfl -f /usr/sap/HDB/HDB00/vhcalhdbdb/trace/webdispatcher_vhcalhdbdb.30006_dev_webdisp
[12747]{-1}[-1/-1] 2015-04-06 19:48:02.160016 i webdispatcher webdispatcher.cpp(00531) : Web Dispatcher Initialization successful
[12732]{-1}[-1/-1] 2015-04-06 19:48:02.161437 i webdispatcher webdispatcher.cpp(00175) : Notified Daemon about startup
[12732]{-1}[-1/-1] 2015-04-06 19:48:02.178062 i webdispatcher webdispatcher.cpp(00170) : Notified Nameserver about startup
[12732]{-1}[-1/-1] 2015-04-06 19:48:02.178073 i webdispatcher webdispatcher.cpp(00116) : Service started
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.401434 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.401491 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.401503 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.401516 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.401518 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.401521 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.401523 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.411449 w Environment Environment.cpp(00295) : Changing environment set SSL_WITH_OPENSSL=0
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.431517 i webdispatcher webdispatcher.cpp(00481) : A file named sapwebdisp.pfl has been detected. Configuration has to be migrate
d to webdispatcher.ini before first startup!
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.431538 e webdispatcher webdispatcher.cpp(00485) : Trying to create webdispatcher.ini. Error: File already exists!
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.431683 e webdispatcher webdispatcher.cpp(00101) : Exception during startup!
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.431689 e webdispatcher webdispatcher.cpp(00102) : exception 1: no.306101 (spine/webdispatcher/webdispatcher.cpp:486)
Profile migration failed! Configuration already migrated!
exception throw location:
1: 0x00007f355baf6fa2 in WebDispatcher::WebDispatcherService::migrateProfile()+0x130 at webdispatcher.cpp:486 (hdbwebdispatcher)
2: 0x00007f355baf86d9 in WebDispatcher::WebDispatcherService::handleConfigurationDuringStartup()+0x5 at webdispatcher.cpp:227 (hdbwebdispatcher)
3: 0x00007f355baf91ef in WebDispatcher::WebDispatcherService::startup()+0x2b at webdispatcher.cpp:90 (hdbwebdispatcher)
4: 0x00007f355bb0a4a3 in nlsui_main+0x930 at TrexService.cpp:681 (hdbwebdispatcher)
5: 0x00007f35599d1083 in System::mainWrapper(int, char**, char**)+0x30 at IsInMain.cpp:202 (libhdbbasis.so)
6: 0x00007f35579cfc16 in __libc_start_main+0xe2 (libc.so.6)
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.440091 e webdispatcher webdispatcher.cpp(00103) : Web Dispatcher could not been started!
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.440100 i webdispatcher webdispatcher.cpp(00191) : Trigger service stop!
[23999]{-1}[-1/-1] 2015-04-07 16:32:44.440133 i Service_Shutdown TrexService.cpp(00781) : Preparing for shutting service down
[24009]{-1}[-1/-1] 2015-04-07 16:32:47.504768 w Environment Environment.cpp(00295) : Changing environment set IMSLERRPATH=/usr/sap/HDB/HDB00/exe//
[24009]{-1}[-1/-1] 2015-04-07 16:32:47.504799 w Environment Environment.cpp(00295) : Changing environment set IMSLSERRPATH=/usr/sap/HDB/HDB00/exe//
[24009]{-1}[-1/-1] 2015-04-07 16:32:47.712890 i webdispatcher webdispatcher.cpp(00181) : Notified Nameserver about shutdown preparation
[24009]{-1}[-1/-1] 2015-04-07 16:32:47.712899 i webdispatcher webdispatcher.cpp(00147) : Web Dispatcher Shutdown initiated!
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713089 i Service_Shutdown TrexService.cpp(00840) : Disabling signal handler
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713100 i Service_Shutdown TrexService.cpp(00852) : Stopping self watchdog
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713102 i Service_Shutdown TrexService.cpp(00864) : Stopping request dispatcher
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713104 i Service_Shutdown TrexService.cpp(00871) : Stopping responder
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713111 i Service_Shutdown TrexService.cpp(00878) : Stopping channel waiter
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713122 i Service_Shutdown TrexService.cpp(00883) : Shutting service down
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713125 i webdispatcher webdispatcher.cpp(00151) : Waiting for Web Dispatcher Shutdown ...
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713635 i webdispatcher webdispatcher.cpp(00187) : Notified Nameserver about shutdown
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713643 i Service_Shutdown TrexService.cpp(00888) : Stopping threads
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.713711 i Service_Shutdown TrexService.cpp(00893) : Stopping communication
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720602 i Service_Shutdown TrexService.cpp(00900) : Deleting console
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720608 i Service_Shutdown TrexService.cpp(00908) : Deleting self watchdog
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720610 i Service_Shutdown TrexService.cpp(00916) : Deleting request dispatcher
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720612 i Service_Shutdown TrexService.cpp(00924) : Deleting responder
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720631 i Service_Shutdown TrexService.cpp(00932) : Deleting service
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720644 e webdispatcher webdispatcherlib.cpp(00036) : Closing shared library failed:
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720650 i Service_Shutdown TrexService.cpp(00939) : Deleting threads
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720652 i Service_Shutdown TrexService.cpp(00945) : Deleting pools
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720659 i Service_Shutdown TrexService.cpp(00955) : Deleting configuration
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720661 i Service_Shutdown TrexService.cpp(00959) : Removing pidfile
[23999]{-1}[-1/-1] 2015-04-07 16:32:47.720916 i Service_Shutdown TrexService.cpp(00996) : System down
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.705363 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.705440 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.705454 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.705464 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.705466 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.705467 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.705469 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.717170 w Environment Environment.cpp(00295) : Changing environment set SSL_WITH_OPENSSL=0
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.738767 i webdispatcher webdispatcher.cpp(00481) : A file named sapwebdisp.pfl has been detected. Configuration has to be migrate
d to webdispatcher.ini before first startup!
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.738796 e webdispatcher webdispatcher.cpp(00485) : Trying to create webdispatcher.ini. Error: File already exists!
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.738956 e webdispatcher webdispatcher.cpp(00101) : Exception during startup!
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.738960 e webdispatcher webdispatcher.cpp(00102) : exception 1: no.306101 (spine/webdispatcher/webdispatcher.cpp:486)
Profile migration failed! Configuration already migrated!
exception throw location:
1: 0x00007fb6061effa2 in WebDispatcher::WebDispatcherService::migrateProfile()+0x130 at webdispatcher.cpp:486 (hdbwebdispatcher)
2: 0x00007fb6061f16d9 in WebDispatcher::WebDispatcherService::handleConfigurationDuringStartup()+0x5 at webdispatcher.cpp:227 (hdbwebdispatcher)
3: 0x00007fb6061f21ef in WebDispatcher::WebDispatcherService::startup()+0x2b at webdispatcher.cpp:90 (hdbwebdispatcher)
4: 0x00007fb6062034a3 in nlsui_main+0x930 at TrexService.cpp:681 (hdbwebdispatcher)
5: 0x00007fb6040ca083 in System::mainWrapper(int, char**, char**)+0x30 at IsInMain.cpp:202 (libhdbbasis.so)
6: 0x00007fb6020c8c16 in __libc_start_main+0xe2 (libc.so.6)
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.747226 e webdispatcher webdispatcher.cpp(00103) : Web Dispatcher could not been started!
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.747235 i webdispatcher webdispatcher.cpp(00191) : Trigger service stop!
[26464]{-1}[-1/-1] 2015-04-07 16:53:05.747349 i Service_Shutdown TrexService.cpp(00781) : Preparing for shutting service down
[26489]{-1}[-1/-1] 2015-04-07 16:53:09.512488 w Environment Environment.cpp(00295) : Changing environment set IMSLERRPATH=/usr/sap/HDB/HDB00/exe//
[26489]{-1}[-1/-1] 2015-04-07 16:53:09.512518 w Environment Environment.cpp(00295) : Changing environment set IMSLSERRPATH=/usr/sap/HDB/HDB00/exe//
[26489]{-1}[-1/-1] 2015-04-07 16:53:09.730193 i webdispatcher webdispatcher.cpp(00181) : Notified Nameserver about shutdown preparation
[26489]{-1}[-1/-1] 2015-04-07 16:53:09.730204 i webdispatcher webdispatcher.cpp(00147) : Web Dispatcher Shutdown initiated!
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.730378 i Service_Shutdown TrexService.cpp(00840) : Disabling signal handler
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.730390 i Service_Shutdown TrexService.cpp(00852) : Stopping self watchdog
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.730392 i Service_Shutdown TrexService.cpp(00864) : Stopping request dispatcher
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.730394 i Service_Shutdown TrexService.cpp(00871) : Stopping responder
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.730402 i Service_Shutdown TrexService.cpp(00878) : Stopping channel waiter
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.730410 i Service_Shutdown TrexService.cpp(00883) : Shutting service down
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.730413 i webdispatcher webdispatcher.cpp(00151) : Waiting for Web Dispatcher Shutdown ...
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.731134 i webdispatcher webdispatcher.cpp(00187) : Notified Nameserver about shutdown
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.731142 i Service_Shutdown TrexService.cpp(00888) : Stopping threads
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.732029 i Service_Shutdown TrexService.cpp(00893) : Stopping communication
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739761 i Service_Shutdown TrexService.cpp(00900) : Deleting console
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739774 i Service_Shutdown TrexService.cpp(00908) : Deleting self watchdog
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739776 i Service_Shutdown TrexService.cpp(00916) : Deleting request dispatcher
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739778 i Service_Shutdown TrexService.cpp(00924) : Deleting responder
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739800 i Service_Shutdown TrexService.cpp(00932) : Deleting service
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739815 e webdispatcher webdispatcherlib.cpp(00036) : Closing shared library failed:
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739821 i Service_Shutdown TrexService.cpp(00939) : Deleting threads
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739823 i Service_Shutdown TrexService.cpp(00945) : Deleting pools
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739832 i Service_Shutdown TrexService.cpp(00955) : Deleting configuration
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.739833 i Service_Shutdown TrexService.cpp(00959) : Removing pidfile
[26464]{-1}[-1/-1] 2015-04-07 16:53:09.740087 i Service_Shutdown TrexService.cpp(00996) : System down
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096549 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096662 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096681 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096698 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096702 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096706 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096709 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096713 e Configuration ConfigStoreManager.cpp(00693) : Configuration directory does not exist.
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.096716 e Configuration ConfigStoreManager.cpp(00693) : Configuration directory does not exist.
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.107401 w Environment Environment.cpp(00295) : Changing environment set SSL_WITH_OPENSSL=0
[27346]{-1}[-1/-1] 2015-04-07 17:06:02.180637 i webdispatcher webdispatcher.cpp(00357) : Generated profile:
# This profile has been generated from webdispatcher.ini.
# Do not change this file! The Web Dispatcher has to be configured in webdispatcher.ini!
# Use the HANA Studio to configure the Web Dispatcher!
SAPSYSTEM=00
SAPSYSTEMNAME=HDB
DIR_INSTANCE=/usr/sap/HDB/HDB00/vhcalhdbdb
DIR_EXECUTABLE=/usr/sap/HDB/HDB00/exe
icm/HTTP/hdb_0=TRUE
wdisp/add_client_protocol_header=1
wdisp/HTTP/use_pool_for_new_conn=1
icm/max_sockets=($(icm/max_conn) * 2)
icm/req_queue_len=6000
icm/min_threads=10
icm/max_threads=500
mpi/total_size_MB=(min(0.06 * $(icm/max_conn) + 50, 2000))
mpi/max_pipes=($(icm/max_conn) * 2)
wdisp/HTTP/max_pooled_con=($(icm/max_conn))
wdisp/HTTPS/max_pooled_con=0
wdisp/add_xforwardedfor_header=true
icm/HTTP/max_request_size_KB=-1
wdisp/use_heap_for_mpis=true
wdisp/HTTP/esid_support=false
wdisp/HTTP/jsessionid_tab_support =false
ipc/sem_mon_off=true
icm/ccms_monitoring=false
wdisp/system_0=SID=$(SAPSYSTEMNAME), EXTSRV=http://localhost:3$(SAPSYSTEM)08, SRCURL=/
icm/security_log=LOGFILE=$(DIR_INSTANCE)/trace/dev_icm_sec,MAXSIZEKB=500
icm/max_conn=2000
icm/server_port_0=PROT=HTTP,PORT=80$(SAPSYSTEM),PROCTIMEOUT=600
icm/server_port_1=PROT=HTTPS,PORT=43$(SAPSYSTEM),PROCTIMEOUT=600
icm/HTTP/admin_0=PREFIX=/sap/hana/xs/wdisp/admin,DOCROOT=$(DIR_INSTANCE)/wdisp/admin,AUTHFILE=backend
wdisp/ssl_encrypt=0
ssl/ssl_lib=/usr/sap/HDB/SYS/global/security/lib/libsapcrypto.so
ssl/server_pse=SAPSSL.pse
icm/HTTPS/verify_client=1
icm/HTTPS/forward_ccert_as_header=true
[27346]{-1}[-1/-1] 2015-04-07 17:06:05.422832 w Environment Environment.cpp(00295) : Changing environment set IMSLERRPATH=/usr/sap/HDB/HDB00/exe//
[27346]{-1}[-1/-1] 2015-04-07 17:06:05.422858 w Environment Environment.cpp(00295) : Changing environment set IMSLSERRPATH=/usr/sap/HDB/HDB00/exe//
[27346]{-1}[-1/-1] 2015-04-07 17:06:05.638325 i webdispatcher webdispatcher.cpp(00453) : Developer Trace will be written to: /usr/sap/HDB/HDB00/vhcalhdbdb/trace/webdis
patcher_vhcalhdbdb.30006_dev_webdisp
[27346]{-1}[-1/-1] 2015-04-07 17:06:05.639408 i webdispatcher webdispatcher.cpp(00098) : Service startup
[27353]{-1}[-1/-1] 2015-04-07 17:06:05.639702 i webdispatcher webdispatcher.cpp(00661) : Starting Web Dispatcher with following arguments: hdbwebdispatcher pf=/usr/sap
/HDB/HDB00/vhcalhdbdb/tmp/temp_sapwebdisp_do_not_change.pfl -f /usr/sap/HDB/HDB00/vhcalhdbdb/trace/webdispatcher_vhcalhdbdb.30006_dev_webdisp
[27346]{-1}[-1/-1] 2015-04-07 17:06:05.719226 w Environment Environment.cpp(00268) : Changing environment set LINES=42
[27346]{-1}[-1/-1] 2015-04-07 17:06:05.719252 w Environment Environment.cpp(00268) : Changing environment set COLUMNS=117
[27353]{-1}[-1/-1] 2015-04-07 17:06:08.843471 i webdispatcher webdispatcher.cpp(00531) : Web Dispatcher Initialization successful
[27346]{-1}[-1/-1] 2015-04-07 17:06:08.844535 i webdispatcher webdispatcher.cpp(00175) : Notified Daemon about startup
[27346]{-1}[-1/-1] 2015-04-07 17:06:08.847503 i webdispatcher webdispatcher.cpp(00170) : Notified Nameserver about startup
[27346]{-1}[-1/-1] 2015-04-07 17:06:08.847510 i webdispatcher webdispatcher.cpp(00116) : Service started
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544500 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544563 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544575 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544594 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544596 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544604 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544606 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544615 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[27980]{-1}[-1/-1] 2015-04-07 17:11:46.544617 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 27980'
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831454 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831511 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831522 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831532 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831534 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831536 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831538 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831541 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[30297]{-1}[-1/-1] 2015-04-07 17:27:21.831543 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 30297'
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054846 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054902 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054913 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054927 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054929 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054931 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054933 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054938 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[31419]{-1}[-1/-1] 2015-04-07 17:46:19.054939 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 31419'
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319309 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319365 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319376 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319390 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319392 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319394 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319396 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319401 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[32050]{-1}[-1/-1] 2015-04-07 17:56:29.319402 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 32050'
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041804 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041880 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041896 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041913 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041916 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041921 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041924 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041931 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[32089]{-1}[-1/-1] 2015-04-07 17:57:44.041934 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 32089'
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520265 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520320 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520333 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520345 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520347 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520350 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520352 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520356 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[32127]{-1}[-1/-1] 2015-04-07 17:58:22.520358 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 32127'
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025335 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel),
build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45)
4.7.2 20130108 [gcc-4_7-branch revision 195014]
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025391 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025402 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025413 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025415 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025417 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025419 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025422 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandHan
dle
[750]{-1}[-1/-1] 2015-04-07 18:10:22.025424 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 750'
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780243 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780298 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780310 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780323 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780325 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780328 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780329 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780334 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[16795]{-1}[-1/-1] 2015-04-08 07:35:36.780336 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 16795'
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.916922 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.916978 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.916989 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.917002 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.917004 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.917007 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.917009 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.917013 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[18742]{-1}[-1/-1] 2015-04-08 08:03:34.917015 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 18742'
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621045 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621101 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621111 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621125 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621126 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621129 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621131 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621136 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[18944]{-1}[-1/-1] 2015-04-08 08:08:41.621137 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 18944'
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711750 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711804 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711815 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711828 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711830 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711833 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711835 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711839 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[18958]{-1}[-1/-1] 2015-04-08 08:08:53.711841 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 18958'
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534434 i Basis TraceStream.cpp(00467) : ==== Starting hdbwebdispatcher, version 1.00.090.00.1416514886 (fa/newdb100_rel)
, build linuxx86_64 5c1aab7f333c2f0fd1620f48fc8fd981243681c3 2014-11-20 21:28:41 ld7272.wdf.sap.corp gcc (SAP release 20140516, based on SUSE gcc47-4.7.2_20130108-0.15.45
) 4.7.2 20130108 [gcc-4_7-branch revision 195014]
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534490 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534501 i Basis TraceStream.cpp(00472) : Server Mode: L2 Delta
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534512 i Basis ProcessorInfo.cpp(00713) : Using GDT segment limit to determine current CPU ID
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534513 i Basis Timer.cpp(00650) : Using RDTSC for HR timer
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534515 i Memory AllocatorImpl.cpp(01326) : Allocators activated
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534517 i Memory AllocatorImpl.cpp(01342) : Using big block segment size 134217728
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534522 w Basis ChannelListener.cpp(00101) : Unable to create socket for name: hdbwebdispatcher_SHDB_I00_ExternalCommandH
andle
[19717]{-1}[-1/-1] 2015-04-08 08:17:36.534523 w Basis ChannelListener.cpp(00101) : Application for this process will only work with 'hdbcons -p 19717'
sid-hdb:/usr/sap/HDB/HDB00/vhcalhdbdb/trace>
nice, very good explained