Article ID: 6903, created on Nov 12, 2009, last review on Apr 25, 2016

  • Applies to:
  • Operations Automation

Symptoms


When attempting to view APS Catalog in POA Provider Control Panel at Service Director > Application Manager > APS Catalog the following error is displayed:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /servlet/Turbine/action/pcp.XMenuSelect/bw_id/77425cf3a6cae930649f6c44ab8fde3d/referer/branding-112-cp.provider.com/nodeid/aps_catalog.

Reason: Error reading from remote server

Apache/2.0.52 (Red Hat) PHP/4.4.9 mod_ssl/2.0.52 OpenSSL/0.9.7a FrontPage/5.0.2.2635 Server at cp.provider.com Port 443
 

Cause


POA can not connect to APS Catalog which is configured in Provider Control Panel at Service Director > Application Manager > APS Catalog > 'Catalog Settings' tab.

By default APS Catalog is accessible by the following URL - https://apscatalog.com.

Resolution


Check if POA can resolve APS Catalog server to IP address and connect to it using URL specified in 'Catalog Settings', there could be several ways to check it.

1. Check if POA Management Node is working through the Privacy Proxy service: go to Top > System Director > Configuration Manager > Services, search for the 'PrivacyProxy' service and remember the host where it is installed. If you can not find the 'PrivacyProxy' service it means that POA does not use it and may connect to needed server directly, omitting proxy.

2. If POA is working through the Privacy Proxy then log into the server where this service is installed, otherwise log into POA Management node.

3. Check if you can connect to the APS Catalog server to the specified port, in the default installation it is apscatalog.com, port 443 (HTTPS). You may use such system utilities as 'telnet', 'tcpdump', 'curl' to check whether POA can connect to APS Catalog server either directly or via the Privacy Proxy server, e.g. run the utility 'tcpdump' and check where POA is trying to connect to and whether connection is successful or not.

If POA is working via proxy then you may enable debug options in the Privacy Proxy configuration file /etc/privoxy/config like these
debug         1 # show each GET/POST/CONNECT request
debug         2 # show each connection status
debug         4 # show I/O status
debug         8 # show header parsing
debug        16 # log all data into the logfile
debug        32 # debug force feature
debug        64 # debug regular expression filter
debug       128 # debug fast redirects
debug      4096 # Startup banner and warnings.
debug      8192 # Non-fatal errors

and restart Privacy Proxy service after that for the changes to take effect:
# /etc/init.d/privoxy restart
After it is done try to open APS Catalog in POA control panel and check in the /var/log/privoxy/logfile log file where Privacy Proxy is trying to connect to and result of these attempts.

If you checked and found that either POA Management Node can not connect to APS Catalog server (in case proxy is not used) or the server where the Privacy Proxy service is installed can not connect to APS Catalog, then you need to solve this problem. The typical reasons of problem is firewall configurarion and/or problem with DNS resolution in POA infrastructure.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF