SAP OS COLLECTOR

[former_member265724]

Every Monday i get the below mentioned error in one of the app sever.

Saposcol: data collection not up to date

The above mentioned error happens only once a week and it gets rectified once i restart the os collector.

May i get help to get rid of this error?

[former_member265724]

Hi Pinkle ,

I have checked the log file and there are no trace entries. The entires in dev_coll.old are as below :

-

---

SAPOSCOL version COLL 20.95 700 - V3.72 64Bit, 64 bit, single threaded, Non-Unicode

compiled at Apr 1 2008

systemid 370 (Solaris on SPARCV9 CPU)

relno 7000

patch text COLL 20.95 700 - V3.72 64Bit

patchno 154

intno 20050900

running on gbahex103 SunOS 5.10 Generic_141414-09 sun4v

-

---

09:05:28 19.04.2011 LOG: Profile : no profile used

09:05:28 19.04.2011 LOG: Saposcol Version : [COLL 20.95 700 - V3.72 64Bit]

09:05:28 19.04.2011 LOG: Working directory : /usr/sap/tmp

09:05:28 19.04.2011 LOG: Process Monitoring active.

09:05:28 19.04.2011 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc

09:05:28 19.04.2011 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/

09:05:28 19.04.2011 LOG: The following processes will be monitored:

09:05:28 19.04.2011 LOG: RefreshDeviceFiltering failed - no filtering done!

09:05:29 19.04.2011 LOG: Shared Memory Size: 407918.

09:05:29 19.04.2011 LOG: Shared Memory was created by process:20287

09:05:29 19.04.2011 LOG: ==== Collector submitted. This is the parent process after fork.=====

09:05:32 19.04.2011 LOG: ==== Collector submitted. This is the child process after fork()=====

09:05:35 19.04.2011 LOG: Collector daemon started

09:05:35 19.04.2011 LOG: read coll.put Tue Apr 19 07:00:10 2011

09:05:35 19.04.2011 LOG: Collector PID: 20312

05:10:44 25.04.2011 LOG: caught signal 2 - exiting

05:10:44 25.04.2011 LOG: ==== Trying to stop saposcol while it is still collecting.

05:10:44 25.04.2011 LOG: ==== Stop Flag set: collector will stop as soon as possible.

05:10:44 25.04.2011 LOG: ====

As OSCol was restarted manually on last Monday as well as a temporary workaround so it has the entries on 25.04.2011. However , there is no entry written in log for the data cllection not up to date.

Can somebody suggest what else can be checked?

[Former Member]

Hello

Kindly check the whether any jobs run at weekend which use system memory. I hope OSCOl is not getting enough shared memory due to which its terminating as you see in the log.

Kindly also have a look at memory usages during weekend when it usually this SAP OScollector goes down.

Regards

Vivek

[Former Member]

Hi,

Check whether there is any trace in dev_coll log file.

Regards,

Pinkle