SAPOSCOL failed to start Cannot create Shared Memory

[Former Member]

Hello All,

We are facing problems while starting saposcol:

<b>Error in dev_coll file is :</b>

04:31:42 30.07.2007 LOG: Architecture identified as 64-bit

04:31:43 30.07.2007 LOG: Shared Memory Size: 1998236.

04:31:43 30.07.2007 LOG: Connected to existing shared memory.

04:31:43 30.07.2007 LOG: MaxRecords = 18852 <> RecordCnt + Dta_offset = 18787 + 61

04:31:48 30.07.2007 WARNING: WaitFree: could not set new shared memory status after 5 sec

04:31:48 30.07.2007 WARNING: Cannot create Shared Memory

In /usr/sap/tmp , I can see the file coll.put

Also sidadm(rwx) has execute (-rwxr-xr-x) permission for saposcol.

<b>saposcol version:</b>

SAPOSCOL version COLL 20.93 700 - V2.5.4 2006-12-04 HP-UX PA-RISC, 64 bit, single threaded, Non-Unicode

Can somebody give us hint.Thanks.

Regards,

Tushar

Message was edited by:

Tushar Chavan

[Former Member · Accepted solution]

Hello Tushar,

The operating system collector SAPOsCol is a stand-alone program that runs in the operating system background. It runs independently of

SAPinstances exactly once per host.Saposcol is not Unicode-dependent, so it makes no difference to download it from Unicode or Non-unicode

directory on Service Market Place.The highest available saposcol version can always be used backwards.

SAPOSCOL should always be started with root permissions, to be able to

collect all the OS statistics (notes #19227 and #726094).

Please check the SAP Notes:

#19227- Open newest saposcol

#1627564 - SAPOSCOL: Clearing Shared Memory and Updating Saposcol

BR

Tamas

[Former Member]

Hello Markus ,

I think we are reached little closer.

When I go dialog mode with saposcol -d

Collector > dump memory all

dump memory all

Pages paged in / sec 7

Pages paged out / sec 0

KB paged in / sec 28

KB paged out / sec 0

freemem [KB] 131372

physmem [KB] 16760832

swap configured [KB] 46137344

swap total size [KB] 59143220

swap free inside [KB] 25346772

swap max. size [KB] 59143220

Other command like dump cpu all are working:

That means shared memory has been assigned and data is stored in it.

Then who picks up this data to the SAP screens those we see via OS06 etc.

Regards,

Tushar

[Former Member]

Hello Markus,

We have a Kernel 700. Should we use saposcol suggested by you?

I restarted saposcol. Now I noticed strange thing:

for one session it displayed data in OS06 for one system.

For another session of the same system / and sessions for another system it won't display data.

Regards,

Tushar

[markus_doehr2]

It´s recommended to use the latest saposcol, subsequent fixes have been incorporated in the latest versions and in case you would open an OSS call they will tell you the same

Use patchlevel 39 (also see Note 918279 - Version history for saposcol on HP-UX). How to get and install see Note 19227 - Open newest saposcol (translation is a bit misleading here - "open").

The saposcol usually creates a shared memory segment before the system starts. It may be possible, that it´s not able to the already created segment, I have seen that with old versions but not with the newer ones.

--

Markus

[Former Member]

Hello Markus,

Still no data has been reported.

When execute OS06 on both systems on status bar following messages appears:

"saposcol not running? (shared memory not available )

Regards,

Tushar

[markus_doehr2]

Ok - I would suggest the following:

- stop each saposcol with "saposcol -k"

- update both of them to the latest version (which is patchlevel 75 for 6.40 from 10th of july)

- set permissions accordingly (4755)

- start saposcol with "saposcol -l"

--

Markus

[Former Member]

Hello Markus,

No There is only one saposcol running under one of the sidadm as owner.

But status shows running through st06 for both systems.

Regards,

Tushar

[markus_doehr2]

So you see now data on both systems? Because you wrote earlier, that you see "saposcol is not running"? I´m confused...

--

Markus

[Former Member]

Hello Markus,

Thanks. There are two systems on the same box.

I have changed permission of the saposcol on one system.On another it was already correct as you said.

Log file for both shows same lines:

Regards,

Tushar

[markus_doehr2]

So you have two saposcol processes running now?

ps -ef | grep saposcol

--

Markus

[Former Member]

Hello Markus,

Thanks .

I have changed owner and permission as you said.

Now SAPOSCOL started.

But Still it has not reported values: when I click on memory /swap etc it shows:

saposcol not running ( shared memory not created )

But status shows it has been started.

<b>Log file says:</b>

SAPOSCOL version COLL 20.93 700 - V2.5.4 2006-12-04 HP-UX PA-RISC, 64 bit, single threaded, Non-Uni

compiled at Jan 27 2007

systemid 273 (HP/9000 (PA-RISC) with HP-UX)

relno 7000

patch text COLL 20.93 700 - V2.5.4 2006-12-04 HP-UX PA-RISC

patchno 95

intno 20050900

running on mou094 HP-UX B.11.11 U 9000/800

09:31:01 30.07.2007 LOG: Profile : no profile used

09:31:01 30.07.2007 LOG: Saposcol Version : [COLL 20.93 700 - V2.5.4 2006-12-04 HP-UX PA-RISC]

09:31:01 30.07.2007 LOG: Working directory : /usr/sap/tmp

09:31:02 30.07.2007 LOG: Identified system as: HP-UX mou094 B.11.11 9000/800/rp7410

09:31:02 30.07.2007 LOG: Architecture identified as 64-bit

09:31:03 30.07.2007 LOG: Shared Memory Size: 1998236.

09:31:03 30.07.2007 LOG: Shared Memory was created by process:15762

09:31:03 30.07.2007 LOG: ==== Collector submitted. This is the parent process after fork.=====

09:31:06 30.07.2007 LOG: ==== Collector submitted. This is the child process after fork()=====

09:31:09 30.07.2007 LOG: Collector daemon started

09:31:09 30.07.2007 LOG: read coll.put Mon Jul 30 09:30:16 2007

09:31:09 30.07.2007 LOG: Collector PID: 15767

09:31:19 30.07.2007 LOG: Initialize Process Monitoring :

09:31:19 30.07.2007 LOG: Process Monitoring active.

09:31:19 30.07.2007 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc

09:31:19 30.07.2007 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/

09:31:19 30.07.2007 LOG: The following processes will be monitored:

There is no progess in log after this.

Best Regards,

Tushar

[markus_doehr2]

Usually it will take some time (amount?) until it is showing something.

Is there just one SAP system running on that box or more than one?

--

Markus

[markus_doehr2]

saposcol needs the SUID-bit set.

Did you execute "saproot.sh <SID>" after you upgraded your kernel?

You can try

cd /usr/sap/<SID>/exe
chown root saposcol
chmod 4755 saposcol

so the effective User-ID during execution is root.

--

Markus