Skip to main content
Participating Frequently
June 12, 2011
Question

No response from core(s) : 32160 (active))

  • June 12, 2011
  • 1 reply
  • 645 views

Hello everybody,

I have a VOD application running fine on FMS 3.5.5 on Ubuntu. But in the past few days I noticed some problems. As per FMS Console it seems all streams are playing fine but when I try to "watch" something, the connection does not seem to complete.

So I found the following:

admin.00.log

2011-06-11      21:19:01        32065   (e)2671287      Admin Command Timeout: (Command (getInstanceStats) timed out. No response from core(s) : 32160 (active))        -

2011-06-11      21:19:01        32065   (e)2671287      Admin Command Timeout: (Command (getInstanceStats) timed out. No response from core(s) : 32160 (active))        -

2011-06-11      21:19:01        32065   (e)2671287      Admin Command Timeout: (Command (getInstanceStats) timed out. No response from core(s) : 32160 (active))        -

2011-06-11      21:19:01        32065   (e)2671287      Admin Command Timeout: (Command (getInstanceStats) timed out. No response from core(s) : 32160 (active))        -

2011-06-11      21:19:01        32065   (e)2671287      Admin Command Timeout: (Command (getInstanceStats) timed out. No response from core(s) : 32160 (active))        -

2011-06-11      21:19:01        32065   (e)2671287      Admin Command Timeout: (Command (getInstanceStats) timed out. No response from core(s) : 32160 (active))        -

.

.

.

# vmstat 2 10
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
17  0 4143328  52152  20648 680680  136   29   190    35    0    0 18 14 65  3
17  0 4143328  52268  20648 680680    0    0     0     0 1297 69785 53 47  0  0
18  0 4143328  52640  20648 680680    0    0     0    14 1265 69582 56 44  0  0
18  0 4143312  52020  20648 681184   48    0   304     0 1242 69532 52 48  0  0
18  0 4143312  52020  20648 681192    0    0     0     0 1263 69790 52 48  0  0
18  0 4143312  51772  20648 681192    0    0     0     0 1237 69597 53 47  0  0
17  0 4143312  51600  20648 681192    0    0     0     0 1299 69653 54 46  0  0
17  0 4143308  51020  20656 681996    2    0   390     0 1304 69768 53 47  0  0
17  0 4143308  51020  20656 681964    0    0     0     0 1360 69988 52 48  0  0
17  0 4143308  51144  20664 681956    0    0     0    20 1293 70004 56 44  0  0

.

.

# free -m
             total       used       free     shared    buffers     cached
Mem:          7993       7942         51          0         20        665
-/+ buffers/cache:       7257        736
Swap:         7054       4046       3008
.
.
.
# ps -ef | grep -i fms | grep -v grep
fms       1095 31710 99 Apr21 ?        53-14:40:49 /opt/adobe/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app -inst -tag _1 -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:_defaultVHost_:::_1
root     31710     1  0 Apr21 ?        00:16:20 ./fmsmaster -silent
fms      31730 31710  0 Apr21 ?        00:45:30 /opt/adobe/fms/fmsedge -edgeports :1935,80 -coreports localhost:19350 -conf /opt/adobe/fms/conf/Server.xml -adaptor _defaultRoot_ -name _defaultRoot__edge1
fms      31733 31710  0 Apr21 ?        00:13:27 /opt/adobe/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app registry -inst registry -tag -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:_defaultVHost_:registry:registry:
root     32065     1  0 Apr21 ?        04:05:33 ./fmsadmin -console -conf ./conf/Server.xml
fms      32160 31710 99 Apr21 ?        68-07:05:01 /opt/adobe/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app -inst -tag _2 -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:_defaultVHost_:::_2
fms      32431 31710 99 Apr29 ?        71-08:13:05 /opt/adobe/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app -inst -tag _0 -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:_defaultVHost_:::_0
.
.
.
Does anyone have any idea about how to get it fixed?
I believe restarting the FMS daemon would "fix" it (actually it would be a simple workarround), but I'm looking for a definitive solution since it's a VOD application and could not be stopped.
Any suggestion is very appreciated.
Thank you!
    This topic has been closed for replies.

    1 reply

    Nikhil_Kalyan
    Participating Frequently
    June 12, 2011

    Hi,

    Thanks for using FMS.

    How much load do you have on the server ? As the admin logs mention, the fmsadmin process is unable to communicate with the fmscore process, seems the core is not responding. I can only think this to happen when the load is too huge that the core is too much blocked to even respond to the admin process.

    Is the fmsadmin command failing only for the getinstancestats api or for all ? If not already done, can you please try any other API to get some of the stream stats?

    Thank you  !