Comments on: Unable to start HTTP server after restore

By: Takumi

Takumi — Tue, 15 Feb 2011 10:50:47 +0000

Many Thankssssss!!!!!! I had the same problem!!!

By: alka

alka — Mon, 14 Feb 2011 12:31:57 +0000

Hi all,
Just have the same error and I fixed it as follow:
1. Stop the OMS, Application Server Control (if running) from this OMS Home:
/opmn/bin
opmnctl stopall
emctl stop iasconsole

2. Check for any and defunct /stuck processes:
$ ps -ef |grep oms10g
$ ps -ef |grep httpd

From the ‘ps’ output, check for any processes that have been started from the ‘oms10g’ path.
===> If any process is still present, kill them using the command : kill -9

3. Take a backup and all the below files to clean up the OMS environment:
/opmn/logs/*.*
/opmn/logs/states/*
/Apache/Apache/logs/*
/j2ee/OC4J_EM/persistence/OC4J_EM_default_island_1/*
/j2ee/OC4J_EMPROV/persistence/OC4J_EMPROV_default_island_1/*
/j2ee/home/persistence/home_default_island_1/*

4.Start the OMS
/opmn/bin
opmnctl startall

Thanks

By: dberthel

dberthel — Thu, 25 Mar 2010 11:04:37 +0000

And please, read Note 436690.1 on the subject (logs does not rotate)

By: dberthel

dberthel — Thu, 25 Mar 2010 10:44:16 +0000

One other solution /* before */ changing any configuration

Go to the directory $OMS_HOME/Apache/Apache/logs then
rm error_log *.sem access_log

Cause could be an $OMS_HOME/Apache/Apache/logs/error_log file to large

By: chris smith

chris smith — Wed, 21 Oct 2009 20:17:42 +0000

I had a similar issue. Same error. my .apachectl file is owned by oracle and that seems to work.
Stopped everything including the database (check for leftover processes ps -ef). My home/oms/Appache/Appache/logs directory was really full. Cleared out the logs and deleted the httpd.pid file.
did ./opmctl startall.

took a while but eventually came back. I think the httpd.pid file was the key but i can’t be sure.

thanks
Chris

By: PeterPaul

PeterPaul — Thu, 20 Aug 2009 07:02:10 +0000

Thanks Frits for the addition. Indeed we used tar, and a “normal user” to restore.

By: Frits Hoogland

Frits Hoogland — Wed, 19 Aug 2009 20:10:36 +0000

It’s only needed to set SUID and SGID if the port or ports on which the webserver is set to run is < 1024 and if it’s on unix or linux.

indeed the daemon itself then runs using UID ’0′, the ‘childs’ of the daemon (with which clients communicate) run with the userid and groupid set in the apache configuration.

compression does not reset file properties. if using tar, there are limitations on the properties of files, like rights, ownership, etc. (a normal user can not restore a file with root ownership and SUID and/or SGID bits)