cancel
Showing results for 
Search instead for 
Did you mean: 

SAPOSCOL failed to running

Former Member
0 Kudos

Hi Friends,

SAPOSCOL is stopped running for almost 30 hrs and automatically started after that .Could you please let me know why it was stopped ,please find the below log.

/* filesystems */ + PX_fsys_anz_max * 25 = 50 * 25 = 1250

LOG: /* cpu all */ + 25

LOG: /* cpus */ + PX_scpu_anz = 8

LOG: /* lans */ + PX_lan_anz_max * 25 = 50 * 25 = 1250

LOG: /* for memory */ + 24

LOG: /* top 40 processes */ + NBR_TOP = 40

LOG: /* process list */ + MAX_PROCESS_CONF_ENTRIES = 50

LOG: /* systemid */ + 1

LOG: /* kernelparameter */ + kpar_anz * 2 = 0 * 2 = 0

LOG: + spec_anz * 25 = 1 * 25 = 25

Searching for Process Monitoring Templates in D:\usr\sap\PRFCLOG\dev_proc

searching for Process Monitoring Templates in D:\usr\sap\PRFCLOG\procmon\

LOG: The following processes will be monitored:

LOG: Process: jlaunch-DSAPINFO=SID_00_dispatcher* for user:

LOG: Process: jlaunch-DSAPINFO=SID_00_server* for user:

LOG: Process: jlaunch-DSAPINFO=SID_00_sdm* for user

Regards

Sreenivas

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

May i know the following.

1) Have you done any changes to the system. Like kernel upgrade, os level user settings, folder settings recently.

If yes, check your settings.

Or just restart the server, everthing will be fine.

And if issue is there , it is with rights. Check the file permissions.

ls -l saposcol = user must have execute rights check. if not give rights.

ex: chmod 744 saposcol

<removed_by_moderator>

Asking for points is not allowed, read the "Rules of Engagement"

Regards,

MSR.

Edited by: Juan Reyes on Sep 22, 2011 9:08 AM

Former Member
0 Kudos

Hi,

i would suggest you to upgrade your kernel which is anyway you will be doing with <sid>adm and then from root user own saposcol using chown root:sapsys saposcol command and then provide permission with chmod 4750 saposcol command from root prompt.

i believe in your case permission is not the case but may be problem with kernel.

Rgds,

Durga.

Former Member
0 Kudos

Hi,

check the saposcol permission 4775

try to run as root

rename dev_coll.tmp and restart saposcol

if no luck after this, try to upgrade saposcol

Thanks