View Single Post

   
  #5 (permalink)  
Old 04-20-2008, 03:35 PM
John Carlson
 
Posts: n/a
Default Re: Confused engine: No SHM segments but thinks it is quiescent

On 21 May 2007 21:40:54 -0700, Beau Nanaz <spamntrapf@yahoo.com>
wrote:

>Hi again, family.
>
>This time I can contribute a solution because it happened again and I
>was able to pay attention to the messages when I tried to bounce the
>engine in an attempt to cure the ghost "quiescent mode" messages.
>
>I don't have that session open in front of me now but when I tried to
>start the engine I got "Error in shared memory initialization" with an
>error number. Finderr on that error number said something about ports
>already in use. AHA! The TCP port must still be occupied. But by
>*whom*? And which TCP port?
>
>The second question was easier - I grep the sqlhosts file for the name
>of my server and turned a port named sqlexec_Y. I then use the
>recently-learned Unix utility, lsof:
>$ lsof | grep sqlexec_Y
>
>This turned up a bunch of oninit processes. I was still monitoring
>the online.log file (tail -f &) so I could see the results of my
>actions. I killed the first oninit process in the list and watched
>"The master daemon has died" and "Attempting to bring system down".
>
>Now I could bring up the engine normally, with the original SHM
>allocations. Hurrah! Pat myself on the back. (Hey, I can *wash* my
>own back ;-)
>
>(I should confess that my first responses to the shared-memory
>messages were to reduce the BUFFER and SHMINIT parameters but it got
>to the point where I could proved they were not a memory issue.)
>
>Now *that* was fun!
>


There is a great feeling when your "detective work" pays off . . . .
and a lesson not soon forgotten . . . great job!

JWC
Reply With Quote