Skip to main content
November 21, 2008
Answered

FMS3 Linux and virtual host

  • November 21, 2008
  • 4 replies
  • 942 views
Instaled FMS3 on my Linux box, but some strange things happen with virtual host configuration:

1. add virtual host directory to /conf/_defaultRoot_ (just making a copy of _defaultVHost_). It contains all needed files - Application.xml and Vhost.xml with default settings
2. Restart the server

When I login into admin console, new vhost appears in the list, but it's impossible to connect to it, or just restart it.
Permissions are ok.

Am I forgetting something?
    This topic has been closed for replies.
    Correct answer
    FMS automaticly unloads vhost if it has no connections, and loads vhost on connect.

    4 replies

    Participant
    February 12, 2009
    i can't login in admin console, fms 3.5, linux ES5
    http://192.168.1.44/fms_adminConsole.htm

    server add: 192.168.1.44 or 192.168.1.44:1111 or 192.168.1.44:1112
    id: mint
    pd: video123

    fms.ini

    SERVER.ADMIN_USERNAME = mint

    # Password for server admin
    # For example:
    # SERVER.ADMIN_PASSWORD = bar
    #
    SERVER.ADMIN_PASSWORD = video123
    Correct answer
    November 26, 2008
    FMS automaticly unloads vhost if it has no connections, and loads vhost on connect.
    November 26, 2008
    I finnaly get it - FMS starts fmscore process for each vhost, but after about 5-7 minutes of work every process quits. Logs don't say anything, what can it be?

    /opt/adobe/fms/fmscore -console -adaptor _defaultRoot_ -vhost test.com -ap -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:test.com:::
    Adobe Flash Media Server (Core)Console mode.
    Host: localhost IPv4: 127.0.0.1
    Starting admin app on core (4651).
    Core (4651) connecting to admin.
    Core (4651) connected to admin.
    Core (4651) connection to admin accepted.
    Core (4651) sending register cmd to edge.
    Core (4651) disconnected from edge.
    Core (4651) disconnecting from admin.
    Unloaded application instance admin

    November 21, 2008
    Try using the new Vhost url or IP as the server address when you connect via the console.
    November 24, 2008
    Seems like FMS uses separate "fmscore" process for each virtual host, is it true?

    fmscore -adaptor _defaultRoot_ -vhost <VHOST1> -app -inst -tag _2 -console -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:<VHOST1>:::_2

    fmscore -adaptor _defaultRoot_ -vhost <VHOST2> -app -inst -tag _2 -console -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:<VHOST2>:::_2