Symantec Privileged Access Management

 View Only

[PIM] Redhat, ipv6 and tomcat/proxy recording not working (12.9+)

  • 1.  [PIM] Redhat, ipv6 and tomcat/proxy recording not working (12.9+)

    Broadcom Employee
    Posted Nov 17, 2015 07:35 PM

    I have had a couple of cases recently where customers have reported proxy recording not working. This turned out to be due to redhat/java preferring to use ipv6 and not giving tomcat a port on ipv4 addresses. My solution to add address="0.0.0.0" to the connector port in /opt/CA/AccessControlServer/apache-tomcat-7.0.54/conf/server.xml from the Re: PIM: Proxy Recording "It's not recording!" Checklist  thread did not work.

     

    Here is a another solution, run the following commands:

     

    echo CATALINA_OPTS=\"-Djava.net.preferIPv4Stack=true\" >> /opt/CA/AccessControlServer/apache-tomcat-7.0.54/bin/setenv.sh
    chmod +x /opt/CA/AccessControlServer/apache-tomcat-7.0.54/bin/setenv.sh

     

    This will create a file, or append to it if it already exists, called /opt/CA/AccessControlServer/apache-tomcat-7.0.54/bin/setenv.sh with the line:


    CATALINA_OPTS="-Djava.net.preferIPv4Stack=true"

     

    This will tell java to use ipv4 instead of ipv6 when starting tomcat. You need to restart tomcat after doing this, of course.

     

    You could of course use an editor like vi to create or edit setenv.sh, but who wants to use vi...?