• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Connecting to the admin console restarts multicast publishing

New Here ,
Sep 05, 2017 Sep 05, 2017

Copy link to clipboard

Copied

Hi,

We have a serious issue

We recently noticed that some log files are showing that when we connect to a server with the admin (Flash) console our multicast streams are republished.

Also Core App seems to restart.

We are running AMS Professional 5.0.14 r4006

CORE.00

#Date: 2017-09-05

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

2017-09-05    10:49:41    12060    (i)2581237    Starting admin app on core (12060).    -

2017-09-05    10:49:41    12060    (i)2581238    Core (12060) connecting to admin.    -

2017-09-05    10:49:41    12060    (i)2581231    Core (12060) connected to admin.    -

2017-09-05    10:49:41    12060    (i)2581234    Core (12060) connection to admin accepted.    -

2017-09-05    10:49:41    12060    (i)2631174    Listener started ( _defaultRoot_ ) : 10.xx.xx.xx:19351 (rtmfp-core)/v4    -

2017-09-05    10:49:41    12060    (i)2631174    Listener started ( _defaultRoot_ ) : 10.xx.xx.xx:19351 (rtmfp-core)/v4    -

2017-09-05    10:49:41    12060    (i)2631174    Listener started ( _defaultRoot_ ) : 127.0.0.1:19351 (rtmfp-core)/v4    -

2017-09-05    10:49:41    12060    (i)2631509    Public rtmfp-core addresses for listener _defaultRoot_ are: 10.xx.xx.xx:19351;10.xx.xx.xx:19351;127.0.0.1:19351    -

2017-09-05    10:49:41    12060    (i)2581246    Core (12060) sending register cmd to edge.    -

2017-09-05    10:49:41    12060    (i)2631521    Successfully bound and configured RTMFP native multicast socket for addr: 10.xx.xx.0:30000. Specific source addr: .     -

2017-09-05    10:49:41    12060    (i)2631521    Successfully bound and configured RTMFP native multicast socket for addr: 10.xx.xx.1:30000. Specific source addr: .     -

ACCESS.00

#Date: 2017-09-05

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    x-sprotection-ver

server-start    server    2017-09-05    10:49:40    Eastern Daylight Time    -    -    12060    0    10    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -

vhost-start    vhost    2017-09-05    10:49:41    Eastern Daylight Time    _defaultVHost_    -    12060    0    10    _defaultRoot_    _defaultVHost_    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -

app-start    application    2017-09-05    10:49:41    Eastern Daylight Time    multicast    -    12060    -    -    _defaultRoot_    _defaultVHost_    multicast    _definst_    -    -    -    -    -    -    -    -    -    -    -    0    0    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -    -

ADMIN.00

2017-09-05    10:49:40    1216    (i)2581242    Core (11312) disconnected : _defaultRoot_:_defaultVHost_:::_1.    -

2017-09-05    10:49:41    1216    (i)2581241    Connection to admin received.    -

2017-09-05    10:49:41    1216    (i)2581243    Connection from core 12060 received.    -

2017-09-05    10:49:41    1216    (i)2581244    Connection from core 12060 accepted.    -

MASTER.00

2017-09-05    10:49:40    1148    (i)2581223    Core (11312) is no longer active.    -

2017-09-05    10:49:40    1148    (w)2581256    Core (11312) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure!    -

2017-09-05    10:49:40    1148    (i)2581221    Core (12060) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "D:\Adobe Media Server 5\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1".    -

2017-09-05    10:49:41    1148    (i)2581223    Core (11312) is no longer active.    -

I confirm that the server was running before 10:49:41 (streams were pushed to mutlicast groups)

Thank you.

Views

183

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

New Here , Sep 07, 2017 Sep 07, 2017

Hi,

I marked it as resolved because the problem was caused by the push app (WSE) which was republishing all the stream as long as one of them was being stopped and restarted.

So we thought that AMS restarted because the multicast app, as there was no stream incoming for one second, killed the instance, and then, when the streams were back it restarted.

So AMS is not the reason of our problem here.

Votes

Translate

Translate
New Here ,
Sep 07, 2017 Sep 07, 2017

Copy link to clipboard

Copied

LATEST

Hi,

I marked it as resolved because the problem was caused by the push app (WSE) which was republishing all the stream as long as one of them was being stopped and restarted.

So we thought that AMS restarted because the multicast app, as there was no stream incoming for one second, killed the instance, and then, when the streams were back it restarted.

So AMS is not the reason of our problem here.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines