you can create it manually at OS and after that you can try to start your Collector from OS as well
saposcol -l
Regards,
Subhash
Hello Christian,
If it's UNIX, then you should have separate file system /usr/sap/tmp.
You need to create tmp directory, if it's Windows environment. Once you have tmp in place then start the saposcol agin and it should be running fine.
Thanks,
Siva Kumar
Thx to both for fast answer.
We have unix (HP-UX).
I've created the tmp directory.
But when I click on START or STOP nothing happens.
I've I click on LogFile II still get the error Cannot open file: /usr/sap/tmp/dev_coll
Any ideas?
Thx to both for fast answer.
We have unix (HP-UX).
I've created the tmp directory.
But when I click on START or STOP nothing happens.
If I click on LogFile I still get the error Cannot open file: /usr/sap/tmp/dev_coll
Oh I forgot:
When I start ST06 I get the message:
SAPOSCOL not running ? (Shared memory not available)
I hope this is helpful.
Thx for help
login to your OS with sidadm
Saposcol -l
check the output if you are getting any error check the permission of tmp directory
Regards,
Subhash
Where do I have to execute the command saposcol -l?
Directly after login or in directory usr/sap/tmp?
Thx verry much for help
Hello Christian,
after system-swap I can't start the os collector with ST06.
What sort of system swap you have done? Can you please clarify?
Thanks,
Siva Kumar
System-definition is the same.
But we got a new server.
So we installed the system to the new server and after that we moved it to the new server.
I think its the same kind like a system-copy.
thx
Not sure you added a new App server or what but you can simply start the OS collector by saposcol -l. just login with sidadm and execute from any directory.
Regards,
Subhash
Check the ownership and permissions for that directory and file.
ls -ltr \usr\sap\tmp
<paste result here>
Then if necessary, run chown and chmod commands against the directory and the dev_coll file.
\usr\sap\tmp and \usr\sap\tmp\dev_coll
You should have RWX for user <SID>ADM so that the SAPOSCOL process can write it's log file to dev_coll in \usr\sap\tmp
I've exectued now saposcol -l
I get the: Command not found???
As I've created the tmp dir today, it is emptry.
So there is no dev_coll file.
thx for help
Hi,
you must be logged on as user <SID>adm otherwise your environment (path etc) will not be correct.
What happens if you type whoami at the command line? What is your system ID?
Hi,
There can be of two reason for this issue.
1. Please see your path variable has the path to your exe directory. You can validate that by issuing env after logged in as <sidadm> user. Compare your path profile with another server in which same SAP product has been installed.
Example PATH Varivale:
PATH=/usr/sap/DSD/J02/exe/sapjvm_5/bin:/home/dsdadm:/usr/sap/DSD/SYS/exe/uc/rs6000_64:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/dsdadm/bin:/usr/bin/X11:/sbin:.:/db2/db2dsd/sqllib/bin:/db2/db2dsd/sqllib/adm:/db2/db2dsd/sqllib/misc
Once you fixed the PATH variable logout from <sidadm> user and then login back. Then issue saposcol -l or saposcol -f to see whether its getting started.
2. Please see incase your system have been installed with saphostctl agent. In that case your saposcol will be part of your host agent itself.
3. Please compare the filesystem permission for the error message dev_coll with another server in which saposcol is running fine.
Best Regards,
Vasanth G
HI,
yesterday and today I will not find time to check this.
But I will do it on monday morning and then I will give you response.
Thx for help
I also think saposcol has the wrong permissions at kernel level, SAPOSCOL must be owned by root and have 4755 permission
If you can't execute SAPOSCOL from the command line while logon as <sid>adm your enviromental variables are not set correctly.
Regards
Juan
Hi,
Please go through below SAP Note for configuring saposcol.
Note 19227 - Open newest saposcol.
Check below link aswell
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a6c5a505211d189550000e829fbbd/content.htm
Regards,
Venkata S Pagolu
Good morning Vasanth,
first sorry for my late response. But I was ill and today is my first day back.
I don't now exactly what I have to check with your last response.
Could you please explain the 3 steps a little more "easier".
As already said, tmp directory is still empty.
I've all rights for sid-adm at this dir.
Thx
Christian
Dear Christian.
firtst you should create the folder and should provide neceessory permission.
then goto console with user : <SID>adm -->
then run : sapccmsr -DCCMS pf=/usr/sap/<SID>/SYS/profile/sapccmsr.pfl to update ccms
then run saposcol -i
regards
priyanshann
Hi priyanshann,
I've exectued the command as your wrote.
After that I got the following:
<servername>:<sysid>adm 21> sapccmsr -DCCMS pf=/usr/sap/<sysid>/SYS/profile/sapccmsr.pfl
sapccmsr=>sapparam(2): fopenU("/usr/sap/<sysid>/SYS/profile/sapccmsr.pfl","r"): No s
uch file or directory
INFO: CCMS agent sapccmsr working directory is /usr/sap/tmp/sapccmsr
INFO: CCMS agent sapccmsr config file is /usr/sap/tmp/sapccmsr/csmconf
ERROR: cannot open config file /usr/sap/tmp/sapccmsr/csmconf.
ERROR: CCMS agent is not registered at central CCMS system.
ERROR: Please start
ERROR: sapccmsr -R [-f <config file>] [pf=<complete path of agent profile file>
]
EXITING with code 1
<servername>:faqadm 22> saposcol -i
saposcol: Command not found.
I've checked dir "tmp" and there exists now a directory called "sapccmsr".
Any ideas whats wrong?
Thx
Hi,
Check that "saposcol" in kernel directory has ownership "root:sapsys" and permission 4755.
Try to start SAPOSCOL with below command.
If you logged in as <sid>adm then,
<sid>adm># su root -c "<full_path_of_saposcol>/saposcol -l"
For example,
faqadm 22>su root -c "/usr/sap/<sysid>/SYS/exe/saposcol -l" or faqadm 22>su root -c "/sapmnt/<sysid>/exe/saposcol -l"
(Run saposcol as root user, either from saposcol directory or with full path...)
Regards.
Rajesh Narkhede
Hello Christian,
Please look into SAP Note 1627564.
It clearly tells you how you have to update SAPOSCOL. If you don't have tmp folder, Please create it manually and give a try.
Hope this helps you.
Thanks & Regards,
Ananda Swaroop
Hi, Please check in the /usr/sap/<SID>/SYS/exe or /sapmnt/exe directories for this saposcol file.
If it is missing there for any reason, then you can not start the saposcol as it will search for this executable file in the above directory when you give this command saposcol -l to start the os collector.
You can copy it from any other server to the above location and then try to start the os collector as sidadm user.
You dont need to be in any specific path/directory to execute this command.