saposcol problem

[Former Member]

hi experts

i upgraded ECC 6.0 kernel 111 to 179.but saposcol is not running after upgrading the kernel.it showing follwoing error in sto6

SAPOSCOL not running ? (shared memory not available )

the corresponding log file is

SAPOSCOL version COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16, 64 bit, single threaded, Non-Unicode

compiled at May 18 2007

systemid 390 (AMD/Intel x86_64 with Linux)

relno 7000

patch text COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16

patchno 111

intno 20050900

running on KARVY-DEV Linux 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:56:44 EST 2007 x86_64

19:42:33 30.12.2008 LOG: Profile : no profile used

19:42:33 30.12.2008 LOG: Saposcol Version : [COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16]

19:42:33 30.12.2008 LOG: Working directory : /usr/sap/tmp

19:42:33 30.12.2008 LOG: PRE UID = (501)

19:42:33 30.12.2008 LOG: PRE EUID = (0)

19:42:33 30.12.2008 LOG: Temporarily changing EUID for running sysctl

19:42:33 30.12.2008 LOG: UID = (501)

19:42:33 30.12.2008 LOG: EUID = (501)

19:42:33 30.12.2008 LOG: Resetting EUID after running sysctl

19:42:33 30.12.2008 LOG: UID = (501)

19:42:33 30.12.2008 LOG: EUID = (0)

19:42:33 30.12.2008 LOG: LINUX: statistics value of cpu_data->pages_in is zero.

19:42:33 30.12.2008 LOG: LINUX: statistics value of cpu_data->pages_out is zero.

19:42:33 30.12.2008 LOG: Shared Memory Size: 523670.

19:42:33 30.12.2008 LOG: Shared Memory was created by process:20201

19:42:33 30.12.2008 LOG: ==== Collector submitted. This is the parent process after fork.=====

19:42:36 30.12.2008 LOG: ==== Collector submitted. This is the child process after fork()=====

19:42:39 30.12.2008 LOG: Collector daemon started

19:42:39 30.12.2008 LOG: read coll.put Tue Dec 30 18:00:08 2008

19:42:39 30.12.2008 LOG: Collector PID: 20205

19:42:49 30.12.2008 LOG: Initialize Device Filtering

19:42:49 30.12.2008 LOG: Initialize Process Monitoring

19:42:49 30.12.2008 LOG: Process Monitoring active.

19:42:49 30.12.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc

19:42:49 30.12.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/

19:42:49 30.12.2008 LOG: The following processes will be monitored:

19:42:49 30.12.2008 LOG: Process: jlaunch-DSAPINFO=KDV_01_dispatcher* for user: kdvadm

19:42:49 30.12.2008 LOG: Process: jlaunch-DSAPINFO=KDV_01_server* for user: kdvadm

19:42:49 30.12.2008 LOG: Process: jlaunch-DSAPINFO=KDV_01_sdm* for user: kdvadm

19:42:49 30.12.2008 LOG: This Linux kernel operates at 100 HZ (compile-time HZ was 100).

can any one help for this

by

srinivas

[Former Member · Accepted solution]

Try to start SAPOSCOL from os level.

saposcol -l ( Launches the collector )

saposcol -s ( Displays the status of the collector)

Make sure that saposcol permission is 4775.

Run the following script from your kernel directly , it will fix the permissions and then start sap.

1. ./saproot.sh

Thanks,

Chandresh Pranami

[Former Member · Accepted solution]

hi Chandresh Pranami

i already i executed with root user after kernel up gradation but no use.but it is working in159 patch level.

[nelis · Accepted solution]

Run the following script from your kernel directly , it will fix the permissions and then start sap.
   1. ./saproot.sh

Just to add, after each kernel upgrade you need to run the above script as root to correct the permissions and you run it specifying the system ID.

./saproot.sh <SID>

Regards,

Nelis

[nelis · Accepted solution]

Whoops, when i posted the original msg I got an error and didn't think it went through so I kept trying..

Sorry for the repeats.

[nelis · Accepted solution]

Imaginary delete

[nelis · Accepted solution]

Imaginary delete

[Former Member]

I have a similar situation. Can anyone tell me the command to start the OS Collector on an iSeries?

[Former Member]

Hai,

If you have root access in the particular sever, login as root and go to /usr/sap/SID/SYS/exe and then execute ./saposcol, this will start the oscol with root user and check the permisson of the saposcol it should be with 4755.

Regards,

Yoganand.V