Saposcol is not running properly

[Former Member]

Dear all,

We have experience some strange behaviour on SAPOSCOL in our WINDOWS 2003 R2 x64 SP2. SAPOSCOL is running but after a reboot this is not working under the DIR_PERF specify as per note 112266 point 18.

In fact the file dev_coll is not located on DIR_PERF and furthermore no data are displayed on ST06.

Could you kindly recommend us to take any action to solve the issue?

Thanks in advance.

BR,

Maite

[Former Member]

Hi,

Also see the note Note 1322232 - saposcol: attaching to existing shared memory. I think this should solve the problem.

Regards

Naeem

[Former Member]

Hi,

Could you please pase the output of command saposcol -l and saposcol -k. It seems to be problem with shared memory.

Regards,

Naeem

[Former Member]

Dear all,

In fact, there is a clustered environment, and files are located under C:\usr\sap\prfclog dev_coll, dev_coll.tmp and coll.put

There are no errors while executing saposcol -k and then saposcol -l.

Thanks in advance.

BR,

Maite

[JPReyes]

Ok.... I don't understand... If it was working as you intended, why did you change config to follow the clustered settings for saposcol?

The only way to find out the reason for your collector not to be working is by checking the logs...

Can you check as requested before the logs of dev_coll and the Event viewer for errors?... also if the changes in the note are not required can you undo those changes?

Regards

Juan

[Former Member]

Dear all,

Thanks a lot for your responses. Perhaps I have not explained enough clear.

For a long period, it was working properly without doing the configurations and setting of cluster environment.

Anyway last week we realized that something strange was happening because it displays no data on ST06, so after doing some changes, we have implemented note 112266. We have done on Tuesday and it began to display data. All seemed to be ok.

On Friday we have a reboot of the server, and after that data are not anymore displayed.

Here are the data requested:

saposcol -k

Setting Stop Flag :

15:32:49 06.05.2010 LOG: ==== Stop Flag was set by saposcol (kill_collector()).

15:32:49 06.05.2010 LOG: ==== The collection process will stop as soon as possible

Collecting process has stopped.

15:32:50 06.05.2010 LOG: Shared memory deleted.

saposcol -l

Starting collector (create new process)

saposcol -s

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

Collector Versions :

running : COLL 20.95 701 - 20.68 NT 09/03/27

dialog : COLL 20.95 701 - 20.68 NT 09/03/27

Shared Memory : attached

Number of records : 4025

Active Flag : active (01)

Operating System : Windows NT 5.2.3790 SP 2

Collector PID : 9596 (0000257C)

Collector : running

[Former Member]

Pls go through the following note:

-

---

SAP Note 688131 - Windows: missing data in ST06/OS06

-

---

cheers !

PRADi

[JPReyes]

try to start it manually and post the error

check that is not still been created at <drive>:\usr\sap\PRFCLOG

Check also that the env variable is set as per the note

Regards

Juan

[Former Member]

Dear Juan,

When you said us to start saposcol manually, you would said the service or doing saposcol -k and saposcol -l?

Last friday it was running and aftere a reboot the saposcol is running but not using the working directory DIR_PERF.

We have done the stop and start of saposcol but no solution was found.

Here are the status of the saposcol shown at ST06:

Thu May 06 11:16:12 2010

WINDOWS NT SP 2

Collector Version: COLL 20.95 701 - 20.68 NT 09

Date/time 06.05.2010

Start of Collector Thu May 06 11:09:21 2010#

Status report

If we go to log file we see the following entries:

Contents of log file

Cannot open file: C:\WINDOWS\SapCluster\dev_co

saposcol

The environment variable is set as system but not for sidadm user.

Thanks in advance.

BR,

Maite

Edited by: Maria Teresa Cuerpo on May 6, 2010 12:27 PM

[JPReyes]

Cannot open file: C:\WINDOWS\SapCluster\dev_co

Seems like permission are not right... saposcol in windows is a service, check what user is the service configured with and make sure that the user has rights for that directory.

Regards

Juan

[Former Member]

Dear Juan,

The same user is starting the service on other servers and there is no problem. Besides, note 112266 is not applied and it works properly.

In fact, in C:\WINDOWS\SapCluster there is no files for saposcol.

BR,

Maite

[JPReyes]

In a non-clustered environment files are usually droped under /usr/sap/prfclog check if dev_coll is there...

Seems to me like theres a step missing somewhere in your config.

Have you tried to start the saposcol directly from the services and check the error?.. Also check the Windows Event Viewer for errors

Regards

Juan