Skip to main content
B
Barjawi
Inspiring
November 14, 2011
Answered

FMS 3.5 Upgrades not Binding to ports 80, 1935

  • November 14, 2011
  • 1 reply
  • 2762 views

I have installed and ran FMS Development Server 3.5 on my Fedora 15 x32 for a long while now. Everything works fine. However, recently I found out about the upgrades for the server. So I downloaded all of them (3.5.2 - 3.5.7)... the current version I have is 3.5.1... and it works fine. Installing any of the new upgrade versions on the server works fine... and when starting the server doesn't give any errors.

In /var/logs/messages it says:

Server starting...

Server started (/opt/adobe/fms/conf/Server.xml).

however, checking the binding of my IP address, it shows no bindings to ports 80 and 1935. The admin server works successfully because I can see binding to port 1111.

Whenever I run my test application which I used to run successfully on FMS 3.5.1, I cannot get a connection.

So I was wondering whats wrong... why it doesn't bind anymore? is there something wrong with my upgrade process?? I even tried uninstalling whatever I currenltly have and installing the new upgrade... same result.

I need the upgrades as they contain fixes of bugs that I need to have on my server.

Thanks,

This topic has been closed for replies.
Correct answer Barjawi

you have configured the settings of apache to listen at port 80 ... and u are also using HTTP Proxy Host ... I guess this is the reason of the conflict ..

u are using HTTPPROXY.HOST = 192.168.56.103:8134 , in apache .. u need to have an entry of Listen 192.168.56.103:8134 as per my past troubleshootings .. as HTTP access is done by FMS not by apache in the real time .. apache proxies request to 8134 which are then carried by FMS over port 80 ...


thank you vibsgupta for pointing out the PROXY thing... I shouldn't have filled in the PROXY value.

However, this is not the real reason for my problem. The ports are not binding and FMS is not working properly because I am using Fedora. Once I switched to CentOS everything worked like charm out of the box.

Thanks,

1 reply

B
BarjawiAuthor
Inspiring
November 16, 2011

Any ideas on how to debug this problem?? anybody?!!

Graeme Bull
Community Expert
Graeme BullCommunity Expert
Community Expert
November 16, 2011

Might be that you haven't changed the xml files to point to the right IP address. Actually, that can be done in the fms.ini file.

B
BarjawiAuthor
Inspiring
November 18, 2011

I haven't found full tutorials on how to do this... only bits here and there on the web. I have configured FMS 3.5.1 and it worked successfully with my configurations... I have done the same configurations for the new upgrade... but it didn't work. So I cannot see why there should be a problem with the configurations.

This is how I configured it:

I want to bind FMS to port 80, but since I have httpd server on the same virtual machine, I wasn't able to do so. So I added another ethernet card to the machine, and configured a new IP address.

So now I have two IP addresses:

192.168.56.102

and

192.168.56.103

I have configured httpd server to use the *.102 one by modifying httpd.conf like the following:

added:

Listen 192.168.56.102:80

added:

NameVirtualHost 192.168.56.102:80

then used that IP in my VirtualHosts:

<VirtualHost 192.168.56.102:80>

</VirtualHost>

Then I configured the FMS to use the *.103 IP address by modifying the following files:

fms/conf/fms.ini

fms/conf/Server.xml

fms/conf/_defaultRoot_/Adaptor.xml

I configured these files and change any place that contains "localhost" to use "192.168.56.103"

and added the same IP address to all port configurations in these file.

Here is the list of changes I made:

fms.ini:

SERVER.ADMINSERVER_HOSTPORT = 192.168.56.103:1111

ADAPTOR.HOSTPORT = 192.168.56.103:80,1935

HTTPPROXY.HOST = 192.168.56.103:8134

Server.xml:

<IpcHostPort>192.168.56.103:11110</IpcHostPort>

<Localhost>192.168.56.103</Localhost>

Adaptor.xml:

<HostPort name="edge1" ctl_channel="192.168.56.103:19350">${ADAPTOR.HOSTPORT}</HostPort>

<!-- this block exists two times in Adaptor.xml -->

<Redirect enable="false" maxbuf="16384">

       <Host port="80">192.168.56.103:8080</Host>

       <Host port="443">192.168.56.103:8443</Host>

</Redirect>

So:

1- Is this the correct way to do it?

2- If it is, then again, why it doesn't bind..? or at least why it worked fine with FMS 3.5.1 but not the newer versions.

Thanks,

Barjawi

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