Prev
Next
Forums S3 Systems Administration

waitpid() failed on process

Sort:
You are not authorized to post a reply.
Author
Messages
Sherry S.
Basic Member
Posts: 11
Basic Member
1/12/2012 4:25 PM

    We have been getting these messages for the last couple weeks.  We cannot find the cause and of course GSC does not know.  we have not applied any patches or made any changes that would cause this issue.  We are on 9.01 Windows.  Any help would be greatly appreciated.

    Wed Jan 11 16:38:00 2012: latm (PrcDeath): Received death notification of lapm, Uid=3, Pid=9520, GenNbr=0

    Wed Jan 11 17:58:02 2012: ERROR:  WaitAlrm() reached, wait terminated.

    Wed Jan 11 17:58:02 2012: ERROR: waitpid() failed on process 13756.

    Wed Jan 11 19:13:54 2012: ERROR: waitpid() failed on process 9840.

    Wed Jan 11 19:38:00 2012: ERROR: waitpid() failed on process 12044.

    Wed Jan 11 22:38:58 2012: ERROR: waitpid() failed on process 12000.

    Wed Jan 11 23:19:58 2012: ERROR: waitpid() failed on process 12000.

    Thu Jan 12 00:24:55 2012: ERROR: waitpid() failed on process 12000.

    Thu Jan 12 05:21:44 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 05:21:44 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 05:26:29 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 05:38:29 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 05:54:29 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 06:16:18 2012: ERROR: waitpid() failed on process 816.

    Thu Jan 12 06:19:29 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 06:21:29 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 06:23:36 2012: ERROR: waitpid() failed on process 3016.

    Thu Jan 12 06:25:59 2012: ERROR: waitpid() failed on process 12000.

    Thu Jan 12 06:56:29 2012: ERROR: waitpid() failed on process 12044.

    Thu Jan 12 07:02:55 2012: ERROR: waitpid() failed on process 12000.

    Thu Jan 12 07:24:02 2012: ERROR: waitpid() failed on process 9956.
    SP
    Veteran Member
    Posts: 122
    Veteran Member
    1/12/2012 8:19 PM
      Run listusermap and find out who is UID=3. That is a really low UID number so it had to be one of the first users setup on the system.

      Once you know who it is, you can start working to track down the processes.
      You are not authorized to post a reply.