SAPOSCOL stops running frequently

[Former Member]

Hello Experts,

We have 3 Production System, in that SAPOSCOL stops frequently.

Frequency is after every 2-3 days SAPOSCOLL stops.

Can i know what would be the reason? How can i get a permenant solution? What should i check?

Please suggest..!!

Regards,

Prasad Jadhav

[Former Member · Accepted solution]

Hello Prasad,

Is SAPOSCOL the latest one?  (at least :dec 22 PL715)

Did you checked the dev_coll file?
What is the OS version?
Did you installed SAPOSCOL from HOSTAGENT packet?

SAPOSCOL: Error Analysis

https://help.sap.com/saphelp_nw70/helpdata/en/c4/3a6c9b505211d189550000e829fbbd/content.htm?frameset...

Known:Warnings and error messages of dev_coll and possible problems with SAPOSCOL

http://scn.sap.com/community/netweaver-administrator/blog/2013/10/08/contain-of-devcoll-and-possible...

How to analyse the missing performace data situation and how to check SAPOsCol issues

http://wiki.scn.sap.com/wiki/display/NWTech/How+to+analyse+the+missing+performace+data+situation+and...

Kind regards,

Tamas Istenes SAP Support Engineer

AGS Primary Support, Global Support Center

[Former Member · Accepted solution]

Tamas,

SAPOSCOL version is COLL 21.02 720 - v2.19, AMD/Intel x86_64 with Linux

Which version shall i use?

Operating System is :Linux bynhc4 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue

How do i check if  SAPOSCOL is installed from HOSTAGENT packet?

Regarsd,

Prasad

[Former Member · Accepted solution]

Hello Prasad,

Please open dev_coll file according to dokument:

SAPOSCOL Log Files

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c4/3a6c67505211d189550000e829fbbd/content.htm

Please copy the line : "compiled at ..." and  "patchno"

Could you please allo scroll down and copy some lines from dev_coll ?

Kind regards,

Tamas Istenes SAP Support Engineer

AGS Primary Support, Global Support Center Hungary

[Former Member · Accepted solution]

Hello Tamas,

Thank you for the reply

Please look at the below information from the dev_coll

SAPOSCOL version  COLL 21.02 720 - v2.19, AMD/Intel x86_64 with Linux, 2010-07-23, 64 bit, single threaded, Non-Unicode

compiled at   Aug 17 2010

systemid      390 (AMD/Intel x86_64 with Linux)

relno         7200

patch text    COLL 21.02 720 - v2.19, AMD/Intel x86_64 with Linux, 2010-07-23

patchno       61

intno         20020600

chgno(local)  1177307

chgno(global) 1182403

PATCHES

DATE     CHANGELIST           PLATFORM             PATCHTEXT

20081211                      ALL                  Option -w support. Removed SizeOfRecord warning rt 130.

20090114                      UNIX                 Log file permissions: 664.

20090203                      UNIX                 Add. single instance check.

20090210                      ALL                  Continue after EWA HW XML generation failure.

20090324                      ALL                  Fix dynamic trace level switch.

20090512                      ALL                  Usage of DIR_HOME as working dir.

20090512 1064069              UNIX                 Hardware XML permissions 660.

20090613                      ALL                  Async HW info generation.

20090909                      UNIX                 DIR_PERF, DIR_HOME, /var/tmp, ...

20090909                      UNIX                 Group sapsys and smarter permissions of files

20091105                      WINDOWS              New Monitoring for VMware

20091210                      ALL                  Performance improvement 'saposcol -xml'.

20100723                      LINUX                New Monitoring for VMware

kindly find the below logs

20:30:05 01.02.2015	LOG: Profile	: no profile used
20:30:05 01.02.2015	LOG: Saposcol Version  : [COLL 21.02 720 - v2.19, AMD/Intel x86_64 with Linux, 2010-07-23]
20:30:05 01.02.2015	LOG: Working directory : /usr/sap/tmp

20:30:05 01.02.2015

