Copy link to clipboard
Copied
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: date | time | x-pid | x-status | x-ctx | x-comment |
2016-01-04 15:02:01.0,rtmp_audio_slave,172.16.152.118,172.16.152.118|2016-01-04 | 15:02:00 | 18096 | (i)2581223 | Core (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-04 | 15:02:00 | 18096 | (w)2581256 | Core (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-04 | 15:02:00 | 18096 | (i)2581221 | Core (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-04 | 15:02:00 | 18096 | (i)2581223 | Core (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-event | x-category | date | time | tz | x-ctx | s-ip | x-pid | x-cpu-load | x-mem-load | x-adaptor | x-vhost | x-app | x-appinst | x-duration | x-status | c-ip | c-proto | c-proto-ver | s-uri | cs-uri-stem | cs-uri-query | c-referrer | c-user-agent | c-client-id | cs-bytes | sc-bytes | c-connect-type | x-sname | x-sname-query | x-suri-query | x-suri-stem | x-suri | x-file-name | x-file-ext | x-file-size | x-file-length | x-spos | c-spos | cs-stream-bytes | sc-stream-bytes | x-service-name | x-sc-qos-bytes | x-comment | x-eid | x-sid | x-trans-sname | x-trans-sname-query | x-trans-file-ext | x-trans-mode | x-soffset | x-codec-type | x-codec | x-plugin | x-page-url | x-smax-rec-size | x-smax-rec-duration | x-forwarded-for |
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|server-start | server | 2016-01-04 | 15:02:02 | CST | - | - | 2241 | 0 | 96 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
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-start | vhost | 2016-01-04 | 15:02:02 | CST | _defaultVHost_ | - | 2241 | 0 | 96 | _defaultRoot_ | _defaultVHost_ | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|app-start | application | 2016-01-04 | 15:02:02 | CST | live | - | 2241 | - | - | _defaultRoot_ | _defaultVHost_ | live | _definst_ | - | - | - | - | - | - | - | - | - | - | - | 0 | 0 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
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: date | time | x-pid | x-status | x-ctx | x-comment |
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-04 | 15:02:02 | 2241 | (i)2581237 | Starting 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-04 | 15:02:02 | 2241 | (i)2581238 | Core (2241) connecting to admin. | - |
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-04 | 15:02:02 | 2241 | (i)2581231 | Core (2241) connected to admin. | - |
2016-01-04 15:02:02.0,rtmp_audio_slave,172.16.152.118,172.16.152.111|2016-01-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631174 | Listener 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-04 | 15:02:02 | 2241 | (i)2631509 | Public 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-04 | 15:02:02 | 2241 | (i)2581246 | Core (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-04 | 15:02:02 | 2241 | (i)2581234 | Core (2241) connection to admin accepted. | - |
Copy link to clipboard
Copied
Hi,
Is there anyone could help me about this issue????
is the ams still keeping maintenance ?? or support???
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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