Symantec Access Management

  • 1.  SPS Agent for virtual host : default did not initialized properly

    Posted May 17, 2016 04:58 PM

    Hello All,

     

       I have this SPS server which is giving this error. I have enabled DEBUG logging but that does not give me exact reason why virtual host is not initializing.

     

    [17/May/2016:15:27:47-950] [FATAL] - [ERROR] Agent for virtual host : default did not initialized properly

     

    Any suggestions what needs to be done to resolve this issue. This SPS never worked on this server.

     

    File Version: 12.52 .0102 .766

     

     

    I see below error in nohup.out20160517_152649

     

    SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener

    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flowbuilder_extensionRegistry' defined in class path resource [spring/appContext-flowbuilder.xml]: Invocation of init method failed; nested exception is org.mybatis.spring.MyBatisSystemException: nested exception is org.apache.ibatis.exceptions.PersistenceException:

    ### Error querying database.  Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: Invalid Oracle URL specified

    ### The error may exist in URL [jar:file:/C:/Program%20Files%20(x86)/CA/secure-proxy/Tomcat/webapps/authapp/WEB-INF/lib/cawebflow-data-8.0-SNAPSHOT.jar!/ibatis/flow_state_mapper.xml]

    ### The error may involve com.ca.aa.ui.framework.cawebflow.data.flow.state.dao.FlowStateDAO.getAllExtensionClasses

    ### The error occurred while executing a query

    ### Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: Invalid Oracle URL specified

      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455)

      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)

      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)

      at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)

      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)

      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)

      at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913)

      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464)

      at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385)

      at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284)

      at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)

      at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5016)

      at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5524)

      at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

      at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)

      at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)

      at java.util.concurrent.FutureTask.run(FutureTask.java:262)

      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

      at java.lang.Thread.run(Thread.java:745)

     

    is it possible that due to this error Virtual host is not initializing? Any suggestions for this issue.

     

    Thank you



  • 2.  Re: SPS Agent for virtual host : default did not initialized properly
    Best Answer

    Posted May 17, 2016 08:25 PM

    Hi Richard,

     

    Are you using Session Assurance feature, if not follow below instructions:

     

    In your server.conf, you have following:

     

    <Context name="AALoginService">

     

    docBase="aaloginservice"

    path="aaloginservice"

    enable="yes"

    </Context>

     

    <Context name="Advacned Auth Application">

     

    docBase="authapp"

    path="authapp"

    enable="yes"

    </Context>

     

    <Context name="UI Application">

     

    docBase="uiapp"

    path="uiapp"

    enable="yes"

    </Context>

    </Contexts>

     

    Please disable all those by setting enable="no".

    Then  restart both SiteMinder Proxy Engine and Secure Proxy Service

     

    If you are need Session Assurance, then please try re-configuring SPS.

     

    Regards,

    Ujwol



  • 3.  Re: SPS Agent for virtual host : default did not initialized properly

    Posted May 18, 2016 09:35 AM

    Thanks Ujwol,

     

       After disabling that portion I don't see error in nohupout file. But Virtual hosts are still not initializing:

     

    [18/May/2016:09:30:04-932] [INFO] - Initialize: [Agent Configuration = C:\Program Files (x86)\CA\secure-proxy\proxy-engine\conf\defaultagent\WebAgent.conf][Single Process Mode = true][retcode = -1][Initialized = false]

    [18/May/2016:09:30:04-943] [FATAL] - [ERROR] Agent for virtual host : default did not initialized properly

    [18/May/2016:09:30:04-943] [INFO] - omitheaders_without_smsession: sending all headers

    [18/May/2016:09:30:04-946] [INFO] - Custom Error Pages : Custom error pages is disabled

    [18/May/2016:09:30:04-948] [INFO] - Custom Error Pages : Using default implementation.

    [18/May/2016:09:30:04-951] [INFO] - ProxyValve::startMonitoring: SPS_Data_Collection_and_Monitoring: No metric-reporter has been configured

    [18/May/2016:09:30:10-120] [INFO] - Initialize: [Agent Configuration = C:\Program Files (x86)\CA\secure-proxy\proxy-engine\conf\defaultagent\WebAgent.conf][Single Process Mode = true][retcode = -1][Initialized = false]

    [18/May/2016:09:30:10-120] [FATAL] - [ERROR] Agent for virtual host : default did not initialized properly

    [18/May/2016:09:30:10-120] [INFO] - omitheaders_without_smsession: sending all headers

     

    Any suggestions to troubleshoot?

     

    Thank you



  • 4.  Re: SPS Agent for virtual host : default did not initialized properly

    Posted May 18, 2016 10:53 AM

    Next, would be troubleshooting the agent init part and check spa agent logs & ps logs.



  • 5.  Re: SPS Agent for virtual host : default did not initialized properly

    Posted May 18, 2016 12:12 PM

    Thanks Ujwol,

     

       I was able to identify the issue, looking at affwebservices.log file, It stated cannot find ACO.

    I was expecting this kind of error should be noted in server.log file. because SPS agent logs will not create until the Virtual host is initialized properly, and policy server logs were not giving any error related to SPS startup.

    I am not sure if this could be a enhancement request or there are some other file we can look at or we are expected to predict something out of this line:

     

    Initialize: [Agent Configuration = C:\Program Files (x86)\CA\secure-proxy\proxy-engine\conf\defaultagent\WebAgent.conf][Single Process Mode = true][retcode = -1][Initialized = false]

     

    Thanks Again



  • 6.  Re: SPS Agent for virtual host : default did not initialized properly

    Posted May 18, 2016 07:10 PM

    Hi Richard,

     

    You are welcome.

     

    Yes, it would have been better if the error was more descriptive.

    I suggest raising an enhancement request (idea) here :

    CA Security

     

    Regards,

    Ujwol



  • 7.  Re: SPS Agent for virtual host : default did not initialized properly

    Broadcom Employee
    Posted Dec 28, 2018 12:56 PM

    In  my case, with the lab based images, I had to restart the SPS services to resolve the same errors, as all the configs looked correct.

     

    [BEFORE SERVICES RESTART IN SERVER.LOG]

    [28/Dec/2018:08:39:16-296] [INFO] - Initialize: [Agent Configuration = C:\Program Files\CA\secure-proxy\proxy-engine\conf\defaultagent\WebAgent.conf][Single Process Mode = true][retcode = -1][Initialized = false]
    [28/Dec/2018:08:39:16-296] [ERROR] - [ERROR] Agent for virtual host : default did not initialized properly

     

    [AFTER SERVICES RESTART IN SERVER.LOG]

    [28/Dec/2018:11:48:10-115] [INFO] - Initialize: [Agent Configuration = C:\Program Files\CA\secure-proxy\proxy-engine\conf\defaultagent\WebAgent.conf][Single Process Mode = true][retcode = 1][Initialized = true]