cancel
Showing results for 
Search instead for 
Did you mean: 

SAPOSCOL NOT START

Former Member
0 Kudos

When I want to start the sap I get the next message:

"start of saposcol failed"

I´ve read that main a permissions problem, but i don´t know to do.

It´s necessary to start the saposcol for the working og the system?

Accepted Solutions (1)

Accepted Solutions (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Have you tried to start saposcol manually ?

Have you done kernel upgrade ? If yes, then after upgrade have you ran saproot.sh script ?

Thanks

Sunny

Former Member
0 Kudos

I´ve only and a installation of sap gateway.

I´ve applied the note 809477 - startsap/stopsap for SAP WebAs 640, 700, 701, 710, 711, 720 and restarted the server and now starts the saposcol.

But how can check that the sap gateway is running? What are the main services to see on command top?

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Try to start saposcol manually. You can check gateway by using command ps -ef and grep gateway process.

Thanks

Sunny

Former Member
0 Kudos

When start the saposcol manually, before / after the startsap?

But Which are the most typicals name services for gateway?

Former Member
0 Kudos

Have you upgrade the kernel?

you try apply the lastest patch for saposcol

Regards

William Neira

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

you can start saposcol after starting of SAP system.

ps -ef | grep gwrd command to check gateway process.

Thanks

Sunny

Former Member
0 Kudos

I don´t upgrade the kernell, only I have had the gateway installation.

I´ve donwloaded the last patch of saposcol, startsap and stopsap.

Former Member
0 Kudos

This is the output of ps -ef

sidadm@server:/sapmnt/GDD/exe> ps -ef | grep gwrd

sidadm 4124 3765 0 16:59 pts/0 00:00:00 grep gwrd

sidadm@server:/sapmnt/GDD/exe>

There are not launched,no?

Former Member
0 Kudos

Any information in the sapstart.log or saposcol.stdout logs in the work?

Regards

William Neira

Former Member
0 Kudos

If I do this ps -ef | grep sidadm

sidadm@server:/sapmnt/GDD/exe> ps -ef | grep sidadm

sidadm 3006 1 0 16:37 ? 00:00:00 /usr/sap/GDD/SYS/exe/run/sapstartsrv pf=/usr/sap/GDD/S YS/profile/START_G00_server -D -u sidadm

sidadm 3258 1 0 16:37 ? 00:00:00 sapstart pf=/usr/sap/GDD/SYS/profile/START_G00_server se

sidadm 3282 3258 0 16:37 ? 00:00:00 gw.sapGDD_G00 -mode=profile pf=/usr/sap/GDD/SYS/profil e/GDD_G00_server

root 3627 2818 0 16:39 ? 00:00:00 sshd: sidadm [priv]

sidadm 3630 3627 0 16:39 ? 00:00:00 sshd: sidadm@pts/0

sidadm 3631 3630 0 16:39 pts/0 00:00:00 -csh

sidadm 3765 3631 0 16:39 pts/0 00:00:00 bash

sidadm 4230 3765 99 17:08 pts/0 00:00:00 ps -ef

sidadm 4231 3765 0 17:08 pts/0 00:00:00 grep sidadm

sapstart.log

cat sapstart.log

SAP-R/3-Startup Program Rel 701 V1.8 (2003/04/24)

-


Starting at 2011/01/19 16:37:24

Startup Profile: "/usr/sap/GDD/SYS/profile/START_G00_server"

Setup Environment Variables

-


(3258) SETENV LD_LIBRARY_PATH=/usr/sap/GDD/SYS/exe/run:/usr/sap/GDD/SYS/exe/run

(3258) SETENV SHLIB_PATH=/usr/sap/GDD/SYS/exe/run:

(3258) SETENV LIBPATH=/usr/sap/GDD/SYS/exe/run:

Execute Pre-Startup Commands

-


(3263) Local: rm -f gw.sapGDD_G00

(3268) Local: ln -s -f /usr/sap/GDD/SYS/exe/run/gwrd gw.sapGDD_G00

Starting Programs

-


(3282) Starting: local gw.sapGDD_G00 -mode=profile pf=/usr/sap/GDD/SYS/profile/GDD_G00_server

(3258) Waiting for Child Processes to terminate.

(3282) New Child Process created.

(3282) Starting local Command:

Command: gw.sapGDD_G00

-mode=profile

pf=/usr/sap/GDD/SYS/profile/GDD_G00_server

System is already running. Process Id = 3258

(3998) Exiting with Return-Code 1. (Already running)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

> If I do this ps -ef | grep sidadm

>

> sidadm@server:/sapmnt/GDD/exe> ps -ef | grep sidadm

> sidadm 3006 1 0 16:37 ? 00:00:00 /usr/sap/GDD/SYS/exe/run/sapstartsrv pf=/usr/sap/GDD/S YS/profile/START_G00_server -D -u sidadm

> sidadm 3258 1 0 16:37 ? 00:00:00 sapstart pf=/usr/sap/GDD/SYS/profile/START_G00_server se

> sidadm 3282 3258 0 16:37 ? 00:00:00 gw.sapGDD_G00 -mode=profile pf=/usr/sap/GDD/SYS/profil e/GDD_G00_server

As per your logs, Your gateway is running.

Thanks

Sunny

nirmal_konchada
Active Contributor
0 Kudos

Hi,

What is your OS???

saposcol has a sticky bit permission.

Please check the permission of saposcol.

Regards,

Nirmal.K

Former Member
0 Kudos

Hi,

I´ve restarted the machine, and when I go to start the sap system via ./startsap , I get again the message "Start of saposcol failed"

Then I´ve execute the command ./saposcol -l for to start it and I get this message:

******************************************************************************

  • This is Saposcol Version COLL 20.95 701 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16

  • Usage: saposcol -l: Start OS Collector

  • saposcol -k: Stop OS Collector

  • saposcol -d: OS Collector Dialog Mode

  • saposcol -s: OS Collector Status

  • Starting collector (create new process)

******************************************************************************

I´ve filter by user in the top program and I´ve founded this entry:

sidadm 20 0 54884 15m 2164 S 0.0 0.4 0:00.18 sapstartsrv --> then the instance is up,not?

I

In the log dev_coll put this:

26.05.2011 LOG: PRE UID = (1001)

19:19:52 26.05.2011 LOG: PRE EUID = (0)

19:19:52 26.05.2011 LOG: Temporarily changing EUID for running sysctl

19:19:52 26.05.2011 LOG: UID = (1001)

19:19:52 26.05.2011 LOG: EUID = (1001)

19:19:52 26.05.2011 LOG: Resetting EUID after running sysctl

19:19:52 26.05.2011 LOG: UID = (1001)

19:19:52 26.05.2011 LOG: EUID = (0)

19:19:52 26.05.2011 LOG: LINUX: statistics value of cpu_data->pages_in is zero.

19:19:52 26.05.2011 LOG: LINUX: statistics value of cpu_data->pages_out is zero.

19:19:52 26.05.2011 LOG: Shared Memory Size: 517628.

19:19:52 26.05.2011 LOG: Shared Memory was created by process:7930

19:19:52 26.05.2011 LOG: ==== Collector submitted. This is the parent process after fork.=====

19:19:55 26.05.2011 LOG: ==== Collector submitted. This is the child process after fork()=====

19:19:58 26.05.2011 LOG: Collector daemon started

19:19:58 26.05.2011 LOG: read coll.put Thu May 26 19:16:36 2011

19:19:58 26.05.2011 LOG: Collector PID: 7934

19:20:08 26.05.2011 LOG: Initialize Device Filtering

19:20:08 26.05.2011 LOG: Initialize Process Monitoring

19:20:08 26.05.2011 LOG: Process Monitoring active.

Former Member
0 Kudos

Hi,

Try to start the SAPOSCOL process from ST06.

Regards

Praveen

Answers (0)