Skip to main content
A
Athtart
Participating Frequently
July 7, 2009
Question

Can not connect to Admin Console FMS 3.5 running separate Apache Server

  • July 7, 2009
  • 1 reply
  • 2127 views

Hi All! I have installed the FMS 3.5 Server on a separate IP from our main Apache Server: The server is running Redhat Linux 2.6.18-128.1.10.el5

FMS 3.5 running on ***.***.**.138 using ports 1935, 8080 (Admin Server using port 1111)

Apache 2 running on ***.***.**.139 using port 80, 443. (several sites setup on this IP)

However, when accessing the fms_adminConsole.htm in the root directory of one of the domains on ***.***.**.139, all login attempts fail. I am connecting to localhost and using the assigned user and password set up in fms.ini. Using either IP fails as well. The FMS server is set up to listen to all hosts as no specific IPs were set.

/var/log/messages show that FMS and the Admin Server are up an running and listening:

Jul  7 12:15:37 228215-web1 Service[28196]: Server starting...

Jul  7 12:15:37 228215-web1 Service[28196]: Server started (/opt/adobe/fms/conf/Server.xml).

Jul  7 12:15:37 228215-web1 Adaptor[28216]: Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4

Jul  7 12:15:38 228215-web1 Adaptor[28216]: Listener started ( _defaultRoot__edge1 ) : 1935/v4

Jul  7 12:15:38 228215-web1 Adaptor[28216]: Listener started ( _defaultRoot__edge1 ) : 8080/v4

Jul  7 12:16:20 228215-web1 Service[28480]: Server starting...

Jul  7 12:16:20 228215-web1 Adaptor[28480]: Listener started ( FCSAdminIpcProtocol ) : localhost:11110/v4

Jul  7 12:16:21 228215-web1 Adaptor[28480]: Listener started ( FCSAdminAdaptor ) : 1111/v4

Jul  7 12:16:22 228215-web1 Service[28480]: Server started (./conf/Server.xml).

All other settings for FMS are default. This is my first time setting up FMS as a fresh install on a new unknown server and I am at a loss as to what settings to check or which files I may need to modify to get it to connect properly. It is a managed server is hosted by rackspace.com if that makes any difference.
Sorry if I have not provided enough info... let me know what I missed and I will supply it.

    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    July 7, 2009

    I'm a little confused... when you say you're trying to connect to localhost, are you running the admin console locally on the server, or from ouside the server's LAN?

    I'd first check to make sure port 1111 is open. Try hitting the admin service via http:

    http://fmsipaddress:1111

    If you get an XML document describing missing credentials, you'll know port 1111 is open. If you get a timeout waiting for the page to load, chances are port 1111 is closed.

    A
    AthtartAuthor
    Participating Frequently
    July 7, 2009

    Sorry for the confusion! *I* am the one really confused. But to answer your question (I hope), the webpage is on the same physical server as the FMS server, but I am using an outside network (I am not on the local server network) to browse the webpages.

    Both IPs fail when trying to reach:

    http://***.***.**.138:1111

    http://***.***.**.139:1111

    Does that mean the ports are blocked? The /var/log/messages shows:

    Jul  7 13:20:37 228215-web1 Service[29862]: Server starting...

    Jul  7 13:20:37 228215-web1 Service[29862]: Server started (/opt/adobe/fms/conf/Server.xml).

    Jul  7 13:20:37 228215-web1 Adaptor[29882]: Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4

    Jul  7 13:20:38 228215-web1 Adaptor[29882]: Listener started ( _defaultRoot__edge1 ) : 1935/v4

    Jul  7 13:20:38 228215-web1 Adaptor[29882]: Listener started ( _defaultRoot__edge1 ) : 8080/v4

    Jul  7 13:20:51 228215-web1 Service[30144]: Server starting...

    Jul  7 13:20:51 228215-web1 Adaptor[30144]: Listener started ( FCSAdminIpcProtocol ) : localhost:11110/v4

    Jul  7 13:20:52 228215-web1 Adaptor[30144]: Listener started ( FCSAdminAdaptor ) : 1111/v4

    Jul  7 13:20:53 228215-web1 Service[30144]: Server started (./conf/Server.xml).

    A
    Anonymous
    July 7, 2009

    Yeah... if the service is running, and you can't access it via http, chances are port 1111 is closed on the firewall. I seem to remember a client of mine telling me that they needed to get rackspace to open the port for them (I'm pretty sure they have firewalls in front of their managed servers).

    While you're at it, you might want to confirm that port 1935 is open as well.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices