[NBLUG/talk] php5 apache2 WON'T DIE

[Robert Hayes]

Eric,

Thank you. Your suggestions helped. I'm sure it's no surprise to any members 
of this mailing list that you knew commands that most of us had not heard of.

I didn't explain my actions very thoroughly. By the time I wrote I was 
thinking in shorthand and regressing into an earlier lifeform as a result of 
the frustration. 

I did use apt to install and remove all of the packages. But lsof revealed all 
sorts of things that were persistently running.

I ended up reinstalling egroupware, calling for the 'egroupware-core' package 
instead of just 'egroupware' (they both install, but different versions 
(egroupware-core:v1.06 and egroupware: v1.04). That seemed to get everything 
into alignment. 

Apparently php5 does not include mysql extensions in the package and while 
that is the preferred build for the latest version of egroupware, in addition 
there are some known bugs in php5 that cause 'haystack' errors that break the 
display of data.

Everything is running now, with php4, mysql5 , and egroupware 1.06.

After that happened I gave way to the primal instincts and fairly *ran* away 
from my keyboard (after locking the console, there was a small piece of 
modern man left in me) and went outside to ogle the big yellow ball in the 
sky.

Thanks again, Eric

Bob

On Saturday 19 May 2007 15:44, Eric Eisenhart wrote:
> On Sat, May 19, 2007 at 01:46:20PM -0700, Robert Hayes wrote:
> > I removed apache2, and php5, installed apache (1.3) and php4, and php5
> > and apache2 keep coming up.
> >
> > I've ripped the directories out by the roots manually from a console.
> > They still keep coming up.
> >
> > Years ago I went on vacation for a week and left my VW parked next to
> > some kudzu vine. When I came home six days later the kudzu had crawled up
> > the tires, over the fenders and the two sides were weaving together
> > across the hood.
> >
> > That was funny. This isn't.
> >
> > Any guidance, please.
>
> lsof.
>
> Specifically, look for the process id of the process that  you don't want,
> and run something like "lsof -p 317".  One of the very first things listed
> will be the executable that it ran from, followed by lots of libraries (and
> other dynamically loaded objects, aka ".so files").
>
> Another thing to try.  Get the process ID again.  Usually there's one
> httpd/apache process running as root and the rest as "apache" or "http" or
> "www-data" -- for the lsof thing it didn't matter which you got, for this
> you really need the one that's running as root.
> "strace -p 317"
> Then in another console, "kill -HUP 317"
>
> This will tell the apache process to reload its configuration, which will
> naturally involve loading all the configuration files.
>
> And, of course, "ps auxfw" is handy for this kind of thing.
>
> You didn't mention which distro you're using, but I would definitely
> recommend using the information you gather from the above to find out which
> package has the files causing you the problems, and tell the package
> management system to remove those packages...  Try working with your
> package management system before ripping things out manually, or you risk
> leaving roots that will sprout again and you'll never get the kudzu out of
> your engine compartment.