topic Re: Oracle Web Listener in Operating System - HP-UX

Oracle Web Listener

Jim Tyler_2 — Mon, 13 Jan 2003 19:57:01 GMT

Problem starting Oracle WEB Listener Error Message Follows:

Error: A failure occurred ( Permission denied ) when assigning a port ( domain: ocdev5, address: 0.0.0.0, port: 80 ).
Error: Failed to start the server.
Error: The server could not initialize
Information: The server is exiting
OWS-08811: Unable to startup Oracle Web Listener `www'.

Re: Oracle Web Listener

John Poff — Mon, 13 Jan 2003 20:11:55 GMT

Could another server program be running already and using port 80? I'd try using 'lsof' to see if something else has that port open.

JP

Re: Oracle Web Listener

Brian Crabtree — Mon, 13 Jan 2003 20:54:19 GMT

From metalink:

The oasroot.sh script needs to be run as root
from the $ORACLE_HOME/ows/4.0/install/ directory.

Brian

Re: Oracle Web Listener

Indira Aramandla — Tue, 14 Jan 2003 04:40:06 GMT

Hi Jim,

OWS-08811: Unable to startup Oracle Web Listener `www'.

When you got this error did you check the listener error log file, you see the following errors:
The listener error log can be found at the location: $ORAWEB_ADMIN/$ORAWEB_SITE/httpd_//.err
A required parameter, ServerPID, specified in the listener configuration file is missing or has become corrupted. This parameter provides the full path of the file to which the WAS listener will write its process id (PID) when it starts up. The current value for this parameter can be viewed using the OAS node manager to select HTTP listeners->myhost:WWW->Network in the tree applet. The value for the ServerPID parameter is displayed in the field labeled Listener PID file. This value can also be accessed and modified using a standard UNIX text editor such as VI or EMACS. Since the format of this file is highly sensitive it is recommended that you make a backup copy prior to making modifications.
During startup, OAS needs to write to a file where it stores the process IDs for active listener processes and failure to obtain the correct location of this file prevents an OAS listener from starting. This note supplies a manual procedure for supplying the parameter that is missing from the listener configuration file, thereby allowing the OAS listener to start.

Re: Oracle Web Listener

T G Manikandan — Tue, 14 Jan 2003 04:52:58 GMT

Try running oasroot.sh.

Re: Oracle Web Listener

T G Manikandan — Tue, 14 Jan 2003 04:55:51 GMT

Metalink tells the files inside

$ORACLE_HOME/ows/4.0/bin
should have root permissions.

-rwsr-sr-x 1 root other 16028 Okt 5 1998 apchlctl

-rwsr-sr-x 1 root dba 1911756 Nov 4 1998 oraweb

-rwsr-xr-x 1 root other 10840 Okt 5 1998 owslctl

Re: Oracle Web Listener

Jeffrey Killian — Tue, 14 Jan 2003 13:27:46 GMT

My experience is with Weblogic webserver, Tuxedo application server, and Oracle database. We have had similar issues with the web server not starting because of another process (thus far always the Work Station Handler from the application server) that is hogging the port. (Use "ps -ef" and grep for the port number - in your case 80 - to identify what is using that port.)

Even after shutting down the app server, the WSH process still remains active so I have had to kill it. Then restarting the app server and webserver works fine.

Good luck!

Re: Oracle Web Listener

Steven E. Protter — Tue, 14 Jan 2003 20:51:50 GMT

Oracle web listener is really apache.

without running the oasroot.sh script it will never run because root permissions are required for any port below 1024

Could this however be more basic?

If its not oasroot.sh could it be a problem with httpd.conf?

Lets say you have a named web server Servername schmobagel.com

and schmobagel.com doesn't resolve.

Or you have an IP based name and you don't have that IP addressed configured in /etc/rc.config.d/netconf

Check that your basic networking is working and matches httpd.conf

I like the oasroot.sh solution but I'd think a better error message would include the IP address of the HP server.

Here is what metalink has to say about the error.

PURPOSE ------- This Note is an attempt to summarize the many Notes related to the OWS-08811 error of Oracle Application Server (OAS) and the Web Application Server (WAS). Thi serror indicates that a listaner cannot start, but the reasons can vary. SCOPE & APPLICATION ------------------- This is useful to any and all experiencing the OWS-08811 error and could benefit by an article that sorts the many reasons this error appears. This Note sorts the existing Notes by Platform and configuration errors Summary of the OWS-08811 Error ------------------------------ The OWS-08811 error is a generic error that can be Platform specific, combined with other errors and is related to many types configuration mistakes. This Note will group solutions by Platform and specific configuration areas. Platform Specific: 168 (Silicon Graphics UNIX) Ver 6.2 - NOTE.1064165.6 OWS-08811: TRYING TO START ADMIN LISTENER ON WEB SERVER ... -- WAS 3.0.2 NOT SUPPORTED ON SGI CHALLENGE S 358 (NCR Unix SVR4) NCR 3.0.1 - NOTE.1064165.6 OWS-08811: TRYING TO START ADMIN LISTENER ON WEB SERVER ... -- A NCR OS patches or an upgrade from NCR 3.0.1 to NCR 3.0.2 is necessary 17 (HP Non-CPU Specific UX UNIX ) HP-UX 11.0 - NOTE.1059038.6 OWS-08811: ERROR UNABLE TO START ADMIN LISTENER -- Applying the 8.0.x inter-operability patch fails 453 (Sun SPARC Solaris) - NOTE.1058606.6 OWS-08811: AFTER PATCH 644535 -> OWSCTL START ADMIN ->OWS -- A Solaris OS patch is needed for Patch 644535 to function correctly. Configuration Specific: - General - NOTE.112661.1 "OWS-08811: when starting newly created listeners" -- This Note lists many general configuration parameters to check, which can cause this error. - Port Related - NOTE.1061925.6 OWS-08811: CAN'T START LISTENER - PORT IN USE -- "PORT IN USE" error in addition to OWS-08811. The cause is plain to see here. NOTE.1032974.6 OWS-08811 & OWS-05721: CANNOT START WEB LISTENER ON PORT BELOW.. -- Enviroment, permissions and procedures all involved to propery start on Port number below 1024 - Configuration File Related - NOTE.1011690.102 OWS-08811: 'TERMINATOR NOT ENDED PROPERLY' STARTING ADMIN -- Virtual Mappings section of the svadmin.cfg file requires a trailing slash for correct syntax NOTE.1082803.6 OWS-8811: Error after making changes to an http listener -- sv.cfg requires the word "any" to entered in UPPER case letters. NOTE.112395.1 OWS-08811: WHEN starting new listener -- Network section of the sv.cfg has a duplicate entry NOTE.1081526.6 OWS-08811: APPLICATION INIT FUCTION ORACLE_ADP_INIT -- Steps used to start over when it is unknown which change to configuration caused error RELATED DOCUMENTS ----------------- Oracle ?? Application Server Administration Guide Release 4.0.8.2 June 2000 Part No. A60172-05

Re: Oracle Web Listener

Steven E. Protter — Tue, 14 Jan 2003 20:55:07 GMT

okay, I was probably wrong about apache. It was first used for Internet Applicataion Server 1.0

Have you applied any patches recently. The oracle forums show at least three users having this error after applying oracle patches.

Steve