• Home
  • Linux
  • UNIX
  • Website Development
  • SAP Basis
  • SAP Solution Manager
  • SAP PI/XI
  • SLD

Problem with stop/start saposcol

Sometimes it may be impossible to stop saposcol either by

“saposcol -d” –> kill or by “saposcol -k”.

The system produces messages similar to:

========================================
can't kill process 99687.
kill: No such process
ERROR:No reaction from collecting process 99687!
Please kill collecting process.
========================================

Although no process with PID 99687  exists, the output of command “saposcol -s” shows that saposcol is running and shared memory is attached.

In this case, stop the collector running by removing the shared memory key of saposcol.

For this, execute command “ipcs -ma” and note the line that contains saposcol key “4dbe”. You need the shared memory ID. After that, execute command
ipcrm -m ID

bash-3.00$ ipcs -ma | grep 4dbe
m   5242883 0x00004dbe --rw-rw-rw-     root   sapsys     root   sapsys      0   187
0188 671902 938150 11:19:40 11:19:40 21:47:04
bash-3.00$ ipcrm -m 5242883

Now the command  “saposcol -s” should show that saposcol is not running and that the shared memory is not attached. The shared memory key will be created automatically by the saposcol when the collector is next started: “saposcol -l”.

« SAP NW Java: Delete old dumps and trace files with command find
JRE 7.25 incompatible with PI Tools | LAZY_CLASSLOADING_FAILED »
Еще по теме:
This entry was posted in SAP Basis and tagged saposcol.
2 Comments к “Problem with stop/start saposcol”
  1. Daniel Oliveira says:
    29/09/2015 at 12:33

    Thank you! We was facing the same issue in our historic environment and this solution worked just fine!!!!

    Reply
    • SAP Basis Expert says:
      02/03/2017 at 00:01

      Thank you for your review!

      Reply
Оставить Ответ
Click here to cancel reply.

  • Курсы валют

    RUB/USD - 69,1263

    RUB/EUR - 75,3348

  • Tags
    ABAP AIX AI_RUNTIME_JCOSERVER Arch Linux awk BPE brtools CHARM client copy cp CUA dd dev_w logs download basket download or upload files drivers EarlyWatch Alert epson ESR file system find firefox FTP GRUB HA systems hot keys HTTPS ibus icm Internet Explorer iso Java kernel keyboard language Linux Linux Mint logs Managed System Configuration mount mpv NWA ORACLE pacman PI Cache READ_USER RFC authorization robots.txt roles RWB RZ20 rz21 SAPCAR sapgui saposcol SAP Web Dispatcher SAP по русски Secure store Service Desk shared memory Shutter SLD sm21 sm59 SMD agent SOLAR_PROJECT_ADMIN spam ST03 STAD STMS STZAC Super L SUSE swap terminal text editors timezone tp Unix client Upgrade USB UTF-8 viber waterfox wordpress xterm YouTube youtube-dl zoom Альтернатива Windows Горячие клавиши Зависания Клавиша Win Кодировка Отмена перехода на зимнее время Температура процессора загрузка Excel минимальные требования к аппаратному обеспечению
  • Posts with most comments
    • SAP Solution Manager не работает отправка сообщения в SAP (4)
    • Error: Remote access to the NetWeaver Administrator is forbidden. See SAP Note 1451753 for details. (4)
    • AI_RUNTIME_JCOSERVER – Timeout while waiting for a connection to be established (2)
    • Script for UnSAPCAR Multiple SAR files in single shot (2)
    • Problem with stop/start saposcol (2)

© 2011 - 2023 30 years in IT. All Rights Reserved.