Skip to main content
P
ptamilar
Participating Frequently
December 28, 2009
Question

fmsmaster using admin server port

  • December 28, 2009
  • 2 replies
  • 1718 views

It seems after a while the admin server stops responding on our fms server.  When logging into the linux machine, I can see that the fms admin process is not running, and the pid in fmsadmin.pid is stale.  When trying to restart the service with:

"./fmsmgr adminserver restart"

it fails to start the service with the following message in /var/log/messages:

Failed to create listener for adaptor admin, IP , port 1111: TCCommBridge::createListener 0.0.0.0:1111/v4: bind failed!!!.

Failed to create listener for adaptor admin, IP , port 1111: TCCommBridge::createListener 0.0.0.0:1111/v4: bind failed!!!.

Failed to initialize listeners for adaptor admin, FMS is already running or other processes are using the same ports.

Checking to see what is listening on port 1111 with netstat:

tcp        0      0 127.0.0.1:11110             0.0.0.0:*                   LISTEN      11005/fmsmaster
tcp        0      0 0.0.0.0:1111                0.0.0.0:*                   LISTEN      11005/fmsmaster

This is the second time this has happend.  How is it possible for fmsmaster to be using the admin server ports, and how would I prevent this in the future?

Thanks,

    This topic has been closed for replies.

    2 replies

    P
    ptamilarasan
    Participant
    January 8, 2010
    • 5065bfd6f653ec44bfb34d158297604b  fmsmaster
    • 303928c69d89aaf28da983925874c73b  fmscore
    • 3c39636a7c99d3aa431985d20b780a75  fmsedge
    • 54167368f1fbe02d34cfc0e639787203  fmsadmin

    Today it seems it is showing as fmscore is incorrectly listed as using this port.

    tcp        0      0 127.0.0.1:11110             0.0.0.0:*                   LISTEN      922/fmscore
    tcp        0      0 0.0.0.0:1111                0.0.0.0:*                   LISTEN      922/fmscore

    apache     922 11005  0 09:02 ?        00:00:00 /usr/local/macromedia/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app Voice3 -inst 2904 -tag -conf ./conf/Server.xml -name _defaultRoot_:_defaultVHost_:Voice3:2904:

    FMS is still configured to only listen on 1935,443,80.  Does this mean it is something to do with the machine itself or maybe the installation of fms?

    P
    ptamilarasan
    Participant
    January 8, 2010

    Also not sure if this is related, but today I noticed a lot of these messages in /var/log/messages.  Not sure if these were also present the last time we had issues.

    Jan  8 13:32:11 test Server[11005]: Shared memory heap (__FCS__) has exceeded 90 usage. Consider increasing the heap size to prevent future memory allocation failures.

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    January 8, 2010

    These are interesting notes here. We can increase your shared memory heap, but that's only relevant if it's simply just a little too small and not something more significant. Do you have any details on how this manifests?

    Asa

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    December 28, 2009

    Check your Adaptor.xml configuration.  What do you have for the HostPort settings?

    P
    ptamilarAuthor
    Participating Frequently
    December 28, 2009

    Host port is set to the following:

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

    My fms.ini defines ADAPTOR.HOSTPORT as the following:

    ADAPTOR.HOSTPORT = XXX.XXX.XXX.XXX:1935,443,80

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    December 28, 2009

    Well, those configs look right - what looks wrong though is that fmsmaster would be listening on anything - that's just not right.  It doesn't even call to listen on any sockets at all.  It doesn't have the code.  Perhaps we've mistakenly labelled fmsadmin (who is programed to do this) as fmsmaster - we can check this via md5 checksums.  If you grab the md5 checksum of the executable logging this and the master.00.log and admin.00.log which you can get from your logs directory under FMS, then we should have enough to ID the issue some more.

    You can send these to me - awhilloc@adobe.com

    Asa

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