LOG: Virtualization: Detected `VMWare'

20:30:05 01.02.2015 WARNING: Error in VMware guest library.

20:30:05 01.02.2015 WARNING: VMware: Can't get host information.

20:30:05 01.02.2015

LOG: VMware guest library is libvmGuestLib.so

20:30:06 01.02.2015	LOG: Shared Memory Size: 767258.
20:30:06 01.02.2015	LOG: Shared Memory was created by process:23471
20:30:06 01.02.2015	LOG: ==== Collector submitted. This is the parent process after fork()=====
20:30:09 01.02.2015	LOG: ==== Collector submitted. This is the child process after fork()=====
20:30:12 01.02.2015	LOG: Connected stderr to log_file
20:30:12 01.02.2015	LOG: Collector daemon started
20:30:12 01.02.2015	LOG: can't open put-file /usr/sap/tmp/coll.put
20:30:12 01.02.2015	LOG: Collector PID: 23489
20:31:12 01.02.2015	LOG: Initialize Device Filtering
20:31:12 01.02.2015 LOG: Initialize Process Monitoring 20:31:12 01.02.2015 LOG: Process Monitoring active. 20:31:12 01.02.2015 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/ 20:31:12 01.02.2015 LOG: The following processes will be monitored: 20:31:12 01.02.2015 LOG: This Linux kernel operates at 100 HZ (compile-time HZ was 100). ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 20:33:28 01.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 22:49:42 01.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 00:55:54 02.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. 01:06:59 02.02.2015 LOG: system config changed: #cpus[new/old]:    27/27 #lans[new/old]:    3/3 #disks[new/old]:   44/44 #filesystems[new/old]: 41/39 hour data will be invalid ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 02:58:06 02.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 06:38:23 02.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 08:38:35 02.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. 20:11:10 02.02.2015 LOG: system config changed: #cpus[new/old]:    27/27 #lans[new/old]:    3/3 #disks[new/old]:   44/44 #filesystems[new/old]: 43/41 hour data will be invalid ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 20:33:37 02.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 22:11:46 02.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 23:42:54 02.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 01:10:00 03.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 02:35:08 03.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 04:07:17 03.02.2015 LOG: No Write Access to Shared Memory: Skip this interval. ======================= LOG: WaitFree: could not set new shared memory status after 15 sec 05:23:22 03.02.2015 LOG: No Write Access to Shared Memory: Skip this interval.

[Former Member · Accepted solution]

Hello,

Thanks for the log file !

First of all SAPOSCOL is too old : compiled at   Aug 17 2010

SAPOSCOL: Clearing Shared Memory and Updating Saposcol

http://scn.sap.com/people/brendan.ocallaghan/blog/2011/09/08/saposcol-clearing-shared-memory-and-upd...

Installing SAPOSCOL on a UNIX Host

https://help.sap.com/saphelp_nw70/helpdata/en/75/a0c43a1291a74ce10000000a114084/content.htm

Please upgrade it to:

Jan 19 2015 ; patchno

717

We also see: WARNING: VMware: Can't get host information. Please check SAP notes:

#994025 - Virtualized OS environments in the operating system

#1122387 - Linux: SAP Support in virtualized environments

#1606643 - Linux: VMware vSphere host monitoring interface

Please refer to KBA how to clean the SHM to solv the :LOG: No Write Access to Shared Memory: Skip this interval.

#1627564 - SAPOSCOL: Clearing Shared Memory and Updating Saposcol

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).

Best regards,

Tamas Istenes SAP Support Engineer

AGS Primary Support, Global Support Center Hungary

[Former Member · Accepted solution]

Thank you Thamas for the information.

The information is very valuable.

Can you let me know were i can find the below information or any file for patch no 717.

Jan 19 2015 ; patchno   717

were it is mention tha latest version.

Regards,

Prasad Jadhav

[Former Member · Accepted solution]

Hello Prasad,

Yes

Please check link:

Downloading SAPOSCOL

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/0f/392500b3477d4b9c1d465d36aec92b/content.htm?frame...

and the KBA(!):  1627564 - SAPOSCOL: Clearing Shared Memory and Updating Saposcol  

or

SAPOSCOL: Clearing Shared Memory and Updating Saposcol

http://scn.sap.com/people/brendan.ocallaghan/blog/2011/09/08/saposcol-clearing-shared-memory-and-upd...

It is in the latest SAPHOSTAGENT packet, please refer to KBA: #1627564

- Stop the old SAPOSCOL process

- If there are SAPCCMSR or SAPCCM4X agents running on the same server it is also better to stop these processes too.

- Check if the shared memory segment is correctly removed (On Windows systems you can try to start SAPOSCOL in dialog mode and execute the ‘leave’ command. If this does not remove the shared memory segment on an OS restart will help. On UNIX systems you can use the OS command ‘cleanipc 99 remove’)

- Delete the coll.put file which is stored in the SAPOSCOL working directory

- Install the new SAPOSCOL executable in the correct executable directory

- Start SAPOSCOL (and the CCMS agents) again.

- After this always check the dev_coll file to see if the new collector process also did recreate the shared memory segment again.

BR

Tamas

Kind regards,

Tamas Istenes SAP Support Engineer

AGS Primary Support, Global Support Center

[Former Member · Accepted solution]

please download latest patch using

https://websmp202.sap-ag.de/swdc

search for this file:

SAPHOSTAGENT203_203-20005731.SAR

ot

saphostagentrpm_203-20005731.rpm

this is the latest patch for sap host agent (that includes saposcol).

use this guide how to upgrade:

SAP Host Agent Upgrade - SAP Host Agent - SAP Library

[Former Member]

What is the platform?

in most of the cases, upgrade of SAPOSCOL to the latest version should solve the problem.

[alwina_enns]

Hello Prasad,

when saposcol stops running what do you see as the last entry in dev_coll? Is a core file created at that time in the working directory of saposcol in /usr/sap/tmp? What reports SAPHOSTAGENT in dev_saphostexec when saposcol stops?

Regards,
Alwina

[divyanshu_srivastava3]

Hi Prasad,

Do you have host agent installed on your systems ?

Check with root user whtr hostagent is running or not.

SAPOSCOL is started with hostagent and can be find in it binaries.(if you are not using old kernel implementations of SAPOscol)

Generally, this should be in usr/sap/hostctrl.

Restart SAP hostagent(using root)

saphostexec -stop

saphostexec -restart -(this will start)

If you have diagnostic agents in your system, then stop diagnostic agent, check if hostagent is stopped and then restart diagnostic agents.

Refer below for more.

http://scn.sap.com/people/brendan.ocallaghan/blog/2011/09/08/saposcol-clearing-shared-memory-and-upd...

SAP Host Agent - SAP Library

[Former Member]

Thanks Miguel and Manu...

@ Miguel : How can i check if my SAP host agent is out dated and which is the latest one.

Regards,

Prasad

[magexposito]

Hello Prasad,

If you execute the command 'saphostexec -version' you will see which version you have installed. About the last version available, you can check it on the Download Area of the Support Portal:

SAP Technology Components / SAP HOST AGENT / SAP HOST AGENT 7.20

Regards.

[Former Member]

Hi pradeep,

you can go to /usr/sap/hostctrl/exe path in your System.

You will find saphostexe executable. Just execute with -help option. You will be clearly briefed

about it.

regard,

Dipak

[Former Member]

Hello,

Is the situation persist after the SAPOSCOL was upgraded to the latest one?
Did you checked the dev_coll file?

Br

T

[magexposito]

Hello Prasad,

Is there any information on the saposcol's log file. You can find where it is supposed to be here:

SAPOSCOL Log Files - Operating System Monitor - SAP Library

Also I will recommend to update your SAP Host Agent on all your the servers of the PRD System.

Best regards.

[manumohandas82]

Hi Prasad ,

Please read the following link

About SAPOSCOL - Netweaver Technology - SCN Wiki

Thanks ,

Manu