Skip to main content
Participant
February 22, 2010
Question

Flash Media Server 3.0 admin console drops

  • February 22, 2010
  • 1 reply
  • 1592 views

Hello!

Please could anybody help me!

Every time while I'm connected to the FMS 3.0 admin console, it works for about 3-5 minutes and then drops. "Lost connection" message is appeared.

I have studied logs files and I found there the following information:

core.log

2010-02-22      01:19:40        31930   (i)2581233      Core (31930) disconnecting from admin: 200.     -
2010-02-22      01:19:40        32033   (i)2581233      Core (32033) disconnecting from admin: 200.     -

admin.log

2010-02-22      01:18:37        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:37        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -
2010-02-22      01:18:42        441     (e)2671287      Admin Command Timeout: (Command (getVHostStats) timed out.)     -

As far as I can, the problem with the "... disconnecting from admin: 200.". Where I can find information regarding this error code?

Thanks!

    This topic has been closed for replies.

    1 reply

    Janaki Lakshmikanthan
    Adobe Employee
    Adobe Employee
    February 23, 2010

    Hi,

    Could you pls look up your admin.log and master.log for more details and get back to us?

    Also check if your FMSAdmin.exe process is running. Meanwhile you can look up event viewer for any errors or warnings reported in it.

    Regards,

    Janaki L

    Participant
    February 23, 2010

    Please, below you can logs from master.log and admin.log files:

    master.log

    2010-02-22    15:49:48    15192    (i)2571011    Server starting...    -
    2010-02-22    15:49:48    15192    (i)2581224    Edge (15212) started, arguments : -edgeports "216.131.90.225:1935,443,80" -coreports "localhost:19350" -conf "/home/fms/etc/fms304/conf/Server.xml" -adaptor "_defaultRoot_" -name "_defaultRoot__edge1".    -
    2010-02-22    15:49:48    15192    (i)2581221    Core (15215) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app "registry" -inst "registry" -tag  -console  -conf "/home/fms/etc/fms304/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:registry:registry:".    -
    2010-02-22    15:49:50    15192    (i)2571111    Server started (/home/fms/etc/fms304/conf/Server.xml).    -
    2010-02-22    15:50:03    15192    (i)2581221    Core (15385) started, arguments : -adaptor "_defaultRoot_" -vhost
    2010-02-22    15:50:04    15192    (i)2581221    Core (15486) started, arguments : -adaptor "_defaultRoot_" -vhost
    2010-02-22    15:50:05    15192    (i)2581221    Core (15587) started, arguments : -adaptor "_defaultRoot_" -vhost
    2010-02-22    15:50:16    15192    (i)2581221    Core (15688) started, arguments : -adaptor "_defaultRoot_" -vhost
    2010-02-22    15:50:28    15192    (i)2581221    Core (15789) started, arguments : -adaptor "_defaultRoot_" -vhost
    2010-02-22    15:54:45    15192    (i)2581221    Core (16079) started, arguments : -adaptor "_defaultRoot_" -vhost
    2010-02-22    16:20:29    15192    (i)2581223    Core (15486) is no longer active.    -
    2010-02-22    16:20:34    15192    (i)2581223    Core (15587) is no longer active.    -
    2010-02-22    16:25:14    15192    (i)2581223    Core (16079) is no longer active.    -

    admin.log

    #Fields: date    time    x-pid    x-status    x-ctx    x-comment
    2010-02-22    15:47:03    14912    (e)2631013    Failed to create listener for adaptor admin, IP , port 1234: TCCommBridge::createListener 0.0.0.0:1234/v4: bind failed!!!.    -
    2010-02-22    15:47:03    14912    (e)2631013    Failed to create listener for adaptor , IP localhost, port 11110: TCCommBridge::createListener 127.0.0.1:11110/v4: bind failed!!!.    -
    2010-02-22    15:47:03    14912    (i)2571011    Server starting...    -
    2010-02-22    15:47:03    14912    (e)2631114    Failed to start listeners for adaptor FCSAdminIpcProtocol.    -
    2010-02-22    15:47:03    14912    (e)2581002    Server initialization failed; service will be stopped.    -
    2010-02-22    15:47:03    14912    (e)2571122    Server aborted.    -
    2010-02-22    15:49:13    10433    (e)2671287    Admin Command Timeout: (Command (getVHostStats) timed out.)    -
    2010-02-22    15:49:27    10433    (i)2581242    Core (10495) disconnected : _defaultRoot_: messenger.com:::_2.    -

    Please advise!

    Thanks,

    Paul

    Janaki Lakshmikanthan
    Adobe Employee
    Adobe Employee
    February 24, 2010

    Hi,

    Looks like your are running your FMSAdmin process in port - '1234'. Make sure this port is free and can be used by FMSAdmin. Then restart admin server and check what happens.

    Regards,

    Janaki L