EMS Ver. 2.0 – pushPullSetup.xml — Issue: – Crashing EMS Streams?

EMS Ver. 2.0 – pushPullSetup.xml — Issue: – Crashing EMS Streams?

Support ForumCategory: Installation and Basic OperationEMS Ver. 2.0 – pushPullSetup.xml — Issue: – Crashing EMS Streams?
App asked 5 years ago
Hello, After trying for weeks, I now see it’s the “pushPullSetup.xml” file causing the issue of “NO STREAM WRITTEN To: autoDASH=, autoHLS=, autoHDS= or autoMSS=. I see the Stream coming in but not going out! Now, if I delete the “pushPullSetup.xml” file and restart EMS, everything will work fine “JUST ONCE” until that streams end. To get it to work again, I have to “rinse and repeat” the removal of the “pushPullSetup.xml” & Restart EMS. Can you tell me why “pushPullSetup.xml” file gets corrupt and how to correct? Thanks App



6 Answers
erika Staff answered 5 years ago
Hi App, Your issue is the corrupted pushpullsetup or crashing of EMS? For the EMS crash, i saw the error: 
/thelib/src/netio/epoll/tcpacceptor.cpp:71 Unable to bind on address: tcp://127.0.0.1:1112; Error was: (98) Address already in use

that's why I told you to kill the process using port 1112.


The issue of corrupted pushpullsetup is a different one.
Can you please send the logs at salesupport@evostream.com?
We will investigate what happened to your EMS.    Thank you.
App answered 5 years ago
In the post above, It was changed to:                 — CLI acceptors
                {
                    ip=”127.0.0.1″,
                    –port=1112,
                    port=1121,
                    protocol=”inboundJsonCli”,
                    useLengthPadding=true
                },   I showed you the command line: [root@server1 ~]# lsof -i:1121
COMMAND     PID       USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
evostream 20536 evostreamd    5u  IPv4 146186      0t0  TCP localhost:rmpp (LISTEN)
evostream 20564 evostreamd    5u  IPv4 146186      0t0  TCP localhost:rmpp (LISTEN)
[root@server1 ~]# kill -9 $(lsof -t -i:1121)
[root@server1 ~]# kill -9 $(lsof -t -i:1121)
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec][root@server1 ~]# I also posted two images of the UI Dashboard: IT Still Don’t Work With That Port Change…  
App answered 5 years ago
I’VE BEEN TRYING TO GET THIS TO WORK SINCE I PURCHASED EMS 2.0 Perpetual License . Can I get PAID SUPPORT or Faster turn around to get this up and running? Date Invoice # Due Date October 5, 2017 6712 10/05/2017
App answered 5 years ago
Of Course after the -9 kill call I “EMS” was started again.
erika Staff answered 5 years ago
Hi App, You can email salesupport@evostream.com for the paid support request.  Also, please use Google Chrome if you are using the UI for playback, The players in UI works only for Chrome browser.    Thank you.

Offcanvas

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.