Re: sqlexecd...double daemon?!

You can need more than one sqlexecd process if you have multiple OnLine systems on a single machine -- or if you have both OnLine and SE -- and all the systems are being accessed remotely. You should be able to detect service name arguments (ps -ef or ps -ax) which will indicate if this is the case. Note that when sqlexecd detects a connection request, it will fork and the child will exec sqlexec (or sqlturbo). So, ensure that the duplicate process isn't just a transient detected between the fork and the exec -- rerun ps should indicate that. You can also investigate whether the two sqlexecds are parent and child. If so, then maybe the child is hung waiting permission to connect to the database -- but I think it would show up as an sqlturbo at that point, rather than as an sqlexecd. However, multiple sqlexecd processes is more usually a symptom of a problem. Given that you have a permanent duplicate sqlexecd, you do definitely have a problem. I'd be inclined to kill both and then restart one. This has to be done as root, of course. What else can cause this? Manual restarts, of course, but you'd know about that unless someone else was trying to be clever. Semi-automatic restarts can occur if sqlexecd is being managed by some system daemon which starts it on request. Etc. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> >From: mail04168@pop.net >Date: 12 Jun 1995 17:54:25 GMT >X-Informix-List-Id: <news.14615> > >Has anyone ever have a problem with /usr/informix/lib/sqlexecd >where it appears twice under different dates...and locks out >remote access? > >To my understanding...there should only be one daemon >running and that another one starting up on its own is a mystery! >If anyone has any ideas of how this can occur, please do reply. > >Thanks in advance. > >Ken >System Administrator