Clovertech

Process won’t start 5.7 Rev2

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Process won’t start 5.7 Rev2

  • Creator
    Topic
  • August 20, 2014 at 3:28 pm #54351
    Tim Hallbauer
    Participant

      Hi all,

      I have a process in my test site that just doesn’t seem to start. I have tried to start it by starting the process and also a single connection within that process. I can see that the pid is created and removed when I start and stop the process. The process just never shows that it is running. Hciprocstatus shows that it is still down.

      I can’t find anything in any log files or output that would indicate an issue. I have shutdown and removed the monitorShmemFile, rdm.taf file, initialized the Db stopped and restarted the host server etc. Everything just short of rebooting. I have to be missing something? Is there somewhere I should be looking?

      Thanks,

      Tim

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • August 20, 2014 at 4:39 pm #81123
        Tim Hallbauer
        Participant

          Additionally, when I issue the command to stop the process, I get a return that it is not running. When I issue the command to start it I get a message that it’s already running.

        • August 20, 2014 at 5:27 pm #81124
          Michael Hertel
          Participant

            I usually find in cases like this that the pid and/or wpid file refers to a process id that is usually an unrelated job running on the system.

            When all else fails, you can delete the process directory and let the system rebuild it at the next start.

          • August 20, 2014 at 8:37 pm #81125
            Russ Ross
            Participant

              If any of the following files don’t exist in $HCISITEDIR/exec/processes/my_process

              cmd_port

              pid

              wpid

              then check if the process might actually be running and has lost the pointer files above to itself, which will require you to manually kill that process on the backend.

              Under AIX, I would do the following to locate the process and pid I need to manually kill

              ps -ef | grep $HCISITE

              once I locate the rogue process pid from the listing above, I use the command

              kill -9 my_pid_of _interest

              Russ Ross
              RussRoss318@gmail.com

            • August 27, 2014 at 11:43 am #81126
              Tim Hallbauer
              Participant

                Thanks for the suggestions.

                It turned out that there were some old processes that were running ‘in memory’ identified.

                HCIENGINE, HCIENGINEWATCH and HCIMONITORD

                Once these were killed, the process started.

                Tim

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.