505 lines
28 KiB
HTML
505 lines
28 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
<!DOCTYPE html
|
||
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow" />
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<meta name="DC.Type" content="topic" />
|
||
|
<meta name="DC.Title" content="Troubleshoot" />
|
||
|
<meta name="abstract" content="This topic lists common problems and solutions for the HTTP Server, the IBM Web Administration for i5/OS interface, and other features associated with the product." />
|
||
|
<meta name="description" content="This topic lists common problems and solutions for the HTTP Server, the IBM Web Administration for i5/OS interface, and other features associated with the product." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiemain.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2002,2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002,2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rzaietrouble" />
|
||
|
<meta name="DC.Language" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>Troubleshoot</title>
|
||
|
</head>
|
||
|
<body id="rzaietrouble"><a name="rzaietrouble"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Troubleshoot</h1>
|
||
|
<div><p>This topic lists common problems and solutions for the HTTP Server,
|
||
|
the <span>IBM<sup>®</sup> Web Administration for i5/OS™ interface</span>, and other features
|
||
|
associated with the product.</p>
|
||
|
<div class="important"><span class="importanttitle">Important:</span> Information
|
||
|
for this topic supports the latest PTF levels for HTTP Server for i5/OS .
|
||
|
It is recommended that you install the latest PTFs to upgrade to the latest
|
||
|
level of the HTTP Server for i5/OS. Some of the topics documented here are
|
||
|
not available prior to this update. See <a href="http://www-03.ibm.com/servers/eserver/iseries/software/http/services/service.html" target="_blank">http://www.ibm.com/servers/eserver/iseries/software/http/services/service.htm</a> <img src="www.gif" alt="Link outside Information Center" /> for more information. </div>
|
||
|
<p><strong>List of symptoms</strong>:</p>
|
||
|
<ul><li><a href="#out">Symptom: Out-of-process ASF Tomcat server does not start or appears to start, but then stops</a> </li>
|
||
|
<li><a href="#error404">Symptom: Error 404 on HTTP Server</a> </li>
|
||
|
<li><a href="#slow">Symptom: HTTP Server has a slow response</a> </li>
|
||
|
<li><a href="#error500">Symptom: Error 500 on HTTP Server</a> </li>
|
||
|
<li><a href="#read">Symptom: Cannot read or write to QUSRSYS/QATMHINSTC or QUSRSYS/QATMHASFT</a> </li>
|
||
|
<li><a href="#start">Symptom: HTTP Server on port 80 does not start</a> </li>
|
||
|
<li><a href="#browser">Symptom: Web browser problems with HTTP Server</a> </li>
|
||
|
<li><a href="#admin">Symptom: ADMIN server will not start</a> </li>
|
||
|
<li><a href="#serverinstancenostart">Symptom: HTTP Server will not start or functions will not work</a></li>
|
||
|
<li><a href="#unknown_stype">Symptom: Unknown server type when working with HTTP Servers in ADMIN</a></li>
|
||
|
<li><a href="#all_stopped">Symptom: All servers show status 'Stopped'</a></li>
|
||
|
<li><a href="#no_access">Symptom: Cannot access ADMIN or some functions do not work</a></li>
|
||
|
<li><a href="#no_iosyscfg">Symptom: User Profile does not have *IOSYSCFG</a></li>
|
||
|
<li><a href="#no_tomcat">Symptom: Tomcat options not shown in the IBM Web Administration for i5/OS interface</a></li>
|
||
|
<li><a href="#create_instance">Symptom: Cannot create new HTTP Server instance</a></li>
|
||
|
<li><a href="#netdata_error">Symptom: Net.Data error</a></li>
|
||
|
<li><a href="#cantopenfile">Symptom: Error occurred opening file</a></li>
|
||
|
<li><a href="#wpwizdb">Symptom: Databases fail to deploy when configuring with the IBM Web Administration for i5/OS interface</a></li>
|
||
|
<li><a href="#portalperf">Symptom: WebSphere Portal authentication performance problems</a></li>
|
||
|
</ul>
|
||
|
<div class="note"><span class="notetitle">Note:</span> Additional troubleshooting information may be found in the following
|
||
|
documentation: <ul><li><a href="http://www.ibm.com/websphere/portal/library/" target="_blank">WebSphere<sup>®</sup> Portal Product Documentation</a> <img src="www.gif" alt="Link outside Information Center" /> Web site</li>
|
||
|
<li><a href="../rzahg/rzahgebappserv.htm" target="_blank">WebSphere
|
||
|
Application Server</a> topic</li>
|
||
|
<li><a href="../rzamy/50/express.htm" target="_blank">WebSphere
|
||
|
Application Server - Express</a> topic</li>
|
||
|
<li><a href="../rzahg/rzahgebusapp.htm" target="_blank">Business
|
||
|
Applications</a> topic</li>
|
||
|
</ul>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiemain.htm">IBM HTTP Server for i5/OS</a></div>
|
||
|
</div>
|
||
|
</div><div class="hr" id="out"><a name="out"><!-- --></a><h2 class="topictitle2">Symptom: Out-of-process ASF Tomcat server does not start or appears
|
||
|
to start, but then stops</h2>
|
||
|
<div><dl><dt class="dlterm">Cause </dt>
|
||
|
<dd>A number of possible causes could be causing your out-of-process ASF Tomcat
|
||
|
to not start. Check the job log for the cause. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>Check the job log for a report on the possible problem and enable tracing. <p><strong>Check
|
||
|
the job log</strong>: </p>
|
||
|
<ol><li>On an iSeries™ command
|
||
|
line, enter <strong><tt>WRKACTJOB</tt></strong> immediately after the server is started. <p>If
|
||
|
the job is active, enter <strong><tt>WRKACTJOB</tt></strong> to work with the job and
|
||
|
display the job log.</p>
|
||
|
<p>If the job is not active, enter <strong><tt>WRKSPLF
|
||
|
SELECT(QTMHHTTP)</tt></strong> to find the name of the server and display the spool
|
||
|
file.</p>
|
||
|
</li>
|
||
|
<li>Check the ASF Tomcat logs. Inspect the tomcat.log, jvmstdout.txt, and
|
||
|
jvmstderr.txt files for possible information concerning the error. </li>
|
||
|
</ol>
|
||
|
<p><strong>Enable/disable tracing</strong>: </p>
|
||
|
<ol><li>On an iSeries command line, enter <strong><tt>ADDENVVAR ENVVAR(QIBM_ASFTOMCAT_TRACE)
|
||
|
VALUE(10) LEVEL(*SYS)</tt></strong>. </li>
|
||
|
<li>Restart the ADMIN server. </li>
|
||
|
<li>Start the out-of-process ASF Tomcat server. </li>
|
||
|
<li>Additional debug information is created for the job. If this information
|
||
|
does not appear in a spool file associated with the started job, then it may
|
||
|
be accessed using the Dump User Trace (<tt>DMPUSRTRC</tt>) command against
|
||
|
the ADMIN server and the out-of-process ASF Tomcat server jobs.<p>To disable
|
||
|
tracing, continue with the next steps.</p>
|
||
|
</li>
|
||
|
<li>On an iSeries command line, enter <tt><strong>RMVENVVAR ENVVAR(QIBM_ASFTOMCAT_TRACE)</strong></tt>.
|
||
|
</li>
|
||
|
<li>Restart the ADMIN server. </li>
|
||
|
<li>Start the out-of-process ASF Tomcat server. </li>
|
||
|
</ol>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="error404"><a name="error404"><!-- --></a><h2 class="topictitle2">Symptom: Error 404 on HTTP Server</h2>
|
||
|
<div><dl><dt class="dlterm">Cause </dt>
|
||
|
<dd>HTTP Server is not able to find the resource that was requested or the
|
||
|
user profile on HTTP Server does not have authority to the requested resource. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>Check the following:<ul><li>Make sure the file exists. </li>
|
||
|
<li>Make sure that the user profile used to access the resource has object
|
||
|
authority. The user profile QTMHHTTP is used by default. The user profile
|
||
|
QTMHHTP1 is used by default when the request is a CGI program. </li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="slow"><a name="slow"><!-- --></a><h2 class="topictitle2">Symptom: HTTP Server has a slow response</h2>
|
||
|
<div><dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>Refer to the following: <ul><li><a href="rzaiemngperf.htm">Manage server performance for HTTP Server (powered by Apache)</a> </li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="error500"><a name="error500"><!-- --></a><h2 class="topictitle2">Symptom: Error 500 on HTTP Server</h2>
|
||
|
<div><dl><dt class="dlterm">Cause </dt>
|
||
|
<dd>A program on your HTTP Server has failed or there is an error in your
|
||
|
CGI program. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>Check the following: <ul><li>Check the server Primary joblog, QSYSOPR messeges, error log and CGI job
|
||
|
logs for more information.</li>
|
||
|
<li>If you have not used the <span>IBM Web Administration for i5/OS interface</span> to
|
||
|
create an HTTP Server configuration, a required directive may be missing from
|
||
|
the configuration file. View the configuration file with the <span>IBM Web Administration for i5/OS interface</span> for
|
||
|
possible errors. </li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="read"><a name="read"><!-- --></a><h2 class="topictitle2">Symptom: Cannot read or write to QUSRSYS/QATMHINSTC or QUSRSYS/QATMHASFT</h2>
|
||
|
<div><dl><dt class="dlterm">Cause </dt>
|
||
|
<dd>The <span>IBM Web Administration for i5/OS interface</span> uses the Java™ Toolbox
|
||
|
for iSeries. When reading and writing files in QSYS, the Java Toolbox sometimes
|
||
|
uses the DDM server. In the <span>IBM Web Administration for i5/OS interface</span>,
|
||
|
this results in problems reading or writing the QUSRSYS/QATMHINSTC file containing
|
||
|
HTTP Server definitions, or QUSRSYS/QATMHASFT file containing out-of-process
|
||
|
ASF Tomcat server definitions. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>On an iSeries command line, enter STRTCPSVR *DDM. </dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="start"><a name="start"><!-- --></a><h2 class="topictitle2">Symptom: HTTP Server on port 80 does not start</h2>
|
||
|
<div><dl><dt class="dlterm">Cause </dt>
|
||
|
<dd>By default, APACHEDFT server autostart setting is *GLOBAL. If, in addition,
|
||
|
the global server setting for autostart is "Yes", then APACHEDFT server will
|
||
|
start during STRTCP command processing. APACHEDFT server uses port 80 and
|
||
|
may cause any other HTTP Server using port 80 to not start. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>Do the following: <p>If you HTTP Server does not start or appears to start,
|
||
|
but then stops, check the following: </p>
|
||
|
<ol><li>The cause of the problem may be in the job log. Use WRKACTJOB immediately
|
||
|
after the server is started. If the job is active, the enter <strong><tt>WRKACTJOB</tt></strong> to
|
||
|
work with job and display the job log. If the job is not active, then enter <tt><strong>WRKSPLF
|
||
|
SELECT(QTMHHTTP)</strong></tt> to find the name of the server and display the spool
|
||
|
file. </li>
|
||
|
<li>If you have configured the error logs, then the cause of the problem may
|
||
|
be in the error log. For example, <tt>/www/myserver/logs/basic_error_log</tt>,
|
||
|
where "<tt>myserver</tt>" is the name of your HTTP Server. <div class="note"><span class="notetitle">Note:</span> If the error
|
||
|
messages have been customized, the error will not be identified in the same
|
||
|
manner as the above example. </div>
|
||
|
</li>
|
||
|
<li>If you have configured ASF Tomcat, then there may be error information
|
||
|
logged in the ASF Tomcat logs. Inspect the tomcat.log, jvmstdout.txt, and
|
||
|
jvmstderr.txt for possible information concerning the error</li>
|
||
|
</ol>
|
||
|
<p>If these steps do not help, then try starting the server with verbose
|
||
|
tracing. See Manage server performance for HTTP Server (powered by Apache)
|
||
|
for tracing. </p>
|
||
|
<p>By default, APACHEDFT server autostart setting is *GLOBAL.
|
||
|
If, in addition, the global server setting for autostart is "Yes", then APACHEDFT
|
||
|
will start during STRTCP command processing. APACHEDFT server uses port 80
|
||
|
and may cause any other HTTP Server using port 80 to not start. To avoid this
|
||
|
condition, you can : </p>
|
||
|
<ul><li>Change APACHEDFT server configuration autostart setting to "No". </li>
|
||
|
<li>Change APACHEDFT server configuration to use a port other than 80. </li>
|
||
|
</ul>
|
||
|
<p>To change the autostart value on APACHEDFT server, do the following:
|
||
|
</p>
|
||
|
<ol><li>Click the <strong>Manage</strong> tab. </li>
|
||
|
<li>Click the <span class="uicontrol">HTTP Servers</span> subtab.</li>
|
||
|
<li>Select <strong>APACHEDFT</strong> from the <strong>Server</strong> list. </li>
|
||
|
<li>Expand <strong>Server Properties</strong>. </li>
|
||
|
<li>Click <strong>General Server Configuration</strong>. </li>
|
||
|
<li>Click the <strong>General Settings</strong> tab in the form. </li>
|
||
|
<li>Select <strong>No</strong> (instead of *GLOBAL or Yes) from the <strong>Autostart</strong> list.
|
||
|
</li>
|
||
|
<li>Click <strong>OK</strong>. </li>
|
||
|
</ol>
|
||
|
<p>To change the port number on APACHEDFT server, do the following: </p>
|
||
|
<ol><li>Click the <strong>Manage</strong> tab. </li>
|
||
|
<li>Click the <span class="uicontrol">HTTP Servers</span> subtab.</li>
|
||
|
<li>Select <strong>APACHEDFT</strong> from the <strong>Server</strong> list. </li>
|
||
|
<li>Expand <strong>Server Properties</strong>. </li>
|
||
|
<li>Click <strong>General Server Configuration</strong>. </li>
|
||
|
<li>Click the <strong>General Settings</strong> tab in the form. </li>
|
||
|
<li>Select the IP address and port from the <strong>Server IP addresses and ports
|
||
|
to listen on</strong> table. </li>
|
||
|
<li>Enter a new value for the port number in the <strong>Port</strong> column. </li>
|
||
|
<li>Click <strong>Continue</strong>. </li>
|
||
|
<li>Click <strong>OK</strong>. </li>
|
||
|
</ol>
|
||
|
<p>As a final precaution, make sure APACHEDFT server is not started by
|
||
|
doing the following: </p>
|
||
|
<ol><li>Click the <strong>Manage</strong> tab. </li>
|
||
|
<li>Click the <span class="uicontrol">All Servers</span> subtab.</li>
|
||
|
<li>Click the <span class="uicontrol">All HTTP Servers</span> tab.</li>
|
||
|
<li>Select <strong>APACHEDFT</strong> from the table. </li>
|
||
|
<li>Click <strong>Stop</strong>. </li>
|
||
|
</ol>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="browser"><a name="browser"><!-- --></a><h2 class="topictitle2">Symptom: Web browser problems with HTTP Server</h2>
|
||
|
<div><dl><dt class="dlterm">Cause </dt>
|
||
|
<dd>Your Web browser may not be configured correctly. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>Below is a list of common problems and solutions for your Web browser. <dl><dt class="dlterm">Miscellaneous Microsoft<sup>®</sup> Internet Explorer errors related to incorrect
|
||
|
interpretation of HTTP/1.1 in response</dt>
|
||
|
<dd>Microsoft Internet Explorer sends requests in HTTP/1.1 format but seems
|
||
|
to only accept responses in HTTP/1.0 format. The work around is to tell HTTP
|
||
|
Server the request came in as HTTP/1.0 format.<p>Fore example: <tt>BrowserMatch
|
||
|
"MSI 4\.0b2;" downgrade-1.0 force-response-1.0 </tt></p>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">URL not found when clicking on a file in a directory listing from Netscape</dt>
|
||
|
<dd>If <tt>AlwaysDirectoryIndex</tt> is set to OFF and a URL for a directory
|
||
|
without a trailing slash is requested, then Netscape does not request the
|
||
|
file relative to the director in which the file exists in the resulting directory
|
||
|
listing. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Microsoft Internet Explorer does not display customized error messages</dt>
|
||
|
<dd>If Internet Explorer is not displaying the customized error messages,
|
||
|
check to see if the preferences for the browser are set to show friendly HTTP
|
||
|
error messages. Disable this preference and the customized error massages
|
||
|
should display properly. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">When using HTTPS, Microsoft Internet Explorer shows pages that were cached
|
||
|
when using HTTP</dt>
|
||
|
<dd>If the browser is showing cached pages instead of connecting to the server
|
||
|
using SSL, clear the browser's cache. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Prompted for password when using certificate for client authentication</dt>
|
||
|
<dd>If you are using a Certificate Authority that offers the option to protect
|
||
|
the private key of your certificate with a password (such as for the Microsoft
|
||
|
Internet Explorer browser), and you use the certificate for client authentication,
|
||
|
you are prompted for the password after about 2 minutes of idle time. This
|
||
|
happens even if you have disabled SSLV2 in the browser being used and in the
|
||
|
server because you are trying to use the longer SSLV3 cache time-out interval.
|
||
|
This is a security feature that protects your private key if you are away
|
||
|
form your client, even though it may look like an SSLV3 caching problem. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Certificate not recognized by browser</dt>
|
||
|
<dd>If you add a certificate to your browser, the browser may not recognize
|
||
|
that there is a new certificate until you restart your computer. </dd>
|
||
|
</dl>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<p>For additional information see the Apache Software Foundations list of
|
||
|
list of <a href="http://www.apache.org/docs/misc/known_client_problems.html" target="_blank">known problems with clients</a> <img src="www.gif" alt="Link outside Information Center" />. </p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="admin"><a name="admin"><!-- --></a><h2 class="topictitle2">Symptom: ADMIN server will not start</h2>
|
||
|
<div><dl><dt class="dlterm">Solution </dt>
|
||
|
<dd>Check to make sure you have the proper authorities. See <a href="rzaiesetauth.htm">User profiles and required authorities for HTTP Server</a> for specific authority and profile information. </dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="serverinstancenostart"><a name="serverinstancenostart"><!-- --></a><h2 class="topictitle2">Symptom: HTTP Server will not start or functions will not work</h2>
|
||
|
<div><dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>General items to check:<ol><li>Check /QIBM/UserData/HTTPA/admin/logs, HTTPAdmin.log, error_log, and
|
||
|
any other logs you may have. More information on the cause of the problem
|
||
|
may be found there.</li>
|
||
|
<li>Use CHKPRDOPT to 57XXDG1, SS1, TC1 and JV1.</li>
|
||
|
<li>Check joblog for user QTMHHTTP.</li>
|
||
|
<li>Check QTMHHTTP and QTMHHTP1 user profiles.</li>
|
||
|
<li>Verify that *PUBLIC is not *EXCLUDEd from '/' (Use WRKLNK '/' and take
|
||
|
option 9).</li>
|
||
|
<li>Verify that QSERVER and QUSRWRK subsystems are running.</li>
|
||
|
</ol>
|
||
|
<p><strong>Error messages</strong>:</p>
|
||
|
<dl><dt class="dlterm">Error ZSRV_MSG0358</dt>
|
||
|
<dd>Found in admin log. Verify that there is a host table entry in CFGTCP
|
||
|
Option 10 that matches the host + domain name in CFGTCP Option 12, and set
|
||
|
'Host Name Search Priority' to *LOCAL.</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Error ZUI_50004 - 'no *IOSYSCFG authority'</dt>
|
||
|
<dd>Verify that user has *IOSYSCFG Authority. If *IOSYSCFG is granted by a
|
||
|
GROUP profile, verify that PTF SF65588 (V4R5) is applied. Check that there
|
||
|
are NO user .jar files in the /QIBM/ProdData directory path - this directory
|
||
|
is for IBM use
|
||
|
only.</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Error HTP8015</dt>
|
||
|
<dd>Verify that the latest PTFs for DG1 product are applied.</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Error CEE0200</dt>
|
||
|
<dd>Verify that 57XXJV1 Options *Base, 5, and 6 are installed, </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Error ZSRV_MSG0302 :User qsecofr:authentication failure for "/":1</dt>
|
||
|
<dd>Known problem with 128 character passwords on V5R1. HTTP servers cannot
|
||
|
use 128 character passwords. You may be able to circumvent this problem by
|
||
|
changing the password in the user profile to CAPITAL letters and using CAPITAL
|
||
|
letters to log into the ADMIN screen.</dd>
|
||
|
</dl>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="unknown_stype"><a name="unknown_stype"><!-- --></a><h2 class="topictitle2">Symptom: Unknown server type when working with HTTP Servers in ADMIN</h2>
|
||
|
<div><dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Ensure that LOOPBACK and LOCALHOST are configured to resolve to 127.0.0.1
|
||
|
and can be PINGed from the i5/OS™ command line. Verify that there are no exit
|
||
|
programs for exit point QIBM_QPWFS_FILE_SERV. Verify that QSERVER and QUSRWRK
|
||
|
subsystems are running and that current group PTF for DG1 product is applied.</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="all_stopped"><a name="all_stopped"><!-- --></a><h2 class="topictitle2">Symptom: All servers show status 'Stopped'</h2>
|
||
|
<div><dl><dt class="dlterm">Cause</dt>
|
||
|
<dd>This problem was determined to be caused by an OEM security application
|
||
|
that registers many exit point programs.</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Remove the application to eliminate the problem.</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="no_access"><a name="no_access"><!-- --></a><h2 class="topictitle2">Symptom: Cannot access ADMIN or some functions do not work</h2>
|
||
|
<div><dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Verify the following:<ul><li>Verify that user's browser is not using a proxy to access the ADMIN server.
|
||
|
</li>
|
||
|
<li>Verify latest DG1 PTF's. </li>
|
||
|
<li>Verify that user profiles QTMHHTTP and QTMHHTP1 are enabled.</li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="no_iosyscfg"><a name="no_iosyscfg"><!-- --></a><h2 class="topictitle2">Symptom: User Profile does not have *IOSYSCFG</h2>
|
||
|
<div><dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>In the HTTPAdmin.log you will find error: 'NoRouteToHostException'. Do
|
||
|
the following:<ul><li>Verify that 127.0.0.1, LOOPBACK and LOCALHOST are configured and work.
|
||
|
</li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="no_tomcat"><a name="no_tomcat"><!-- --></a><h2 class="topictitle2">Symptom: Tomcat options not shown in the <span>IBM Web Administration for i5/OS interface</span></h2>
|
||
|
<div><dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Do the following:<ul><li>Verify latest DG1 PTF's </li>
|
||
|
<li>Verify that AdminTc.jar is in: <tt>/QIBM/UserData/HTTPA/admin/webapps/HTTPAdmin/WEB-INF/lib</tt>.
|
||
|
This file can be found in /QIBM/ProdData/HTTPA/admin/pgm/. If so, the problem
|
||
|
can be circumvented by adding a SYMLNK. </li>
|
||
|
<li>On the i5/OS command line, type the following:<pre>ADDLNK OBJ('/QIBM/ProdData/HTTPA/admin/pgm/AdminTc.jar')+
|
||
|
NEWLNK('/QIBM/UserData/HTTPA/admin/webapps/httpadmin/web-inf/lib/AdminTc.jar')
|
||
|
Press Enter, then typethe following:
|
||
|
CHGOWN OBJ('/QIBM/USerData/HTTPA/admin/webapps/HTTPAdmin/WEB-INF/lib/AdminTc.jar')+
|
||
|
NEWOWN(QTMHHTTP) SYMLNK(*YES)</pre>
|
||
|
</li>
|
||
|
</ul>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="create_instance"><a name="create_instance"><!-- --></a><h2 class="topictitle2">Symptom: Cannot create new HTTP Server instance</h2>
|
||
|
<div><dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Verify LOCALHOST , LOOPBACK and 127.0.0.1 exist and work.</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="netdata_error"><a name="netdata_error"><!-- --></a><h2 class="topictitle2">Symptom: Net.Data<sup>®</sup> error</h2>
|
||
|
<div><p><strong>Include object specified in /QIBM/ProdData/HTTPSVR/MRIXXX/Macro/qzhamsg.nds
|
||
|
at line 208</strong></p>
|
||
|
<dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Verify that directory <tt>/QIBM/ProdData/HTTPSVR/Macro/</tt> contains
|
||
|
only objects that are appropriate to the current OS version . </dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" id="cantopenfile"><a name="cantopenfile"><!-- --></a><h2 class="topictitle2">Symptom: Error occurred opening file</h2>
|
||
|
<div><dl><dt class="dlterm">Cause</dt>
|
||
|
<dd>If your HTTP Server configuration uses the Rewrite directive and does
|
||
|
not have the proper access for QTMHHTTP configured, your server will not start. </dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Make sure QTMHHTTP has *RWX access authority to the <em>/tmp</em> directory.</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="hr" xml:lang="en-us" id="wpwizdb"><a name="wpwizdb"><!-- --></a><h2 class="topictitle2">Symptom: Databases fail to deploy when configuring with the <span>IBM Web Administration for i5/OS interface</span></h2>
|
||
|
<div><dl><dt class="dlterm">Cause</dt>
|
||
|
<dd>This error occurs when the user ID selected as the WebSphere Portal database
|
||
|
owner does not have authority to the CHGJOB command. The configuration wizard
|
||
|
requires this authority to autoreply when the system would otherwise require
|
||
|
a response from the user. Without this authority, the create-all-db configuration
|
||
|
task fails, and databases are not deployed.<p>If databases fail to deploy
|
||
|
when configuring WebSphere Portal with the <span>IBM Web Administration for i5/OS interface</span>,
|
||
|
check the <samp class="codeph">/QIBM/UserData/Webas5/Base/<instance>/logs/<instance>/WPSWIZARD_<timestamp>_create-all-db.log</samp> log
|
||
|
file for the following error: </p>
|
||
|
<pre>[java] java.lang.RuntimeException: error when creating statement [CPF0006]
|
||
|
Errors occurred in command.
|
||
|
[java] java/lang/Throwable.(Ljava/lang/String;)V+4 (Throwable.java:85)
|
||
|
[java] java/lang/Exception.(Ljava/lang/String;)V+1 (Exception.java:33) [java]
|
||
|
java/lang/RuntimeException.(Ljava/lang/String;)V+1 (RuntimeException.java:38)
|
||
|
[java] com/ibm/wps/config/SqlProcessor.process([Ljava/lang/String;Ljava/lang/
|
||
|
String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)I+0
|
||
|
(SqlProcessor.java:78)
|
||
|
[java] com/ibm/wps/config/SqlProcessor.main([Ljava/lang/String;)V+0
|
||
|
(SqlProcessor.java:478)</pre>
|
||
|
<p></p>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>Ensure the user ID selected as the WebSphere Portal database owner has
|
||
|
authority to the CHGJOB command.</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="portalperf"><a name="portalperf"><!-- --></a><h2 class="topictitle2">Symptom: WebSphere Portal authentication performance problems</h2>
|
||
|
<div><p>If you are experiencing performance problems when users are logging into
|
||
|
Portal (the authentication phase), the following indicators may help determine
|
||
|
that the filters are causing these performance problems:</p>
|
||
|
<ul><li>Your LDAP server is populated with a large number of entries. </li>
|
||
|
<li>When you type <kbd class="userinput">WRKACTJOB</kbd> in a console command line,
|
||
|
QSQSRVR jobs are using an excessive amount of CPU during the Portal authentication
|
||
|
(sign on) phase. </li>
|
||
|
<li>When two Portal users sign on concurrently, one sign on request takes
|
||
|
two times as long as the other request.</li>
|
||
|
</ul>
|
||
|
<dl><dt class="dlterm">Cause</dt>
|
||
|
<dd>You may encounter a performance problem if you configure a secure WebSphere
|
||
|
Portal server with LDAP. This problem only occurs if you use the <span class="uicontrol">Create
|
||
|
WebSphere Portal wizard</span> in the <span>IBM Web Administration for i5/OS interface</span>.
|
||
|
When configuring LDAP with the WebSphere Portal wizard, the two LDAP fields <span class="uicontrol">LDAPUserFilter</span> and <span class="uicontrol">LDAPGroupFilter</span> are configured with default values depending on the type of LDAP server
|
||
|
being used. For example, if you are securing your WebSphere Portal server
|
||
|
using the IBM Directory Server, the two LDAP fields are set to <var class="varname">"(&(|(cn=%v)(uid=%v))(objectclass=person))"</var> and <var class="varname">"(&(cn=%v)(|(objectclass=groupOfUniqueNames)(objectclass=groupOfNames)(objectclass=group)))"</var>, respectively. By configuring the fields with the default values, the WebSphere
|
||
|
Portal wizard allows the wpsadmin Portal administrator to successfully login
|
||
|
and existing LDAP entries can be used once the Portal server is successfully
|
||
|
configured and secured. However, if the LDAP server has a large number of
|
||
|
entries, or if many additional users are added to the LDAP server, Portal's
|
||
|
authentication performance may be noticeably impacted.</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">Solution</dt>
|
||
|
<dd>If you determine that the filters, as configured by the WebSphere Portal
|
||
|
wizard, are causing authentication performance problems, complete the following
|
||
|
steps:<ol><li>Start the <span>IBM Web Administration for i5/OS interface</span>.</li>
|
||
|
<li>Click the <span class="uicontrol">Manage</span> tab.</li>
|
||
|
<li>Click the <span class="uicontrol">Application Servers</span> subtab.</li>
|
||
|
<li>Expand <span class="uicontrol">Tools</span>.</li>
|
||
|
<li>Click <span class="uicontrol">Launch Administrative Console</span>.</li>
|
||
|
<li>Login to the console and click <span class="uicontrol">OK</span>.</li>
|
||
|
<li>Expand <span class="uicontrol">Security</span>.</li>
|
||
|
<li>Expand <span class="uicontrol">User Registries</span>.</li>
|
||
|
<li>Click <span class="uicontrol">LDAP</span>.</li>
|
||
|
<li>Click <span class="uicontrol">Advanced LDAP Settings</span> in the <span class="uicontrol">Additional
|
||
|
Properties</span> table.</li>
|
||
|
</ol>
|
||
|
<ol><li>Edit the <span class="uicontrol">User Filter</span> and the <span class="uicontrol">Group
|
||
|
Filter</span> properties values to more precise values to increase authentication
|
||
|
performance. For more information about this syntax, see the <a href="../rzahy/rzahyrzahywelpo.htm">LDAP directory service documentation</a> and
|
||
|
the <a href="http://www.ibm.com/websphere/portal/library/" target="_blank">WebSphere Portal Product Documentation</a> <img src="www.gif" alt="Link outside Information Center" /> Web site.</li>
|
||
|
<li>Click <span class="uicontrol">OK</span>.</li>
|
||
|
<li>Click <span class="uicontrol">Save</span> to apply changes to the master configuration.</li>
|
||
|
<li>Click <span class="uicontrol">Save</span> again on the next page.</li>
|
||
|
</ol>
|
||
|
<div class="note"><span class="notetitle">Note:</span> You may need to restart your WebSphere Application Server for these
|
||
|
changes to take affect.</div>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
|
||
|
</body>
|
||
|
</html>
|