12-07-2006 12:11 PM
Dear all,
I'm looking for a way to deactivate the sapstart and sapstartsrv processes which keep running every time I stop the system (NW04s on AIX 5.2).
I checked the SAP notes 823941 and 936273 but they only explain how I can configure the SAP MMC better, but I'd like to get rid of it (as it's a security risk if someone knows the ports).
I tried it by removing the entry in /usr/sap/sapservices, but that didn't change anything.
Does anyone know what I can do that these processes would not be startet in the future?
Best regards
Cornelia
12-11-2006 10:30 AM
Hi Cornelia,
the sapstart program should terminate after the R/3 system has terminated. If this is not the case, some child process is still running. Please check, what other service did not stop in this case.
sapstartsrv get's started by startsap (even if not configured in /usr/sap/sapservices) and has to be shutdown after stopsap manually.
You can stop it with the following command (has to be exectued as SIDadm):
sapcontrol -nr <InstanzNummern> -function StopService
Regards,
Patrick
12-11-2006 10:30 AM
Hi Cornelia,
the sapstart program should terminate after the R/3 system has terminated. If this is not the case, some child process is still running. Please check, what other service did not stop in this case.
sapstartsrv get's started by startsap (even if not configured in /usr/sap/sapservices) and has to be shutdown after stopsap manually.
You can stop it with the following command (has to be exectued as SIDadm):
sapcontrol -nr <InstanzNummern> -function StopService
Regards,
Patrick
12-12-2006 7:29 AM
Hi,
just to avoid confusion, I did not say, that you should terminate either sapstartsrv nor sapstart while the R3 system is running, just as mentioned by Shaun, the restart from within NWA would not work anymore.
The statement was only, that AFTER the NWAS has been shut down, if you want to shut down sapstartsrv as well, you can use the command mentioned.
The sapstart executable should terminate immediatly after the NWAS has been stopped automaticaly.
In addition, if the issue is about the ports open by sapstartsrv, you can also bind them to localhost only by setting the property service/hostname (see <a href="https://service.sap.com/sap/support/notes/927637">Note 927637</a> for details).
Regards,
Patrick
12-12-2006 8:18 AM
Hello,
thanks for he information. But my problem is that I do not want sapstartsrv running neither when the system is running nor when it's down (we do not start or stop the systems by MMC or NWA).
As I only found information about how to configure it but not on how to stop it, I did the following:
I commented the entries in sapservices out and renamed sapstartsrv into _sapstartsrv.
When I restarted the system I got a message that it could not start the sapstartsrv, but the rest of the system started properly.
I'm pretty sure that's not the recommended way, but at least sapstartsrv is not running any more.
I was wondering if there's a parameter to set or some entry in the start profile to tell the system not to start that service...?
Best regards,
Cornelia
12-12-2006 9:02 AM
Hi Cornelia,
it's not clear to me, why you want to stop the sapstartsrv completly. Also I doubt that this is a supported configuration. Sapstartsrv is also used in controlling the cluster systems, therefor it has to be up, while the application server is running. Maybe you should ask this question in one of the other forums.
It is my understanding, that the security risk you mentioned initialy can be avoided by using good passwords (the service requires authentication) and binding it to localhost, if everthying is running on the local system.
Regards,
Patrick Hildenbrand
09-06-2007 5:14 PM
Just curious if you ever found a way to prevent this service from running?
Doyle
01-26-2010 12:12 PM
Hello,
You can stop it with the following command (has to be exectued as SIDadm):
sapcontrol -nr <InstanzNummern> -function StopService
I found two sapstartsrv rocesses (two instances?), one of them stops according to your advice, but another fails.
process:
/usr/sap/PROD1/SCS15/exe/sapstartsrv pf=/usr/sap/PROD1/SYS/profile/START_SCS15_host1 -D
# /usr/bin/su - prod1adm "-c /sapmnt/PROD1/exe/sapcontrol -nr 15 -function StopService"
26.01.2010 13:19:02
StopService
OK
another process:
/usr/sap/PROD1/SYS/exe/run/sapstartsrv pf=/usr/sap/PROD1/SYS/profile/START_DVEBMGS16_host1 -D
# /usr/bin/su - prod1adm "-c /usr/sap/PROD1/SYS/exe/run/sapcontrol -nr 16 -function StopService"
26.01.2010 13:25:23
StopService
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
Path to sapstartsrv is slightly different in second process. Anyway command fails. ( "-c /sapmnt/PROD1/exe/sapcontrol -nr 16 -function StopService" command also fails. )
How coud I resolve this ?
thanks
Vilius
12-12-2006 12:07 AM
Be careful before you remove the dameon(s) as they are there for a reason. Look at note 768727 as a starting point.
12-06-2010 9:25 PM
Hi.
Check ownership an permissions (s-bit) of /sapmnt/SID/exe/sapuxuserchk
-rwsr-x--- 1 root sapsys
See SAP note 927637 for details.
Regards
01-24-2011 8:57 PM
We are having the issue where the log for this sapstartsrv is HUGE...
4692211625 Jan 24 15:48 sapstartsrv.log
It is filled with the trace type data... I do not want this data... I am trying to use the command ...
sapcontrol -nr 42 -function StopService and it is not working...I just get the help for the sapcontrol command...
ahqscc1:ri0adm 35> ps -ef |grep ri0|grep sapsta
ri0adm 4118 1 0 Nov 9 ? 0:00 /usr/sap/RI0/DVEBMGS42/exe/sapstart pf=/usr/sap/RI0/SYS/profile/START_DVEBMGS42_ahqscc1
ri0adm 4666 1 0 Nov 9 ? 1:00 /usr/sap/RI0/ASCS41/exe/sapstartsrv pf=/usr/sap/RI0/SYS/profile/START_ASCS41_ahqscc1 -D -u ri0adm
ri0adm 4873 1 0 Nov 9 ? 16:51 /usr/sap/RI0/DVEBMGS42/exe/sapstartsrv pf=/usr/sap/RI0/SYS/profile/START_DVEBMGS42_ahqscc1 -D -u ri0adm
ri0adm 3782 1 0 Nov 9 ? 0:00 /usr/sap/RI0/ASCS41/exe/sapstart pf=/usr/sap/RI0/SYS/profile/START_ASCS41_ahqscc1
how can I stop the service and get the log file to clean up... we also have the issue where these processes are not stopping when we stop and SAP instance...they are very annoying.
01-25-2011 12:38 AM
If you don't want to start them on system start remove them from you init script (depending on your Unix flavor /etc/init.d or /etc/rc5.d or /etc/inittab).
Markus