Error: "10022 unknown error: make_secure_socket" loading Apache

(Last modified: 19Nov2004)

This document (10092828) is provided subject to the disclaimer at the end of this document.

fact

Novell NetWare 6.5

Novell NetWare 6.0

Novell iManager 1.5

Novell GroupWise WebAccess

symptom

Error: "10022 unknown error: make_secure_socket" loading Apache

Web services products (iPrint, etc) not functioning correctly

SSL authentication is not working

Cannot access iManager login page

Cannot access GroupWise Webaccess

cause

A copy of NILE.NLM exists in the SYS:SYSTEM directory and is being loaded instead of the NILE.NLM in C:\NWSERVER. This is an incorrect version.

fix

If NILE.NLM exists in SYS:SYSTEM, rename it to NILE.OLD and reboot the server. If the file does not exist in SYS:SYSTEM, try the next fix listed below.

Unload Apache 1.3 - use the command "nvxadmdn" on the Console Screen you will see the following:

Unloading module Apache from address space OS

Module APACHE.NLM unloaded

Module MDLIB is not loaded

Unload Tomcat33 (if you are using Tomcat 4 see below) - use command "tomcat33 -stop" on the Logger Screen you will see the following:

Stopping Tomcat

Stopping Tomcat on 127.0.0.1:9007 null

Stop Reaper

SUPER org.apache.tomcat.util.qlog.LogDaemon@xxxxxxx Exiting

ContextManager: Exiting

Java: Class org.apache.tomcat.startup.Main exited successfully

Unload Tomcat 4 (if you are using this instead of Tomcat33) - use the command "tc4stop" on the Logger Screen you will see the following:

Doing a stop Stopping service Tomcat-Standalone

java: Class org.apache.catalina.startup.Bootstrap exited successfully

NEXT - Download and install the PKIDIAG.NLM from the www.support.novell.com/filefinder website, the run the PKIDIAG.NLM at the server console, log in as ADMIN. Now in order to run the utility in fix mode type in the numbers 4, 5, 6, then 0 to verify the configuration of these objects. This will give you summary of the problems found/fixed, and should resolve all errors on the first pass.

Note: PKIDIAG writes to the log file SYS:\ETC\Certserv\REPAIR.LOG You may check this log file for any unresolved errors.

Re-load Apache 1.3 - use the command "nvxadmup" on the Logger Screen you will see the following:

Apache/1.3.27 (NETWARE) mod_jk/1.2.2-dev running...

Listening on port(s) :2200 443 80 2211

Re-load Tomcat33 - use command "tomcat33" on the console screen you will see the following:

Loading Module JAVA.NLM

Type JAVA -SHOW and you should see - "org.apache.startup.Main xxx"

Re-load Tomcat 4 (if using it instead) - use the command "tcadmup" on the Logger Screen you will see:

Doing a start

(INFO messages)

Starting service Tomcat-Standalone

Apache Tomcat/4.1.18 (wait for a few minutes then you will see)

INFO:JK2:ajp13 listening on /0.0.0.0:9010

<date> <time> org.apche.jk.server.JkMain start

INFO Jk running ID=0 time=17/709 config=sys:\tomcat\4\conf\jk2.properties

Type JAVA -SHOW and you should see - "org.apache.startup.Main xxx"

Now try accessing iManager or another web services page, and you should be able to access them. If this does not resolve the issue, you can turn to the online doucmentation or call into Novell Technical Support for additional help.

document

Document Title:	Error: "10022 unknown error: make_secure_socket" loading Apache
Document ID:	10092828
Solution ID:	NOVL96932
Creation Date:	12May2004
Modified Date:	19Nov2004
Novell Product Class:	novell directory services

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.