Symantec Access Management

 View Only
Expand all | Collapse all

Apache Error Log

  • 1.  Apache Error Log

    Posted Apr 12, 2017 02:11 PM

    Hi All,

     

    We are getting a warning message in one of the apache error logs:

    [12/Apr/2017:19:23:14] [Warning] SiteMinder Agent
            Session cache failed to initialize.
            Failed to fetch SmCacheData object from existing shared segment.
    [12/Apr/2017:19:23:14] [Warning] SiteMinder Agent
            Session cache failed to initialize.
            Unable to initialize shared memory segment.
    [12/Apr/2017:19:23:14] [Warning] SiteMinder Agent
            Session cache failed to initialize.
            Failed to attach to the authorization cache. Please verify that the LLAWP process is running.

     

    What's the reason for this message as this is occurring in logs too much frequently.

     

    Regards,

    Shrawan



  • 2.  Re: Apache Error Log

    Posted Apr 13, 2017 12:45 AM

    That generally meant that there was no space left on the shared memory segments to create cache objects.

     

    If you install an Apache-based agent on Solaris systems, tune the shared memory settings of the operating environment for the Agent to function correctly. By increasing the shared memory segments or your operating environment, you improve the performance of the Agent. The variables that control shared memory segments are defined in the specification file of your operating environment.

     

    Operating System Tuning for Agents - CA Single Sign-On - 12.6.01 - CA Technologies Documentation 



  • 3.  Re: Apache Error Log

    Posted Apr 13, 2017 02:44 AM

    Hi Wonsa03,

     

    We are using Apache based agent on RHEL 6. Is there any article or solution regarding this?



  • 4.  Re: Apache Error Log

    Posted Apr 13, 2017 05:11 AM

    Shut down the web server
    Make sure the LLAWP process is shut down
    Check for shared memory and semaphores leftover from the web server using these commands:

    ipcs -s : list semaphores
    ipcs -m : list shared memory
    ipcrm -s : remove semaphores
    ipcrm -m : remove shared memory

    Then remove any shared memory or semaphores for this instance. Look in the Web Server error log for the semaphore and shared memory keys. Those are the ones which need to be removed.
    Start the web server and check how it works.

     
    Thanks
    Siva



  • 5.  Re: Apache Error Log

    Posted Apr 13, 2017 05:38 AM

    Hi Siva,

     

    We have already tried this thing but we are getting this error too much frequently in Apache error logs.

     

    So is there any configuration on server that will resolve this permanently?

     

    Regards,

    Shrawan



  • 6.  Re: Apache Error Log

    Posted Apr 13, 2017 08:19 AM

    Hello Shrawan,

     

    Did you try to change the values of session/resource cache size?

    If not try this:

     

    - Check if the system has enough memory to handle the resource and session caches.

    1. If you have increased the session/resource cache size, then change them to default.
       
    2. If you are using the default values, then decrease to 0.
       
    3. Then restart the Web Server.

      Session and resource cache size parameters are:
      • MaxSessionCacheSize
         
      • MaxResourceCacheSize

    The idea behind decreasing those values to 0 is to check whether your system has enough memory or not. There might be a loss of performance while those values are at 0, because there will be no caching. However if this issue disappears, then it means that you should add some memory to the system, or reduce the cache size to a lower level if adding memory isn't possible.

     

    Best Regards,

    Ashish Sharma



  • 7.  Re: Apache Error Log

    Posted Apr 13, 2017 08:22 AM

    Also, just curious to know:

     

    - As these look to be warning messages, do you see any functional impact too on the Webagent?

    - And what are the Webagent logs saying?

     

    Best Regards,
    Ashish Sharma



  • 8.  Re: Apache Error Log

    Posted Apr 17, 2017 01:30 AM

    Hi Ashish,

     

    Yes there was functional impact of these. As, after sometime these warning messages convert into Error messages and that stops the WebAgent Process.

     

    Regards,

     

    Shrawan



  • 9.  Re: Apache Error Log

    Posted Apr 17, 2017 05:14 AM

    Hello Shrawan,

     

    Did you try to change the values of session/resource cache size as per my previous comment?

    And what are the Webagent logs saying at the time of warning messages in error logs?

     

    Best regards,
    Ashish Sharma



  • 10.  Re: Apache Error Log

    Posted Apr 17, 2017 05:20 AM

    Hi Ashish,

     

    I haven't checked those changes as these Messages are coming on Production server of one of the application and we are unable to replicate this issue in development.

     

    Regards,

    Shrawan



  • 11.  Re: Apache Error Log

    Posted Apr 17, 2017 05:35 AM

    Yeah understood..

     

    Do you have Webagent logs enabled? and are you receiving any error/warning messages in these logs too at the same time?

    Also, what are the Webagent details:

     

    Web Agent complete version: ?
    Web Server complete version and Bit level details (32 or 64): ?
    Web Server complete O/S and Bit level details (32 or 64): ?

     

    May be you can try to check the latest version release notes, if there is a known issue like that.

     

    Hope this helps!

     

    Best Regards,
    Ashish Sharma



  • 12.  Re: Apache Error Log

    Posted Apr 17, 2017 06:30 AM

    Hi Ashish,

     

    Yes we do have WebAgent Logs enabled but there's neither an Error message nor a Warning Message in Logs.

     

    Please find WebAgent Details below:

     

    WebAgent Version: 12.0.310.624

    Webserver Complete version:- Apache/2.2.22 (Unix)

    Webserver Complete OS version: Red Hat Enterprise Linux Server release 6.8 (Santiago).

     

    I have checked all CA docs and community posts but din't find any solution for this issue.

     

    Regards,

    Shrawan



  • 13.  Re: Apache Error Log

    Posted Apr 17, 2017 07:24 AM

    Hi Shrawan,

     

    How many apache instances are running on the box? Are they using same ServerPath?

     

    If you configure a Web Agent on multiple web server instances, each server instance requires its own Web Agent cache, log file, and health monitoring resources. To verify that resources are unique, ServerPath should be unique.
    The Web Agent tracks shared memory using a semaphore. A semaphore is a value in operating system (or kernel) storage. Process running on the system examine this value to verify resource availability. Because the semaphore is not unique, multiple Agents would try to point to the same area of memory. Naming a server path gives the root of an instance, and the Agent finds the files that are used for creating unique keys for semaphores.
    To configure a Web Agent on multiple server instances, add a unique path to the ServerPath parameter in each WebAgent.conf file.

     

    if you are using multiple apache instances and same ServerPath for the the instance then it could cause memory issues.

     

    Thanks,

    Sharan



  • 14.  Re: Apache Error Log

    Posted Apr 17, 2017 08:11 AM

    Hi Sharan,

     

    There's only one instance on that server.

     

    Regards,

    Shrawan



  • 15.  Re: Apache Error Log

    Posted Apr 18, 2017 04:31 AM

    Hi Shrawan,

     

    How many web servers are running on the production env?

    All the agents are getting the same issue in prod? 

    Is the load same across all the agents?

    Did you compare the semaphore settings across all the envs?

     

    If you are not able do the changes on production. You could try to replicate the issue in lower env with the load testing ( match the load with your production). Once you are able to replicate, please try below option to find whether your system has enough memory or not.

     

    Set Session and resource cache size parameters to 0:
    MaxSessionCacheSize
    MaxResourceCacheSize

    The idea behind decreasing those values to 0 is to check whether your system has enough memory or not. There might be a loss of performance while those values are at 0, because there will be no caching. However if this issue disappears, then it means that you should add some memory to the system, or reduce the cache size to a lower level if adding memory isn't possible

     

    Thanks,

    Sharan



  • 16.  Re: Apache Error Log

    Posted Apr 19, 2017 06:54 AM

    Hi Sharana,

    I will check this out.

     

    Regards,

    Shrawan