Symantec Access Management

 View Only
  • 1.  Failed to Start the LLAWP process:LowLevelAgent.LLAWPExec.Failed (Permission denied)

    Posted Jun 20, 2015 09:29 AM

    I have installed 12.52 64bit AIX agent on IBM http server and configured to work with IHS8.5 http server. After configuring when we start the apachectl siteminder agent fails to start throwing the following error in http error logs. No entry in the siteminder webagent logs. We have checked all possible permissions but still the error continues. We need to fix this as we are unable to proceed ahead our prod environment.Any quick ideas and reolution will be appreciated.

    CSmLowLevelAgent: Permission denied

    cannot open file: /opt/ca/siteminder1252rcs/webagent/resources/AgentFramework_en.properties

    [20/Jun/2015:01:03:23] [Error] SiteMinder Agent

            Failed to Start the LLAWP process.

            LowLevelAgent.LLAWPExec.Failed (Permission denied)

     

     



  • 2.  Re: Failed to Start the LLAWP process:LowLevelAgent.LLAWPExec.Failed (Permission denied)

    Posted Jun 21, 2015 09:29 AM

    I guess user and group which you are using to start your webserver is not having permission over the webagent files, say SmHost.conf or in your case " /opt/ca/siteminder1252rcs/webagent/resources/AgentFramework_en.properties"

     

    For testing purpose, you can try below command and see if it helps.

    chmod 777 /opt/ca/siteminder1252rcs/webagent/resources/AgentFramework_en.properties



  • 3.  Re: Failed to Start the LLAWP process:LowLevelAgent.LLAWPExec.Failed (Permission denied)

    Posted Jun 21, 2015 12:09 PM

    Thanks Ankush

     

    I have already tried giving all the related config and log folders on the agent side as well as the conf side of IHS full permissions but that didnt help as well , infact we also unmounted and mounted both the AIX file systems to see if the underlying permissions for these directories was not an issue.

     

    Regards

    Ketan



  • 4.  Re: Failed to Start the LLAWP process:LowLevelAgent.LLAWPExec.Failed (Permission denied)

    Posted Jun 21, 2015 02:05 PM

    Hi Ketan,

     

    Do you observe any failure message in policy server logs at time stamp when error is seen in webagent.

     

    Thanks,

    Ankush



  • 5.  RE: Re: Failed to Start the LLAWP process:LowLevelAgent.LLAWPExec.Failed (Permission denied)

    Posted Dec 16, 2019 10:46 AM
    Hi Ankush raj, 

    I had a similar issue to start the LLAWP process:LowLevelAgent.LLAWPExec.Failed(Permission denied) I tried clearing all the semaphores and restarted the process it was working but " I need to know - what are the minimum permission required to the files and folder for the "apache" user to access read and write?? is there any limit for that?? ". Can you please let me know the details, Please find the below details of the siteminder errors that I came across - 

    [13/Dec/2019:13:58:26] [Info] [CA WebAgent IPC] [2949] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0xf49c894e

    [13/Dec/2019:13:58:26] [Error] [CA WebAgent IPC] [2949] [CSmIpcEvent::CSmIpcEvent] Error initializing semaphore -1

    [13/Dec/2019:13:58:26] [Error] [CA WebAgent IPC] [2949] [CSmSem::GetValue] Error performing GETVAL operation on semaphore -1 - Invalid argument (22)

    [13/Dec/2019:13:58:26] [Info] [CA WebAgent IPC] [2949] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0xf49c894e

    [13/Dec/2019:13:58:26] [Error] [CA WebAgent LLAWP] [2949] [Failed to send shutdown signal to the LLAWP. Ensure that the process is running and the path to the WebAgent.conf is correct.]

    [Fri Dec 13 13:58:36.445944 2019] [suexec:notice] [pid 2975] AH01232: suEXEC mechanism enabled (wrapper: /opt/rh/httpd24/root/usr/sbin/suexec)

    CSmLowLevelAgent: Permission denied

    cannot open file: /opt/app/siteminder/webagent/resources/AgentFramework_en.properties

    [13/Dec/2019:13:58:36] [Error] SiteMinder Agent

            Failed to Start the LLAWP process.

            LowLevelAgent.LLAWPExec.Failed (Invalid argument)

    nm: '/opt/rh/httpd24/root/etc/httpd/bin/httpd': No such file

    [Fri Dec 13 13:58:41.492926 2019] [sm:warn] [pid 2975] Siteminder Web Agent: restart not supported.

    [Fri Dec 13 13:58:41.494360 2019] [lbmethod_heartbeat:notice] [pid 2975] AH02282: No slotmem from mod_heartmonitor

    [Fri Dec 13 13:58:41.496740 2019] [mpm_prefork:notice] [pid 2975] AH00163: Apache/2.4.34 (Red Hat) OpenSSL/1.0.2k-fips configured -- resuming normal operations

    [Fri Dec 13 13:58:41.496770 2019] [core:notice] [pid 2975] AH00094: Command line: '/opt/rh/httpd24/root/usr/sbin/httpd -D FOREGROUND'

    [Fri Dec 13 14:00:18.462563 2019] [mpm_prefork:notice] [pid 2975] AH00170: caught SIGWINCH, shutting down gracefully

    [13/Dec/2019:14:00:19] [Info] [CA WebAgent IPC] [3261] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0xf49c894e

    [13/Dec/2019:14:00:19] [Error] [CA WebAgent IPC] [3261] [CSmIpcEvent::CSmIpcEvent] Error initializing semaphore -1

    [13/Dec/2019:14:00:19] [Error] [CA WebAgent IPC] [3261] [CSmSem::GetValue] Error performing GETVAL operation on semaphore -1 - Invalid argument (22)

    [13/Dec/2019:14:00:19] [Info] [CA WebAgent IPC] [3261] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0xf49c894e

    [13/Dec/2019:14:00:19] [Error] [CA WebAgent LLAWP] [3261] [Failed to send shutdown signal to the LLAWP. Ensure that the process is running and the path to the WebAgent.conf is correct.]

    [Fri Dec 13 14:00:31.945872 2019] [suexec:notice] [pid 3323] AH01232: suEXEC mechanism enabled (wrapper: /opt/rh/httpd24/root/usr/sbin/suexec)

    [13/Dec/2019:14:00:31] [Info] [CA WebAgent LLAWP] [3324] [LLAWP Monitor: LLAWP has been started.]

    [13/Dec/2019:14:00:31] [Warning] SiteMinder Agent

            Siteminder Web Agent not having write permissions on host configuration file. Shared secret roll-over may not be supported.

            Permission denied. Please assign write privileges to the user apache for the file /opt/app/siteminder/webagent/config/SmHost.conf

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x6b9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x6b9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4292612 using key 0x6b9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSharedSegment::smalloc] Created shared memory segment 0 using key 0x6c9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0xf49c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4325381 using key 0xf49c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x329c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4358150 using key 0x329c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x6a9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSharedSegment::smalloc] Created shared memory segment 32769 using key 0x619c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4390919 using key 0x6a9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSharedSegment::smalloc] Created shared memory segment 65538 using key 0x699c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x339c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4423688 using key 0x339c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSharedSegment::smalloc] Created shared memory segment 98307 using key 0x629c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x349c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4456457 using key 0x349c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSharedSegment::smalloc] Created shared memory segment 131076 using key 0x639c894e

    File open error.: Permission denied

    [13/Dec/2019:14:00:33] [Error] SiteMinder Agent

            Unable to open file.

            LLAWP failed to open log file '/siteminder/webagent/log/wa.log'.  Check disk space, permissions and configuration.

    File open error.: Permission denied

    [13/Dec/2019:14:00:33] [Error] SiteMinder Agent

            Unable to open file.

            LLAWP failed to open log file '/siteminder/webagent/log/wa_trace.log'.  Check disk space, permissions and configuration.

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x669c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4489226 using key 0x669c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x679c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4521995 using key 0x679c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x6c9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4554764 using key 0x6c9c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSharedSegment::smalloc] Created shared memory segment 163845 using key 0x659c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x689c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4587533 using key 0x689c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Attempted to attach to non-existent semaphore with key 0x699c894e

    [13/Dec/2019:14:00:33] [Info] [CA WebAgent IPC] [3325] [CSmSem::getSem] Created semaphore 4620302 using key 0x699c894e

    nm: '/opt/rh/httpd24/root/etc/httpd/bin/httpd': No such file

    [Fri Dec 13 14:00:36.995341 2019] [sm:warn] [pid 3323] Siteminder Web Agent: restart not supported.

    [Fri Dec 13 14:00:36.996695 2019] [lbmethod_heartbeat:notice] [pid 3323] AH02282: No slotmem from mod_heartmonitor

    [Fri Dec 13 14:00:36.999034 2019] [mpm_prefork:notice] [pid 3323] AH00163: Apache/2.4.34 (Red Hat) OpenSSL/1.0.2k-fips configured -- resuming normal operations

    [Fri Dec 13 14:00:36.999059 2019] [core:notice] [pid 3323] AH00094: Command line: '/opt/rh/httpd24/root/usr/sbin/httpd -D FOREGROUND'




  • 6.  Re: Failed to Start the LLAWP process:LowLevelAgent.LLAWPExec.Failed (Permission denied)

    Posted Jun 22, 2015 03:02 AM

    Hi

     

    Well the Error will not be in the policy server logs because LLAWP itself is not coming up.  hence the communication is not yet established with the Policy Server.

    Can you please enable Agent trace logs added with the "AgentFunc" component and see what is happening in the agent TLI layer ?

    you have already mentioned that LLAWP has all the permissions on each resources, please clean up all the semaphores and shared memory segments if the LLAWP has acquired any. Post the trace logs if possible to diagnose the problem further.

     

    Best

    Sandeep Khurana



  • 7.  Re: Failed to Start the LLAWP process:LowLevelAgent.LLAWPExec.Failed (Permission denied)

    Posted Jun 23, 2015 08:56 AM

    What is "EXTSHM" ? is should be "ON"

    If i remember correctly, default setting of  "OFF" limits to 12 shared memory segments. SiteMinder uses 13.

     

    Next step after that is to check actual permissions. but  it sounds like that has been done.