on 01-20-2016 12:03 PM
Hi Experts,
Our Linux team told us that our "/ (Slash)" mount point of SOLMAN got 100% utilization so we told them to clear something and make the space available and we stopped the SAP and DB on SOLMAN machine. So they freed some space and after that when I am trying to start SAP instance of SOLMAN server but it is showing "Startup of Instance Service failed" and the logs shows as below.
SOLMAN:smdadm 48> startsap
Checking SMD Database
Database is running
-------------------------------------------
Starting Startup Agent sapstartsrv
FAIL: Timeout
Startup of Instance Service failed
See /home/smdadm/startsap_SCS01.log for details
-------------------------------------------
SOLMAN:smdadm 50> cat /home/smdadm/startsap_SCS01.log
Trace of system startup/check of SAP System SMD on Wed Jan 20 16:59:04 IST 2016
Called command: /usr/sap/SMD/SYS/exe/run/startsap start
-------------------------------------------
16:59:05
Starting Startup Agent sapstartsrv
-------------------------------------------
17:01:05
Startup of Instance Service failed
-------------------------------------------
17:01:05
See /home/smdadm/startsap_SCS01.log for details
Please suggest me what to do on this situation
Thanks in advanced.
Regards,
Musa.
Hi,
The problem should be the lock file permission.
please check the permission of the following hidden file:
/tmp/.sapstartsrv01_sapstartsrv.log
the default/correct permission should be "-rw-rw-rw- 1 <sid>adm sapsys" .
other permissions will cause "Unable to open trace file sapstartsrv.log. (Error 13 Permission denied) " error when you run
"sapstartsrv pf=/sapmnt/SMD/profile/START_SCS01_SOLMAN" command.
you can just delete /tmp/.sapstartsrv01_sapstartsrv.log file and it will be generated again when sapstartsrv service start again.
Thanks and best regards,
Shi Feng
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Feng,
I just saw your suggestion and found that the permission of sapstartsrv00_sapstartsrv.log and sapstartsrv01_sapstartsrv.log is root root
So now i am trying to delete it and will start the instance once again and will let you know the status very soon.
Thanks for your suggestion.
Regards,
Musaddik.
SOLUTION
Hey Feng,
Thanks a lot for your suggestion it solved my issue.
I deleted old log files below
sapstartsrv00_sapstartsrv.log
sapstartsrv01_sapstartsrv.log
which had root root permission and then gave command startsap.
The result is below.
SOLMAN:smdadm 45> startsap
Checking SMD Database
Database is not available via R3trans
-------------------------------------------
Trying to start SMD database ...
Log file: /home/smdadm/startdb.log
SMD database started
Starting Startup Agent sapstartsrv
OK
Instance Service on host SOLMAN started
-------------------------------------------
starting SAP Instance SCS01
Startup-Log is written to /home/smdadm/startsap_SCS01.log
-------------------------------------------
/usr/sap/SMD/SCS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function Start
Instance on host SOLMAN started
Starting Startup Agent sapstartsrv
OK
Instance Service on host SOLMAN started
-------------------------------------------
starting SAP Instance DVEBMGS00
Startup-Log is written to /home/smdadm/startsap_DVEBMGS00.log
-------------------------------------------
/usr/sap/SMD/DVEBMGS00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start
Instance on host SOLMAN started
Thanks Feng and everybody who gave their valuable thoughts on my problem.
May God Bless everybody.
Regards,
Musaddik.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
By the way, /tmp/.sapstartsrv01_sapstartsrv.log is the lock file for sapstartsrv, you must not delete it if there is sapstartsrv process already running, otherwise, there will be more than one sapstartsrv can be started.
Best regards,
Shi Feng
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SOLUTION
Hey Feng,
Thanks a lot for your suggestion it solved my issue.
I deleted old log files below
sapstartsrv00_sapstartsrv.log
sapstartsrv01_sapstartsrv.log
which had root root permission and then gave command startsap.
The result is below.
SOLMAN:smdadm 45> startsap
Checking SMD Database
Database is not available via R3trans
-------------------------------------------
Trying to start SMD database ...
Log file: /home/smdadm/startdb.log
SMD database started
Starting Startup Agent sapstartsrv
OK
Instance Service on host SOLMAN started
-------------------------------------------
starting SAP Instance SCS01
Startup-Log is written to /home/smdadm/startsap_SCS01.log
-------------------------------------------
/usr/sap/SMD/SCS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function Start
Instance on host SOLMAN started
Starting Startup Agent sapstartsrv
OK
Instance Service on host SOLMAN started
-------------------------------------------
starting SAP Instance DVEBMGS00
Startup-Log is written to /home/smdadm/startsap_DVEBMGS00.log
-------------------------------------------
/usr/sap/SMD/DVEBMGS00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start
Instance on host SOLMAN started
Thanks Feng and everybody who gave their valuable thoughts on my problem.
May God Bless everybody.
Regards,
Musaddik..
Dear RBK B,
I think there is a permission issue some where.
Just run the below command
sapstartsrv pf=<give the instance profile of SCS>
Paste the error here.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Ashutosh,
Please see the rights and permission of the sapstartsrv.log file.
SOLMAN:smdadm 32> ls -l /usr/sap/SMD/DVEBMGS00/work/sapstartsrv.log
-rw-r--r-- 1 smdadm sapsys 681 Jan 8 11:37 /usr/sap/SMD/DVEBMGS00/work/sapstartsrv.log
SOLMAN:smdadm 33> ls -l /usr/sap/SMD/SCS01/work/sapstartsrv.log
-rw-r--r-- 1 smdadm sapsys 673 Jan 8 11:37 /usr/sap/SMD/SCS01/work/sapstartsrv.log
Regards,
Musa
Hello,
SOLMAN:smdadm 10> sapstartsrv pf=/sapmnt/SMD/profile/START_SCS01_SOLMAN
Unable to open trace file sapstartsrv.log. (Error 13 Permission denied) [ntservsserver.cpp 3483]
What are the permissions of the /tmp folder?
The command "ls -lad /tmp" should return this.
If this has been changed, reset it to the default (usually "drwxrwxrwt").
Regards,
Isaías
Hi Musa,
has given the correct suggestion.
Kindly check the sapnote
1762827 - "Startup of Instance Service failed" in UNIX or Linux environment
With Regards
Ashutosh Chaturvedi
please attach sapstartsrv.log , stderr* logs , startsap.trc here.
best regards,
Manjunath Hanmantgad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Manjunath,
Please take a look at "sapstartsrv.log"
SOLMAN:smdadm 158> cat sapstartsrv.log
---------------------------------------------------
trc file: "sapstartsrv.log", trc level: 0, release: "720"
---------------------------------------------------
pid 7224
[Thr 47483764347440] Fri Jan 8 11:37:20 2016
No halib defined => HA support disabled
CCMS agent initialization for instance type DOUBLESTACK: return code 0.
CCMS agent start: return code 255.
Initializing SAPControl Webservice
Starting AutoRestart thread
SapSSLInit failed => https support disabled
Starting WebService thread
[Thr 1095481664] Fri Jan 8 11:37:22 2016
AutoRestart thread started
Webservice thread started, listening on port 50013
soap_bind failed, Webservice thread enters retry loop
Hi,
---------
Webservice thread started, listening on port 50013
soap_bind failed, Webservice thread enters retry loop
---------
==> Which indicate that sapstartsrv does not work correctly due to the fact that port 50013 is occupied by other process.
Please see 2208264 sap KBA for the root cause and solution.
2208264 - Sapstartsrv - Soap_bind failed
Best regards,
Shi Feng
Hi,
-------------------
Webservice thread started, listening on port 50013
soap_bind failed, Webservice thread enters retry loop
-------------------
this trace log indeed indicates that port 50013 was occupied by other process at that moment.
if you are sure that 50013 port is free and open now, I think you can try to start the system again.
Meanwhile, I just review all the history.
As far as I can see, the problem is that sapstartsrv of SCS01 instance could not be started.
however, as you mentioned, the sapstartsrv.log is as below:
=======================
... ...
Webservice thread started, listening on port 50013
soap_bind failed, Webservice thread enters retry loop
=======================
Normally, the HTTP port of sapstartsrv on SCS01 instance should be 50113, but not 50013, since SCS instance number is 01.
where did you get the sapstartsrv.log file ?
if you got it from /usr/sap/<SID>/SCS01/work/, maybe there are some problem of sapstartsrv service definition or SCS01 instance profile.
if system still can not be started with the same error, please also upload :
1)the result of command: ps -ef | grep sapstartsrv
2)all the profiles which under /sapmnt/<SID>/profile directory
Best regards,
Shi Feng
Hi Feng,
Again it failed. see
startsap
Checking SMD Database
Database is running
-------------------------------------------
Starting Startup Agent sapstartsrv
FAIL: Timeout
Startup of Instance Service failed
See /home/smdadm/startsap_SCS01.log for details
output of command ps -ef |grepsapstartsrv is
SOLMAN:smdadm 2> ps -ef |grep sapstartsrv
smdadm 26911 26634 0 13:46 pts/0 00:00:00 grep sapstartsrv
Feng,
Now which profile of the below your want
-rw-rw---- 1 smdadm sapsys 2297 Oct 18 2013 DEFAULT.BAK
-rwxrwxrwx 1 smdadm sapsys 2412 Oct 18 2013 DEFAULT.PFL
-rwxrwxrwx 1 smdadm sapsys 3544 Jul 9 2014 SMD_DVEBMGS00_SOLMAN
-rwxrwxrwx 1 smdadm sapsys 1395 Sep 27 2013 SMD_DVEBMGS00_SOLMAN.1
-rwxrwxrwx 1 smdadm sapsys 1453 Sep 27 2013 SMD_DVEBMGS00_SOLMAN.2
-rw-rw---- 1 smdadm sapsys 3194 Jul 9 2014 SMD_DVEBMGS00_SOLMAN.BAK
-rwxrwxrwx 1 smdadm sapsys 950 Oct 9 2013 SMD_SCS01_SOLMAN
-rwxrwxrwx 1 smdadm sapsys 3530 Oct 18 2013 START_DVEBMGS00_SOLMAN
-rwxrwxrwx 1 smdadm sapsys 1631 Sep 27 2013 START_SCS01_SOLMAN
Hello Rbk,
Please execute command sapcontrol -function StopService -nr 00 with SIDADM.
Confirm whether its stopped or not. If not kill the process and restart the system again.
Regards
Anand
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Musa,
Maybe this WIKI page can help you.
Regards,
Isaías
Hi Rbk B,
Just run the command
sapstartsrv pf=<location of start profile of SCS >
You will receive the exact message which is causing the TIMEOUT issue.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Sriram for your valuable reply
Q . Could you share the log /startsap_SCS01.log ??
Ans yes please see below.
SOLMAN:smdadm 50> cat /home/smdadm/startsap_SCS01.log
Trace of system startup/check of SAP System SMD on Wed Jan 20 16:59:04 IST 2016
Called command: /usr/sap/SMD/SYS/exe/run/startsap start
-------------------------------------------
16:59:05
Starting Startup Agent sapstartsrv
-------------------------------------------
17:01:05
Startup of Instance Service failed
-------------------------------------------
17:01:05
See /home/smdadm/startsap_SCS01.log for details
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.