AIX IBM 7.1 version - defunct process

Question

0.00/5 (No votes)

See more:

Hi guys, good afternoon :)
I do a deploy on my AIX machine geddistri04 which the AIX version is 7.1. When I restart the oplink process, my parent process 63308256 is not exist.

[desenv20@geddistri04]/ambiente/producao/desenv20/exec/funcn/bin> DO*

ERROR DOWN THE OPLINK PROCESS

[desenv20@geddistri04]/ambiente/producao/desenv20/exec/funcn/bin> UP*

Saving the log archive..
              ./nohup.out => ./Log/nohup.out.20220410144659
       * compressing data...
 -- file unchanged
       * remove old files...
       * saving operations logs...
              ./Log/oplinkse.log => ./Log/oplinkse.log.20220410144659
       * compressing data...
..zip complete.
Up Openlink session..
Sending output to nohup.out
OPENLINK SERVER desenv20 IS UP. PROCESS PARENT IS: 63308256

[desenv20@geddistri04]/ambiente/producao/desenv20/exec/funcn/bin> ps -ef | grep 63308256
desenv20  1638962  6554358   0 15:47:09  pts/4  0:00 grep 63308256

I google it and he discoverd that's a defunct process. How can I ative it for the correct process? May I do it linking to a program or process? I google it but I didn't found anything to help me.

What I have tried:

I tried to run the process to plug in the oplink server, but the process ends quickly without chance to restart. I tried to kill all defunct process and recompile the environment but still with the same problem. I can't restart the machine because I'm not admin.

Posted 10-Apr-22 5:14am

Nuno Pereira 2021

Updated 10-Apr-22 7:30am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

k5054 · Accepted Answer · 2022-04-10T07:30:00

A defunct process is a process that has exited, but the parent process has not called wait() for it yet. The wait() system call returns the child process exit value to the parent for whatever processing it might need to do based on whether the process succeeded or not. Since the process has exited, you cannot kill it - as you've found out. This is true for root as well. A defunct process stays in the process table until a wait() call has been made (I think maybe if the parent exits then that works too .. not 100% sure about that).
I think you'll have to discuss the problem with supplier of the OpenLink software. If a reboot is needed, you'll have to discuss with the system admin.

NB. You can find out the status of a process (or some processes) by using the -p flag for ps e.g.

Bash

$ ps -fp 1234,9876,34567

will do ps -f for processes 1234, 9876, 34567. If you only need to examine one process, then just use ps -fp pid