RE: [U2] Phantom job started from another phantom job
Thanks gang for your help. We'll try out some of these next week. If we have success, I'll share it with you. ...ds > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Barry Rogen > Sent: Friday, May 19, 2006 3:59 PM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > >It may sound like a bizarre formula but we are able to > control this scenario. We have a background process that runs > 24x7. It checks for tasks to do, then goes to sleep, wakes up > and checks, etc. If there is some task that needs doing, the > phantom process, starts another phantom process and that > phantom process starts the actual process that does the work. > > So phantom watchdog starts a phantom ph.start. > ph.start's only task is to start phantom.to.do.actual.work. > > This method seems to dramatically keep defuct and zombie > processes to a substantial minimum. > > > > Barry Rogen > PNY Technologies, Inc. > Senior Programmer/Analyst > (973) 515 - 9700 ext 5327 > [EMAIL PROTECTED] > > - > Far better it is to dare mighty things, to win glorious > triumphs even though checkered by failure, than to rank with > those poor spirits who neither enjoy nor suffer much because > they live in the gray twilight that knows neither victory > nor defeat.t. roosevelt > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mark Eastwood > Sent: Friday, May 19, 2006 2:39 PM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > > In the main phantom (one spawning the other phantoms), try executing > "JOBS" every time it wakes up. > > Mark > > -Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave > Sent: Friday, May 19, 2006 10:36 AM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > > We tried this and it didn't solve the problem. > > Thanks for the suggestion. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of roy > > Sent: Friday, May 19, 2006 11:58 AM > > To: u2-users@listserver.u2ug.org > > Subject: RE: [U2] Phantom job started from another phantom job > > > > Try executing the VOC item NOTIFY ON see help files > > > > This finishes the phantom job and delete the process. > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave > > Sent: Friday, May 19, 2006 10:56 AM > > To: u2-users@listserver.u2ug.org > > Subject: [U2] Phantom job started from another phantom job > > > > A colleague of mine ask me to post this on his behalf. > > > > I have a Phantom job that runs continuously. The job performs > > a select, executes some processing on the records returned > > from the select, and then goes to sleep for a few minutes. > > After sleeping, the process repeats itself. > > I > > recently added an additional step after the processing. This > > step starts another Phantom process which launches a program > > that does a select and processes the results of the select > > and then stops (using CHAIN "OFF"). > > > > The problem is that our system admins have noticed that the > > "child" Phantom processes launched by the parent Phantom > > process go into a state of "defunct" > > from a Unix process perspective. > > > > $ ps -ef | grep defunct > > fhooven 23180 986 18 16:33:12 ? 0:00 > > dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct > > > > The child Phantom process runs successfully and the "defunct" > > process eventually goes away. > > > > Any idea what causes this? > > > > System is Universe 10.0 running on HPUX B.11.11 A > > > > Thanks for you help. > > > > ...Frank Hooven > > --- > > u2-users mailing list > > u2-users@listserver.u2ug.org > > To unsubscribe please visit http://listserver.u2ug.org/ > > --- > > u2-users mailing list > > u2-users@listserver.u2ug.org > > To unsubscribe please visit http://listserver.u2ug.org/ > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
It may sound like a bizarre formula but we are able to control this scenario. We have a background process that runs 24x7. It checks for tasks to do, then goes to sleep, wakes up and checks, etc. If there is some task that needs doing, the phantom process, starts another phantom process and that phantom process starts the actual process that does the work. So phantom watchdog starts a phantom ph.start. ph.start's only task is to start phantom.to.do.actual.work. This method seems to dramatically keep defuct and zombie processes to a substantial minimum. Barry Rogen PNY Technologies, Inc. Senior Programmer/Analyst (973) 515 - 9700 ext 5327 [EMAIL PROTECTED] - Far better it is to dare mighty things, to win glorious triumphs even though checkered by failure, than to rank with those poor spirits who neither enjoy nor suffer much because they live in the gray twilight that knows neither victory nor defeat.t. roosevelt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Eastwood Sent: Friday, May 19, 2006 2:39 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Phantom job started from another phantom job In the main phantom (one spawning the other phantoms), try executing "JOBS" every time it wakes up. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave Sent: Friday, May 19, 2006 10:36 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Phantom job started from another phantom job We tried this and it didn't solve the problem. Thanks for the suggestion. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of roy > Sent: Friday, May 19, 2006 11:58 AM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > > Try executing the VOC item NOTIFY ON see help files > > This finishes the phantom job and delete the process. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave > Sent: Friday, May 19, 2006 10:56 AM > To: u2-users@listserver.u2ug.org > Subject: [U2] Phantom job started from another phantom job > > A colleague of mine ask me to post this on his behalf. > > I have a Phantom job that runs continuously. The job performs > a select, executes some processing on the records returned > from the select, and then goes to sleep for a few minutes. > After sleeping, the process repeats itself. > I > recently added an additional step after the processing. This > step starts another Phantom process which launches a program > that does a select and processes the results of the select > and then stops (using CHAIN "OFF"). > > The problem is that our system admins have noticed that the > "child" Phantom processes launched by the parent Phantom > process go into a state of "defunct" > from a Unix process perspective. > > $ ps -ef | grep defunct > fhooven 23180 986 18 16:33:12 ? 0:00 > dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct > > The child Phantom process runs successfully and the "defunct" > process eventually goes away. > > Any idea what causes this? > > System is Universe 10.0 running on HPUX B.11.11 A > > Thanks for you help. > > ...Frank Hooven > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
In the main phantom (one spawning the other phantoms), try executing "JOBS" every time it wakes up. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave Sent: Friday, May 19, 2006 10:36 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Phantom job started from another phantom job We tried this and it didn't solve the problem. Thanks for the suggestion. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of roy > Sent: Friday, May 19, 2006 11:58 AM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > > Try executing the VOC item NOTIFY ON see help files > > This finishes the phantom job and delete the process. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave > Sent: Friday, May 19, 2006 10:56 AM > To: u2-users@listserver.u2ug.org > Subject: [U2] Phantom job started from another phantom job > > A colleague of mine ask me to post this on his behalf. > > I have a Phantom job that runs continuously. The job performs > a select, executes some processing on the records returned > from the select, and then goes to sleep for a few minutes. > After sleeping, the process repeats itself. > I > recently added an additional step after the processing. This > step starts another Phantom process which launches a program > that does a select and processes the results of the select > and then stops (using CHAIN "OFF"). > > The problem is that our system admins have noticed that the > "child" Phantom processes launched by the parent Phantom > process go into a state of "defunct" > from a Unix process perspective. > > $ ps -ef | grep defunct > fhooven 23180 986 18 16:33:12 ? 0:00 > dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct > > The child Phantom process runs successfully and the "defunct" > process eventually goes away. > > Any idea what causes this? > > System is Universe 10.0 running on HPUX B.11.11 A > > Thanks for you help. > > ...Frank Hooven > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
from what I understood and the problem we were having...yes. yes, they will both work, however, the phantom processes that are forked off, when they end, their PID are not released back into the PID pool until the parent phantom dies. If the parent phantom only forks off a few phantoms it may not be noticable, however, when the parent phantom is forking off 20-30-40 child processes every minute, after about 6-7 hours, this became a major problem having all those zombie processes hanging around. It's also possible this might just be a unix thing, (zombies). It's very possible that eventually the zombie's may be released over some period of time, and with few child processes, it never will become a problem. However, we were using it in conjunction with a webserver, and each cgi request would filter through our phantom and fire off the appropriate program to dynamically create the HTML code that would then get fed back to the cgi. If I'm mistaken, which is very possible :) and our situation was unique, I'm sure the correct information will be proudly posted (which is always a good thing, the truth must be told!). > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Bill Haskett > Sent: Friday, May 19, 2006 1:05 PM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > > > George: > > Are you saying one cannot have a single service manager > program running once > as a phantom, like cron? So, this doesn't work: > > PHANTOM RUN MYCRON > > MYCRON > 001 LOOP > 002...Read if MyCron should be stopped > 003...Stop MyCron if it should be stopped > 004...Read jobs to run > 005IF JobToRun THEN > 006 PHANTOM RUN JOBDEFINITION > 007END > 008SLEEP 60 > 009 REPEAT > > ...but this does: > > PHANTOM RUN MYCRON > > PHANTOM.MYCRON > 001 PA > 002 PHANTOM RUN MYCRON > > MYCRON > 001 LOOP > 002...Read if MyCron should be stopped > 003IF StopMyCron THEN STOP > 004...Read jobs to run > 005IF JobToRun THEN > 006 PHANTOM RUN JOBDEFINITION > 007 CHAIN \PHANTOM.MYCRON\ > 007END > 008SLEEP 60 > 009 REPEAT > > Do I understand this correctly? > > Bill > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > George Gallen > > Sent: Friday, May 19, 2006 8:16 AM > > To: u2-users@listserver.u2ug.org > > Subject: RE: [U2] Phantom job started from another phantom job > > > > After sleeping, instead of the process repeats itself, what > > you need to do is CHAIN"" to itself, this will end that > > phantom, which will release all it's child processes from > > their zombie status. > > > > If you continue to build up zombies, without releaseing them, > > you will eventually get the dreaded "no more processes available" > > message, at which point, UV comes to grinding crash halt, > > until you kill that one repeating phantom, then magically, > > all the processes become available again, and UV picks itself > > up and continues on with life. > > > > The only problem with this method, is you will build up a > > crap load of very small files in the &PHANTOMS& file. We have > > a process which every few days deletes old fileid (using the > > ls to give us the date the file was created, and made our > > &PHANTOMS& file a type 19) > > > > Oh, and YEA, looks like the reply is back to the way it was. > > > > George > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of > Scott, Dave > > > Sent: Friday, May 19, 2006 10:56 AM > > > To: u2-users@listserver.u2ug.org > > > Subject: [U2] Phantom job started from another phantom job > > > > > > > > > A colleague of mine ask me to post this on his behalf. > > > > > > I have a Phantom job that runs continuously. The job performs a > > > select, executes some processing on the records returned from the > > > select, and then goes to sleep for a few minutes. After > > sleeping, the > > > process repeats itself. I recently added an additional step > > after the > > > processing. This step starts another Phantom process which > > launches a > > > program that does a select and processes the results of the > > select and > > > then stops (using CHAIN "OFF"). > > > > > > The problem
RE: [U2] Phantom job started from another phantom job
We tried this and it didn't solve the problem. Thanks for the suggestion. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of roy > Sent: Friday, May 19, 2006 11:58 AM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > > Try executing the VOC item NOTIFY ON see help files > > This finishes the phantom job and delete the process. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave > Sent: Friday, May 19, 2006 10:56 AM > To: u2-users@listserver.u2ug.org > Subject: [U2] Phantom job started from another phantom job > > A colleague of mine ask me to post this on his behalf. > > I have a Phantom job that runs continuously. The job performs > a select, executes some processing on the records returned > from the select, and then goes to sleep for a few minutes. > After sleeping, the process repeats itself. > I > recently added an additional step after the processing. This > step starts another Phantom process which launches a program > that does a select and processes the results of the select > and then stops (using CHAIN "OFF"). > > The problem is that our system admins have noticed that the > "child" Phantom processes launched by the parent Phantom > process go into a state of "defunct" > from a Unix process perspective. > > $ ps -ef | grep defunct > fhooven 23180 986 18 16:33:12 ? 0:00 > dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct > > The child Phantom process runs successfully and the "defunct" > process eventually goes away. > > Any idea what causes this? > > System is Universe 10.0 running on HPUX B.11.11 A > > Thanks for you help. > > ...Frank Hooven > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
George: Are you saying one cannot have a single service manager program running once as a phantom, like cron? So, this doesn't work: PHANTOM RUN MYCRON MYCRON 001 LOOP 002...Read if MyCron should be stopped 003...Stop MyCron if it should be stopped 004...Read jobs to run 005IF JobToRun THEN 006 PHANTOM RUN JOBDEFINITION 007END 008SLEEP 60 009 REPEAT ...but this does: PHANTOM RUN MYCRON PHANTOM.MYCRON 001 PA 002 PHANTOM RUN MYCRON MYCRON 001 LOOP 002...Read if MyCron should be stopped 003IF StopMyCron THEN STOP 004...Read jobs to run 005IF JobToRun THEN 006 PHANTOM RUN JOBDEFINITION 007 CHAIN \PHANTOM.MYCRON\ 007END 008SLEEP 60 009 REPEAT Do I understand this correctly? Bill > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of George Gallen > Sent: Friday, May 19, 2006 8:16 AM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Phantom job started from another phantom job > > After sleeping, instead of the process repeats itself, what > you need to do is CHAIN"" to itself, this will end that > phantom, which will release all it's child processes from > their zombie status. > > If you continue to build up zombies, without releaseing them, > you will eventually get the dreaded "no more processes available" > message, at which point, UV comes to grinding crash halt, > until you kill that one repeating phantom, then magically, > all the processes become available again, and UV picks itself > up and continues on with life. > > The only problem with this method, is you will build up a > crap load of very small files in the &PHANTOMS& file. We have > a process which every few days deletes old fileid (using the > ls to give us the date the file was created, and made our > &PHANTOMS& file a type 19) > > Oh, and YEA, looks like the reply is back to the way it was. > > George > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Scott, Dave > > Sent: Friday, May 19, 2006 10:56 AM > > To: u2-users@listserver.u2ug.org > > Subject: [U2] Phantom job started from another phantom job > > > > > > A colleague of mine ask me to post this on his behalf. > > > > I have a Phantom job that runs continuously. The job performs a > > select, executes some processing on the records returned from the > > select, and then goes to sleep for a few minutes. After > sleeping, the > > process repeats itself. I recently added an additional step > after the > > processing. This step starts another Phantom process which > launches a > > program that does a select and processes the results of the > select and > > then stops (using CHAIN "OFF"). > > > > The problem is that our system admins have noticed that the "child" > > Phantom processes launched by the parent Phantom process go into a > > state of "defunct" > > from a Unix process perspective. > > > > $ ps -ef | grep defunct > > fhooven 23180 986 18 16:33:12 ? 0:00 > > dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct > > > > The child Phantom process runs successfully and the > "defunct" process > > eventually goes away. > > > > Any idea what causes this? > > > > System is Universe 10.0 running on HPUX B.11.11 A > > > > Thanks for you help. > > > > ...Frank Hooven > > --- > > u2-users mailing list > > u2-users@listserver.u2ug.org > > To unsubscribe please visit http://listserver.u2ug.org/ > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
Don't chain to off. Just stop the program and it will release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave Sent: Friday, May 19, 2006 9:56 AM To: u2-users@listserver.u2ug.org Subject: [U2] Phantom job started from another phantom job A colleague of mine ask me to post this on his behalf. I have a Phantom job that runs continuously. The job performs a select, executes some processing on the records returned from the select, and then goes to sleep for a few minutes. After sleeping, the process repeats itself. I recently added an additional step after the processing. This step starts another Phantom process which launches a program that does a select and processes the results of the select and then stops (using CHAIN "OFF"). The problem is that our system admins have noticed that the "child" Phantom processes launched by the parent Phantom process go into a state of "defunct" from a Unix process perspective. $ ps -ef | grep defunct fhooven 23180 986 18 16:33:12 ? 0:00 dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct The child Phantom process runs successfully and the "defunct" process eventually goes away. Any idea what causes this? System is Universe 10.0 running on HPUX B.11.11 A Thanks for you help. ...Frank Hooven --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
George, Are you saying that a phantom process launched from another phantom process "hangs around" in a defunct state after completing until the parent phantom process ends? Ouch! Thanks for you feedback. ...ds From: [EMAIL PROTECTED] on behalf of George Gallen Sent: Fri 5/19/2006 11:16 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Phantom job started from another phantom job After sleeping, instead of the process repeats itself, what you need to do is CHAIN"" to itself, this will end that phantom, which will release all it's child processes from their zombie status. If you continue to build up zombies, without releaseing them, you will eventually get the dreaded "no more processes available" message, at which point, UV comes to grinding crash halt, until you kill that one repeating phantom, then magically, all the processes become available again, and UV picks itself up and continues on with life. The only problem with this method, is you will build up a crap load of very small files in the &PHANTOMS& file. We have a process which every few days deletes old fileid (using the ls to give us the date the file was created, and made our &PHANTOMS& file a type 19) Oh, and YEA, looks like the reply is back to the way it was. George > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Scott, Dave > Sent: Friday, May 19, 2006 10:56 AM > To: u2-users@listserver.u2ug.org > Subject: [U2] Phantom job started from another phantom job > > > A colleague of mine ask me to post this on his behalf. > > I have a Phantom job that runs continuously. The job performs > a select, > executes some processing on the records returned from the > select, and then > goes to sleep for a few minutes. After sleeping, the process > repeats itself. I > recently added an additional step after the processing. This > step starts > another Phantom process which launches a program that does a > select and > processes the results of the select and then stops (using > CHAIN "OFF"). > > The problem is that our system admins have noticed that the > "child" Phantom > processes launched by the parent Phantom process go into a > state of "defunct" > from a Unix process perspective. > > $ ps -ef | grep defunct > fhooven 23180 986 18 16:33:12 ? 0:00 > dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct > > The child Phantom process runs successfully and the "defunct" process > eventually goes away. > > Any idea what causes this? > > System is Universe 10.0 running on HPUX B.11.11 A > > Thanks for you help. > > ...Frank Hooven > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type application/ms-tnef which had a name of winmail.dat] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
Try executing the VOC item NOTIFY ON see help files This finishes the phantom job and delete the process. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott, Dave Sent: Friday, May 19, 2006 10:56 AM To: u2-users@listserver.u2ug.org Subject: [U2] Phantom job started from another phantom job A colleague of mine ask me to post this on his behalf. I have a Phantom job that runs continuously. The job performs a select, executes some processing on the records returned from the select, and then goes to sleep for a few minutes. After sleeping, the process repeats itself. I recently added an additional step after the processing. This step starts another Phantom process which launches a program that does a select and processes the results of the select and then stops (using CHAIN "OFF"). The problem is that our system admins have noticed that the "child" Phantom processes launched by the parent Phantom process go into a state of "defunct" from a Unix process perspective. $ ps -ef | grep defunct fhooven 23180 986 18 16:33:12 ? 0:00 dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct The child Phantom process runs successfully and the "defunct" process eventually goes away. Any idea what causes this? System is Universe 10.0 running on HPUX B.11.11 A Thanks for you help. ...Frank Hooven --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Phantom job started from another phantom job
After sleeping, instead of the process repeats itself, what you need to do is CHAIN"" to itself, this will end that phantom, which will release all it's child processes from their zombie status. If you continue to build up zombies, without releaseing them, you will eventually get the dreaded "no more processes available" message, at which point, UV comes to grinding crash halt, until you kill that one repeating phantom, then magically, all the processes become available again, and UV picks itself up and continues on with life. The only problem with this method, is you will build up a crap load of very small files in the &PHANTOMS& file. We have a process which every few days deletes old fileid (using the ls to give us the date the file was created, and made our &PHANTOMS& file a type 19) Oh, and YEA, looks like the reply is back to the way it was. George > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Scott, Dave > Sent: Friday, May 19, 2006 10:56 AM > To: u2-users@listserver.u2ug.org > Subject: [U2] Phantom job started from another phantom job > > > A colleague of mine ask me to post this on his behalf. > > I have a Phantom job that runs continuously. The job performs > a select, > executes some processing on the records returned from the > select, and then > goes to sleep for a few minutes. After sleeping, the process > repeats itself. I > recently added an additional step after the processing. This > step starts > another Phantom process which launches a program that does a > select and > processes the results of the select and then stops (using > CHAIN "OFF"). > > The problem is that our system admins have noticed that the > "child" Phantom > processes launched by the parent Phantom process go into a > state of "defunct" > from a Unix process perspective. > > $ ps -ef | grep defunct > fhooven 23180 986 18 16:33:12 ? 0:00 > dscott 23302 23199 1 16:33:32 pts/tW0:00 grep defunct > > The child Phantom process runs successfully and the "defunct" process > eventually goes away. > > Any idea what causes this? > > System is Universe 10.0 running on HPUX B.11.11 A > > Thanks for you help. > > ...Frank Hooven > --- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
