Web Services Security Guides › CA SiteMinder® Web Services Security Agent Guide for Apache-based Web Servers › Troubleshooting

Troubleshooting

This section contains the following topics:

Apache Server Shows shmget Failure On Startup

Apache Agent is Enabled but Default Server Page or Protected Resource Not Accessible

Apache Web Agent Not Operating

Incorrect Error Code Returned Returned on XML-DCC Authentication Failure

Apache Server Shows shmget Failure On Startup

Symptom:

When starting the web server, you see: shmget failed.

You may be trying to make a cache that is too large or be doing apachectl restart.

Solution:

Make the recommended adjustments to the shared memory segments.

Apache Agent is Enabled but Default Server Page or Protected Resource Not Accessible

Symptom:

The default web server page or the protected resource is not accessible after enabling Web Agent.

Solution:

Make the recommended adjustments to the shared memory segments.

Apache Web Agent Not Operating

Symptom:

The Apache Web Agent is not operating.

Solution:

Tune the Apache operating system shared memory.

Incorrect Error Code Returned Returned on XML-DCC Authentication Failure

Valid on Oracle Directory Enterprise Edition (formerly Oracle iPlanet Directory Server Enterprise Edition)

Symptom:

Authentication against the XML Document Credential Collector authentication scheme fails, but the web server returns a 500 Internal Server Error instead of a 403 Forbidden error.

Solution:

Perform the following steps:

1. Open the obj.conf file on your web server.
2. Locate the following line:

   AuthTrans fn="SiteMinderAgent"
   

3. Add UseOutputStreamSize="0"to the end of the previous line, as shown in the following example:

   AuthTrans fn="SiteMinderAgent" UseOutputStreamSize="0"
   

4. Save the file, and then restart the web server.