Skip to main content
Participant
January 4, 2016
Question

Core is no longer active (ams5.0)

  • January 4, 2016
  • 1 reply
  • 695 views

Hi ,

Recently i met core is no longer active issue on ams 5.0, below is my log for ams.

I check the discussion, it seems that it was cause by memory increase, and ams seems like have problem to manage it.

my configuration are all default except log config.

Can anyone could help me, how to config it ?

2016-01-04 15:02:01.0,rtmp_audio_slave,172.16.152.118,172.16.152.118|#Fields: datetimex-pidx-statusx-ctxx-comment
2016-01-04 15:02:01.0,rtmp_audio_slave,172.16.152.118,172.16.152.118|2016-01-0415:02:0018096(i)2581223Core (35326) is no longer active.-
2016-01-04 15:02:01.0,rtmp_audio_slave,172.16.152.118,172.16.152.118|2016-01-0415:02:0018096(w)2581256Core (35326) _defaultRoot_:::: experienced 1 failure!-
2016-01-04 15:02:01.0,rtmp_audio_slave,172.16.152.118,172.16.152.118|2016-01-0415:02:0018096(i)2581221Core (2241) started, arguments : -adaptor "_defaultRoot_" -vhost  -app  -inst  -tag  -conf "/opt/adobe/ams/conf/Server.xml" -name "_defaultRoot_::::".-
2016-01-04 15:02:01.0,rtmp_audio_slave,172.16.152.118,172.16.152.118|2016-01-0415:02:0018096(i)2581223Core (35326) is no longer active.-

2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|#Date: 2016-01-04

2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|#Fields: x-eventx-categorydatetimetzx-ctxs-ipx-pidx-cpu-loadx-mem-loadx-adaptorx-vhostx-appx-appinstx-durationx-statusc-ipc-protoc-proto-vers-urics-uri-stemcs-uri-queryc-referrerc-user-agentc-client-idcs-bytessc-bytesc-connect-typex-snamex-sname-queryx-suri-queryx-suri-stemx-surix-file-namex-file-extx-file-sizex-file-lengthx-sposc-sposcs-stream-bytessc-stream-bytesx-service-namex-sc-qos-bytesx-commentx-eidx-sidx-trans-snamex-trans-sname-queryx-trans-file-extx-trans-modex-soffsetx-codec-typex-codecx-pluginx-page-urlx-smax-rec-sizex-smax-rec-durationx-forwarded-for
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|server-startserver2016-01-0415:02:02CST--2241096------------------------------------------------

2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,Start play hich-ra000099

2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|vhost-startvhost2016-01-0415:02:02CST_defaultVHost_-2241096_defaultRoot__defaultVHost_----------------------------------------------
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|app-startapplication2016-01-0415:02:02CSTlive-2241--_defaultRoot__defaultVHost_live_definst_-----------00-------------------------------

2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|#Date: 2016-01-04

2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|#Fields: datetimex-pidx-statusx-ctxx-comment
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2581237Starting admin app on core (2241).-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2581238Core (2241) connecting to admin.-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2581231Core (2241) connected to admin.-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 127.0.0.1:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 192.168.1.111:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 192.168.77.118:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 192.168.77.111:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 172.16.152.118:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 172.16.152.111:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 192.168.200.118:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631174Listener started ( _defaultRoot_ ) : 192.168.200.111:19350 (rtmfp-core)/v4-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2631509Public rtmfp-core addresses for listener _defaultRoot_ are: 127.0.0.1:19350;192.168.1.111:19350;192.168.77.118:19350;192.168.77.111:19350;172.16.152.118:19350;172.16.152.111:19350;192.168.200.118:19350;192.168.200.111:19350-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2581246Core (2241) sending register cmd to edge.-
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-0415:02:022241(i)2581234Core (2241) connection to admin accepted.-
This topic has been closed for replies.

1 reply

BlackrenAuthor
Participant
January 7, 2016

Hi,

Is there anyone could help me about this issue????

is the ams still keeping maintenance ?? or support???

Adobe Employee
January 21, 2016

Hi,

Can you give more details on the issue you are facing?
Is the issue easily reproducible? Which application of AMS are you using?

The logs seem to be after the point that core experienced failures.

Can you send your core logs (logs/core.xx.log) to saikhanATadobeDOTcom

Regards,
Saima

BlackrenAuthor
Participant
January 26, 2016

Hi Saima

I'm using live application on AMS.

Sorry,i do not have core.xx.log anymore, but I still have master.xx.log and admin.xx.log, do you need it?

and could you provide me the mail? I do not know what is saikhanATadobeDOTcom.

BR