How to find Process corresponding to instance
A user running three IDS 11.10 instances on Solaris 10 saw identical "oninit -v" entries in ps -aef and couldn't tell which process belonged to which instance. The answer: set your environment (INFORMIXSERVER/ONCONFIG) for each instance and run "onstat -g glo", which lists the PIDs of the virtual processors for that instance. Others suggested making the mapping visible in ps output by starting each server via a per-instance link/copy of oninit (e.g. oninit.servername, invoked by full path), with Jonathan Leffler preferring hard links over symlinks.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hello !
IDS 11.10 on solaris 10
i have 3 instances on my machine and when i do ps -aef |grep informix
i see these 3 lines correspoinding to 3 instances (i guess),
informix 26810 1 0 Jun 17 ? 2:05 oninit -v
informix 19816 1 0 Jun 12 ? 4:44 oninit -v
informix 2861 1 0 May 20 ? 8:02 oninit -v
now, how do i find that which process belongs to which instance?
Thanking you all in advance.
Regards
vikas.
Hi,
try "onstat -g glo" in each environment you will see all the VP's with
their process-number.
Jacques Lapeire
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
VIKAS HIVARKAR
Sent: dinsdag 24 juni 2008 13:31
To: ids@iiug.org
Subject: How to find Process corresponding to instance [12491]
Hello !
IDS 11.10 on solaris 10
i have 3 instances on my machine and when i do ps -aef |grep informix
i see these 3 lines correspoinding to 3 instances (i guess),
informix 26810 1 0 Jun 17 ? 2:05 oninit -v
informix 19816 1 0 Jun 12 ? 4:44 oninit -v
informix 2861 1 0 May 20 ? 8:02 oninit -v
now, how do i find that which process belongs to which instance?
Thanking you all in advance.
Regards
vikas.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
Set your environment to one of the instances and run:
onstat -g glo
it will list the pids of all of the oninit processes that belong to that
instance.
Art
On Tue, Jun 24, 2008 at 7:31 AM, VIKAS HIVARKAR <vikas.hivarkar@tcs.com>
wrote:
> Hello !
>
> IDS 11.10 on solaris 10
>
> i have 3 instances on my machine and when i do ps -aef |grep informix
> i see these 3 lines correspoinding to 3 instances (i guess),
>
> informix 26810 1 0 Jun 17 ? 2:05 oninit -v
> informix 19816 1 0 Jun 12 ? 4:44 oninit -v
> informix 2861 1 0 May 20 ? 8:02 oninit -v
>
> now, how do i find that which process belongs to which instance?
>
> Thanking you all in advance.
> Regards
> vikas.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do those
opinions reflect those of other individuals affiliated with any entity with
which I am affiliated nor those of the entities themselves.
One thing we do to keep track of pids easily is create a link called oninit in
a directory specific to each $INFORMIXSERVER. We point the link to
$INFORMIXDIR/bin/oninit and start the engine by executing the link. Be careful
doing this...
When we look at ps output we see:
% ps -eaf | grep oninit
informix 10828 10818 0 May 06 ? 4323:34 prodms/oninit -v
informix 9872 1 2 May 06 ? 4308:21 prodms/oninit -v
informix 516 512 0 May 06 ? 7982:35 pro/oninit -v
informix 10841 10818 0 May 06 ? 2248:59 prodms/oninit -v
informix 540 512 0 May 06 ? 5948:03 pro/oninit -v
informix 10858 10818 0 May 06 ? 2156:21 prodms/oninit -v
informix 29978 1 2 May 06 ? 8407:39 pro/oninit -v
informix 26510 26396 0 Jun 16 ? 1715:51 prodb/oninit -v
informix 26445 26396 0 Jun 16 ? 2215:34 prodb/oninit -v
informix 531 512 0 May 06 ? 6801:04 pro/oninit -v
informix 523 512 0 May 06 ? 7974:36 pro/oninit -v
informix 26479 26396 0 Jun 16 ? 1803:26 prodb/oninit -v
informix 26413 26396 0 Jun 16 ? 2660:16 prodb/oninit -v
informix 24429 1 0 Jun 16 ? 2599:32 prodb/oninit -v
I've also seen links like the following used at some sites:
ln -s $INFORMIXDIR/bin/myserver_oninit $INFORMIXDIR/bin/oninit
Not fond of the practice myself, but the argument is that then the SA's who
don't need to know how to track down which server is causing trouble can
join the monitoring effort.
Art
On Tue, Jun 24, 2008 at 11:47 AM, MIKE MAGIE <jmmagie@yahoo.com> wrote:
> One thing we do to keep track of pids easily is create a link called oninit
> in
> a directory specific to each $INFORMIXSERVER. We point the link to
> $INFORMIXDIR/bin/oninit and start the engine by executing the link. Be
> careful
> doing this...
>
> When we look at ps output we see:
>
> % ps -eaf | grep oninit>
> informix 10828 10818 0 May 06 ? 4323:34 prodms/oninit -v
> informix 9872 1 2 May 06 ? 4308:21 prodms/oninit -v
> informix 516 512 0 May 06 ? 7982:35 pro/oninit -v
> informix 10841 10818 0 May 06 ? 2248:59 prodms/oninit -v
> informix 540 512 0 May 06 ? 5948:03 pro/oninit -v
> informix 10858 10818 0 May 06 ? 2156:21 prodms/oninit -v
> informix 29978 1 2 May 06 ? 8407:39 pro/oninit -v
> informix 26510 26396 0 Jun 16 ? 1715:51 prodb/oninit -v
> informix 26445 26396 0 Jun 16 ? 2215:34 prodb/oninit -v
> informix 531 512 0 May 06 ? 6801:04 pro/oninit -v
> informix 523 512 0 May 06 ? 7974:36 pro/oninit -v
> informix 26479 26396 0 Jun 16 ? 1803:26 prodb/oninit -v
> informix 26413 26396 0 Jun 16 ? 2660:16 prodb/oninit -v
> informix 24429 1 0 Jun 16 ? 2599:32 prodb/oninit -v
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do those
opinions reflect those of other individuals affiliated with any entity with
which I am affiliated nor those of the entities themselves.
Well, apart from fixing the order of the arguments in the 'ln'
command, avoiding symlinks (something resolves the name; using a hard
link works better for me) and using oninit.servername instead of
servername_oninit, this is what I do on my main machine, combined with
ensuring that oninit is always run with the full pathname
($INFORMIXDIR/bin/oninit.server), and then I have a record of the
server name and the Informix directory readily visible in the 'ps -ef'
output. Personally, I find that useful, especially given the esoteric
collection of instances I have on my machine.
On Tue, Jun 24, 2008 at 9:09 AM, Art Kagel <art.kagel@gmail.com> wrote:
> I've also seen links like the following used at some sites:
>
> ln -s $INFORMIXDIR/bin/myserver_oninit $INFORMIXDIR/bin/oninit
>
> Not fond of the practice myself, but the argument is that then the SA's who
> don't need to know how to track down which server is causing trouble can
> join the monitoring effort.
>
> Art
>
> On Tue, Jun 24, 2008 at 11:47 AM, MIKE MAGIE <jmmagie@yahoo.com> wrote:
>
>> One thing we do to keep track of pids easily is create a link called oninit
>> in
>> a directory specific to each $INFORMIXSERVER. We point the link to
>> $INFORMIXDIR/bin/oninit and start the engine by executing the link. Be
>> careful
>> doing this...
>>
>> When we look at ps output we see:
>>
>> % ps -eaf | grep oninit>>
>> informix 10828 10818 0 May 06 ? 4323:34 prodms/oninit -v
>> informix 9872 1 2 May 06 ? 4308:21 prodms/oninit -v
>> informix 516 512 0 May 06 ? 7982:35 pro/oninit -v
>> informix 10841 10818 0 May 06 ? 2248:59 prodms/oninit -v
>> informix 540 512 0 May 06 ? 5948:03 pro/oninit -v
>> informix 10858 10818 0 May 06 ? 2156:21 prodms/oninit -v
>> informix 29978 1 2 May 06 ? 8407:39 pro/oninit -v
>> informix 26510 26396 0 Jun 16 ? 1715:51 prodb/oninit -v
>> informix 26445 26396 0 Jun 16 ? 2215:34 prodb/oninit -v
>> informix 531 512 0 May 06 ? 6801:04 pro/oninit -v
>> informix 523 512 0 May 06 ? 7974:36 pro/oninit -v
>> informix 26479 26396 0 Jun 16 ? 1803:26 prodb/oninit -v
>> informix 26413 26396 0 Jun 16 ? 2660:16 prodb/oninit -v
>> informix 24429 1 0 Jun 16 ? 2599:32 prodb/oninit -v
>>
>>
>>
>>
>
*******************************************************************************
>> Forum Note: Use "Reply" to post a response in the discussion forum.
>>
>>
>
> --
> Art S. Kagel
> Oninit (www.oninit.com)
> IIUG Board of Directors (art@iiug.org)
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions and
> do not reflect on my employer, Oninit, the IIUG, nor any other organization
> with which I am associated either explicitly or implicitly. Neither do those
> opinions reflect those of other individuals affiliated with any entity with
> which I am affiliated nor those of the entities themselves.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2008.0513 -- http://dbi.perl.org/
"Blessed are we who can laugh at ourselves, for we shall never cease
to be amused."
NB: Please do not use this email for correspondence.
I don't necessarily read it every week, even.