Skip to main content
A
Anonymous
June 10, 2010
Question

VOD is stopping whenever origin restarts

  • June 10, 2010
  • 2 replies
  • 864 views

<running environment>

-windows 2003 server

-using linux based load balancer(two origin only FMIS)

-FMIS 3.5.3

-default settings of all XML, CONF

-origin only and 2 servers

-providing live and vod services(vod files are placed in NAS storage and FMLE is feeding live video)

-only alphabet charater file name (no * , no _, no other special character)  of VOD files

-nomally 300 VOD clients and 200 LIVE clients are connected on live time.

-changed HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort created and set value 65535 in registry)

I changed this setting to give more connections to Apache and FMS services, cause of they are making a lot of connection to connect each other.

Live streaming is always fine, but VOD playings are stopped in every 3x minutes ( files are ok and checked by FLVCHECK and over 1 hour).

And the time information is chanced to NN NA in client player.(adobe reference player)

And origin process was restarted at the same time. But Live client was not stopped.

How can I keep the VOD connection alive till the end of file(duration)?

    This topic has been closed for replies.

    2 replies

    A
    Anonymous
    June 28, 2010

    Cause all services are assinged to real domain address,

    I can't turn off the load balancer but I can set the route to single path.

    And also I think HDD is much better than NAS, so I prepared official NAS (Network appliance new model), and tested.

    But the result was same.

    Symtom was simple, As connectors incresesed, system memory was assgined to core process and was increasing.

    And the connectors has disconnected, connections were disconnected. (I checked netstat -a).

    But the memory which was assinged to connectors was not released

    I mean the memory kept increasing, and after 1.xGB, then the process has been killed and restarted

    S
    SE_0208
    Participating Frequently
    July 1, 2010

    Hi TomSeo75,

    Since your set-up cannot be replicated at my end, i won't be able to reproduce your scenario. If you are still facing same issue which you have mentioned i can help you open a support incident and let our support team get in touch with you to get resolution to your problem. In order to open incident for you, i would like to have your contact details where our support person can get in touch with you. Please mail me at rchari@adobe.com with your contact details.

    S
    SE_0208
    Participating Frequently
    June 10, 2010

    changed HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPo rt created and set value 65535 in registry)

    I changed this setting to give more connections to Apache and FMS services, cause of they are making a lot of connection to connect each other.

    - Before you changed this setting did you face any issues.

    I think what is happening probably core on which VOD is on is going down and "live" application is loaded on another core so that is not getting affected.

    Can you paste you logs here: master,edge,core and access logs.

    Also are you using one server for VOD and one server for Live or you are using both for live and vod and then load balancing amongst them.

    Do you get this error when your reach particular connection limit or do you get it at the very start.

    Also if you do not use load balancer, does that make any difference.

    Also you are saying you are using NAS , if you use local storage does it cause same issues.

    A
    Anonymous
    June 10, 2010

    Before changing the registry, it was terrible, as clients connects, all service was stopped and FMS could not make more connections.

    Then, I had to restart the services.

    And I'm using VOD and LIVE same macine and two servers are same.

    I don't think this is not connection limit, this error also happens when connections was very low.

    I mean that every VOD user faces this error after 3x mins when the heavy traffic or not.

    I cound not test without load balancer and NAS, and two macines are sharing the VOD files in NAS.

    here is error log

    master.log

    this error are happend every 20~30 mins.

    2010-06-10 19:03:05 1304 (i)2581223 Core (4856) is no longer active. -

    2010-06-10 19:03:05 1304 (w)2581256 Core (4856) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure! -

    2010-06-10 19:03:07 1304 (i)2581221 Core (4840) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "C:\Program Files\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

    2010-06-10 19:24:00 1304 (i)2581223 Core (4840) is no longer active. -

    2010-06-10 19:24:00 1304 (w)2581256 Core (4840) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure! -

    2010-06-10 19:24:03 1304 (i)2581221 Core (9188) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "C:\Program Files\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

    2010-06-10 19:42:40 1304 (i)2581223 Core (9188) is no longer active. -

    2010-06-10 19:42:40 1304 (w)2581256 Core (9188) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure! -

    2010-06-10 19:42:43 1304 (i)2581221 Core (8544) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "C:\Program Files\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

    2010-06-10 20:05:31 1304 (i)2581223 Core (8544) is no longer active. -

    2010-06-10 20:05:31 1304 (w)2581256 Core (8544) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure! -

    2010-06-10 20:05:31 1304 (i)2581221 Core (4932) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "C:\Program Files\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

    2010-06-10 20:05:35 1304 (i)2581223 Core (8544) is no longer active. -

    2010-06-10 20:23:30 1304 (i)2581223 Core (4932) is no longer active. -

    2010-06-10 20:23:30 1304 (w)2581256 Core (4932) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure! -

    2010-06-10 20:23:31 1304 (i)2581221 Core (9352) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "C:\Program Files\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

    2010-06-10 20:40:31 1304 (i)2581223 Core (9352) is no longer active. -

    2010-06-10 20:40:31 1304 (w)2581256 Core (9352) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure! -

    2010-06-10 20:40:31 1304 (i)2581221 Core (8912) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "C:\Program Files\Adobe\Flash Media Server 3.5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

    2010-06-10 20:40:35 1304 (i)2581223 Core (9352) is no longer active. -

    edge log

    because of master log, this edge kept re-connecting

    2010-06-10 18:41:27 7456 (i)2581252 Registering core (4856). -

    2010-06-10 19:03:01 7456 (i)2581250 Edge disconnected from core (4856). -

    2010-06-10 19:03:08 7456 (i)2581252 Registering core (4840). -

    2010-06-10 19:23:58 7456 (i)2581250 Edge disconnected from core (4840). -

    2010-06-10 19:24:03 7456 (i)2581252 Registering core (9188). -

    2010-06-10 19:42:37 7456 (i)2581250 Edge disconnected from core (9188). -

    2010-06-10 19:42:43 7456 (i)2581252 Registering core (8544). -

    2010-06-10 20:05:30 7456 (i)2581250 Edge disconnected from core (8544). -

    2010-06-10 20:05:32 7456 (i)2581252 Registering core (4932). -

    2010-06-10 20:23:27 7456 (i)2581250 Edge disconnected from core (4932). -

    2010-06-10 20:23:31 7456 (i)2581252 Registering core (9352). -

    2010-06-10 20:40:30 7456 (i)2581250 Edge disconnected from core (9352). -

    2010-06-10 20:40:32 7456 (i)2581252 Registering core (8912). -

    2010-06-10 20:55:48 7456 (i)2581250 Edge disconnected from core (8912). -

    core log

    also same, same time, core kept restarting.

    #Date: 2010-06-10

    #Fields: date time x-pid x-status x-ctx x-comment

    2010-06-10 19:42:43 8544 (i)2581237 Starting admin app on core (8544). -

    2010-06-10 19:42:43 8544 (i)2581238 Core (8544) connecting to admin. -

    2010-06-10 19:42:43 8544 (i)2581231 Core (8544) connected to admin. -

    2010-06-10 19:42:43 8544 (i)2581234 Core (8544) connection to admin accepted. -

    2010-06-10 19:42:43 8544 (i)2581246 Core (8544) sending register cmd to edge. -

    #Date: 2010-06-10

    #Fields: date time x-pid x-status x-ctx x-comment

    2010-06-10 20:05:32 4932 (i)2581237 Starting admin app on core (4932). -

    2010-06-10 20:05:32 4932 (i)2581238 Core (4932) connecting to admin. -

    2010-06-10 20:05:32 4932 (i)2581231 Core (4932) connected to admin. -

    2010-06-10 20:05:32 4932 (i)2581234 Core (4932) connection to admin accepted. -

    2010-06-10 20:05:32 4932 (i)2581246 Core (4932) sending register cmd to edge. -

    #Date: 2010-06-10

    #Fields: date time x-pid x-status x-ctx x-comment

    2010-06-10 20:23:31 9352 (i)2581237 Starting admin app on core (9352). -

    2010-06-10 20:23:31 9352 (i)2581238 Core (9352) connecting to admin. -

    2010-06-10 20:23:31 9352 (i)2581231 Core (9352) connected to admin. -

    2010-06-10 20:23:31 9352 (i)2581234 Core (9352) connection to admin accepted. -

    2010-06-10 20:23:31 9352 (i)2581246 Core (9352) sending register cmd to edge.

    admin log

    also same, core kept reconnecting to admin

    2010-06-10 19:24:03 1328 (i)2581241 Connection to admin received. -

    2010-06-10 19:24:03 1328 (i)2581243 Connection from core 9188 received. -

    2010-06-10 19:24:03 1328 (i)2581244 Connection from core 9188 accepted. -

    2010-06-10 19:42:37 1328 (i)2581242 Core (9188) disconnected : _defaultRoot_:_defaultVHost_:::_1. -

    2010-06-10 19:42:43 1328 (i)2581241 Connection to admin received. -

    2010-06-10 19:42:43 1328 (i)2581243 Connection from core 8544 received. -

    2010-06-10 19:42:43 1328 (i)2581244 Connection from core 8544 accepted. -

    2010-06-10 20:05:30 1328 (i)2581242 Core (8544) disconnected : _defaultRoot_:_defaultVHost_:::_1. -

    2010-06-10 20:05:32 1328 (i)2581241 Connection to admin received. -

    2010-06-10 20:05:32 1328 (i)2581243 Connection from core 4932 received. -

    2010-06-10 20:05:32 1328 (i)2581244 Connection from core 4932 accepted. -

    2010-06-10 20:23:27 1328 (i)2581242 Core (4932) disconnected : _defaultRoot_:_defaultVHost_:::_1. -

    2010-06-10 20:23:31 1328 (i)2581241 Connection to admin received. -

    2010-06-10 20:23:31 1328 (i)2581243 Connection from core 9352 received. -

    2010-06-10 20:23:31 1328 (i)2581244 Connection from core 9352 accepted. -

    2010-06-10 20:40:30 1328 (i)2581242 Core (9352) disconnected : _defaultRoot_:_defaultVHost_:::_1. -

    2010-06-10 20:40:32 1328 (i)2581241 Connection to admin received. -

    2010-06-10 20:40:32 1328 (i)2581243 Connection from core 8912 received. -

    2010-06-10 20:40:32 1328 (i)2581244 Connection from core 8912 accepted. -

    2010-06-10 20:55:48 1328 (i)2581242 Core (8912) disconnected : _defaultRoot_:_defaultVHost_:::_1. -

    2010-06-10 20:55:49 1328 (i)2581241 Connection to admin received. -

    2010-06-10 20:55:49 1328 (i)2581243 Connection from core 10236 received. -

    2010-06-10 20:55:49 1328 (i)2581244 Connection from core 10236 accepted. -

    S
    SE_0208
    Participating Frequently
    June 10, 2010

    Its clear from logs that FMS core is crashing. In order to nail down can you try below steps:

    1. Keep same set up but keep the VOD files on some local storage and run same scenario. See if you get the crash again.

    2. If you still get crash, go to FMS directly and not via Load balancer.

    This is will help us nail down what is causing the issue.

    If you do not get crash at step 1 most likely it might be issue with NAS. Can you triage and let me know about your findings.

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