Can't Kill HTTPD Process

romeo_tango · 01-04-2011, 01:18 AM

okay already went throught it.

Code:

#svcs -xv http:apache2
svc:/network/http:apache2 (Apache 2 HTTP server)
 State: maintenance since Mon Dec 13 16:02:19 2010
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
   See: http://sun.com/msg/SMF-8000-KS
   See: man -M /usr/apache2/man -s 8 httpd
   See: /var/svc/log/network-http:apache2.log
Impact: This service is not running.

The /var/svc/log/network-http:apache2.log showed :

Code:

[ Dec 13 16:02:18 Executing start method ("/lib/svc/method/http-apache2 start") ]
[ Dec 13 16:02:19 Method "start" exited with status 96 ]

And also I checked this :

Code:

#find / -name httpd
/usr/apache/bin/httpd
/usr/apache2/bin/httpd
/usr/local/apache2/bin/httpd

I believe it showed 3 apaches in the system. Both in /usr/apache are by systems default and what I installed was in /usr/local/apache. Perhaps the apache2 svc above cannot be started because the port 80 is already been used by the /usr/local/apache (perhaps).

Now if my assumption is right I'll go back to my very first questions.. why did the /usr/local/apache could not be stopped? and it also couldn't be restarted. At first I read that it might be because the SMF is controlling the apache, but at this moment from facts that I've gathered it seems that the SMF was not in control. I even can't 'kill 9' any single httpd process at that moment.

jlliagre · 01-04-2011, 04:31 AM

Why did you install apache2 while it was already bundled with the OS ?

The Solaris service is handling the /usr/apache2 installation. You should disable (or reconfigure it to use a different port) it if you want to use the one in /usr/local/apache2.

About the processes not dying after a "kill -9", they are stuck in the kernel for some reason.

romeo_tango · 01-04-2011, 08:29 PM

Quote:

Originally Posted by jlliagre

Why did you install apache2 while it was already bundled with the OS ?

The Solaris service is handling the /usr/apache2 installation. You should disable (or reconfigure it to use a different port) it if you want to use the one in /usr/local/apache2.

About the processes not dying after a "kill -9", they are stuck in the kernel for some reason.

Because I don't know it was there. I'm not the one who installed the OS and we needed the newest apache at that time.

Okay, that's what also I have in mine. I'll try to configure or disable the /usr/apache2 then and hope that the /usr/local/apache2 will be fine after that.

Thank you very much.

ADxD_7 · 01-05-2011, 06:10 PM

I would also suggest just changing the manifest script to run the /usr/local/apache2 you want it to - it is always good practice to use SMF - all you would need to do is edit /lib/svc/method/http-apache2 and change everything to reflect the /usr/local location of apache2 - then use svc commands to manage the service

jlliagre · 01-06-2011, 01:30 AM

That should work but beware a future Solaris patch might restore the modified files to using the regular apache2 instance. Better to create a separated SMF service.