Archiver Appliance mgmt tomcat issue

["Manoussakis, Adamandios via Tech-talk" <tech-talk at aps.anl.gov>]

Hey All,

 

I am trying to figure out why I cannot access the front end interface of the archiver (192.168.3.50:17665/mgmt/ui/index.html) from another subnet.  Locally it works perfectly fine, able to archive PVs and retrieve with Phoebus for example or even using python.  When I try to get the web page to serve up on another PC that is not on the same subnet 192.168.2.25(PC) and 192.168.3.50(Archiver) for example it seems like the request gets stuck.  Some possible debugging has led to the JS not being loaded properly on the web browsers but I have looked for anything that would block on the network and cant seem to find any issue.  I also looked at the install guide again and found this part

 

“

Editing the conf/server.xml file to change the ports to better suit your installation.

1. By default, the connector port for the HTTP connector is set to 8080. Change this to the port used by the mgmt webapp for this appliance, in this example, 17665.

<Connector connectionTimeout="20000" port="17665" protocol="HTTP/1.1" redirectPort="8443"/>

“

 

Which matches the port I use for the mgmt tomcat instance.  I wasn’t sure about the redirectPort if that had to be changed?  I also have tried the archiver on multiple computers and using multiple other PCs on different subnets to see if a PC was an issue but get the same stuck request.  I am fairly sure it is something I have misconfigured on the archiver possibly.  For phoebus I have the settings.ini set for the epics env variables (not sure if these impact those requests for PVs though from the archiver) and I have the usual env variables set for EPICs.