Re: Determining instance's oninits

Then try and kill the shared memory ones first. ipcrm -m [segid]. Determine which instance they belong to by the SERVERNUM. They all should equal a certain key + the servernum. It looks like you have 3 instances, the segments end in 4801, 4802 and 4803. the servernums on the instance are one apart. Lets say that your SERVERNUMS are 1 2 and 3, and you want to kill the one whose servernum is 2. Then ipcrm -m [the ones that end in 4802 ]. That may make the root owned semaphore go away. If not then you need root privs. ( I guess the instance was started as root ] Or, you can shutdown the other instances, and the ones that are left belong to this instance. ----- Original Message ----- From: "red_valsen" <red_valsen@yahoo.com> Sent: Fri, March 6, 2009 16:52 Subject:Re: Determining instance's oninits On Mar 6, 2:55 pm, "Floyd Wellershaus" <fl...@fwellers.com> wrote: > Did you also remove the semaphores ? > ipcrm -m AND ipcrm -s > > ----- Original Message ----- > From: "red_valsen" <red_val...@yahoo.com> > Sent: Fri, March 6, 2009 13:56 > Subject:Re: Determining instance's oninits > > On Mar 6, 9:34 am, theBP <th...@Usenet-News.Net> wrote: > > red_val...@yahoo.com wrote: > > > I have 3 informixservers running on a single host. One of the > > > instances has experienced an assertion failure and is now > > > unresponsive, so I'd like to kill its oninit processes and attempt to > > > restart it. But running onstat -g ses only reports a PID of 0 for the > > > oninit sessions. How do I determine which oninit processes are > > > associated with which instances? > > > > Running IDS 9.40FC8 on HPUX11. > > > onstat -g glo> > > Establish the main CPU VP. > > > Get an onstat -g stk all first, and an onstat -a for diagnostics. > > Thank you. > > Now that I've been able to identify the oninit processes for the > instance by ID, I've deleted them. But even after using ipcrm to > remove the now-dead instance's shared memory segments, they are still > being reported as being referenced by the O/S (ipcs status 'D'), > preventing the informixserver from being restarted. All the oninit > processes for the instance were killed. At this point is there an > alternative to using the Microsoft solution and rebooting the host? > _______________________________________________ > Informix-list mailing list > Informix-l...@iiug.orghttp://www.iiug.org/mailman/listinfo/informix-list > > ----- End of original message ----- No other onstats lurking. Haven't found a way to determine who owns which semaphores -- root ownership prevents dropping them: informix@hrmis11:/home/informix/smitht/work/030609: ipcs|grep inf m 2359303 0x525d4801 --rw-rw---- root informix m 8 0x525d4802 --rw-rw---- root informix m 163849 0x525d4803 --rw-rw-rw- root informix m 196618 0x525f4801 --rw-rw---- root informix m 98315 0x525f4802 --rw-rw---- root informix m 262156 0x525f4803 --rw-rw-rw- root informix m 163853 0x52604801 --rw-rw---- root informix m 65550 0x52604802 --rw-rw---- root informix m 163855 0x52604803 --rw-rw-rw- root informix m 458768 0x00000000 D-rw-rw---- informix informix m 1769489 0x00000000 D-rw-rw---- informix informix m 720914 0x00000000 D-rw-rw---- informix informix m 32802 0x52604804 --rw-rw---- informix informix m 32803 0x52604805 --rw-rw---- informix informix m 32804 0x52604806 --rw-rw---- informix informix s 30 0x00000000 --ra-ra---- root informix s 31 0x00000000 --ra-ra-ra- root informix s 32 0x00000000 --ra-ra---- root informix s 33 0x00000000 --ra-ra-ra- root informix s 34 0x00000000 --ra-ra---- root informix s 35 0x00000000 --ra-ra-ra- root informix _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list ----- End of original message -----