RTMP Streams Push to Server but Cannot Play via RTMP and/or HLS

RTMP Streams Push to Server but Cannot Play via RTMP and/or HLS

Support ForumCategory: Installation and Basic OperationRTMP Streams Push to Server but Cannot Play via RTMP and/or HLS
solidbit asked 5 years ago
Recently upgraded to Evostream 2. Prior settings and configuration still applied.When evostream is running via console, every thing works fine. I can push an RTMP stream, server rebroadcasts it, HLS files are generated and play. However, if i\’m not using the console mode, i.e. starting it up as normal, then the server receives RTMP streams, but will not rebroadcast them. Additionally the HLS/DASH streams are not generated.Any guidance?

Question Tags:


6 Answers
solidbit answered 5 years ago
I do have a current Evostream v.2 license.
erika Staff answered 5 years ago
Hi solidbit , There should be no difference in running via console or daemon except for the terminal logs.. Can you send listConfig and listStreams and paste the output here?   Thank you!
solidbit answered 5 years ago
Below is the output when running “start” vs “start_console”. Again, “start_console” works without fault, “start” allows the software pushing the stream to connect, but that’s it. Both are being run on the same systems, no changes to the streaming setup are made other than changing the startup command. Please advise. #service evostreamms start listConfig Command entered successfully! Run-time configuration dash: [] hds: [] hls: — configId: 1 groupName: moriahhls localStreamName: moriah1080p30 status: current: description: Waiting for stream uniqueStreamId: 0 targetFolder: /var/evo-webroot/moriahhls/moriah1080p30 — configId: 2 groupName: moriahhls localStreamName: moriah720p30 status: current: description: Waiting for stream uniqueStreamId: 0 targetFolder: /var/evo-webroot/moriahhls/moriah720p30 — configId: 3 groupName: moriahhls localStreamName: moriah480p30 status: current: description: Waiting for stream uniqueStreamId: 0 targetFolder: /var/evo-webroot/moriahhls/moriah480p30 metalistener: [] mss: [] process: [] pull: [] push: [] record: [] webrtc: [] listStreams Command entered successfully! Available streams — audio: bytesCount: 731377 codec: AAAC farIp: 69.61.168.159 name: moriah720p30 nearIp: 50.28.10.87 outStreamsUniqueIds: processId: 2695 processType: edge type: INR uniqueId: 11574936862722 video: bytesCount: 11281418 codec: VH264 — audio: bytesCount: 719155 codec: AAAC farIp: 69.61.168.159 name: moriah480p30 nearIp: 50.28.10.87 outStreamsUniqueIds: processId: 2696 processType: edge type: INR uniqueId: 11579231830018 video: bytesCount: 5085157 codec: VH264 — audio: bytesCount: 1113353 codec: AAAC farIp: 69.61.168.159 name: moriah1080p30 nearIp: 50.28.10.87 outStreamsUniqueIds: processId: 2694 processType: edge type: INR uniqueId: 11570641895426 video: bytesCount: 23460989 codec: VH264 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- #service evostreamms start_console listConfig Command entered successfully! Run-time configuration dash: [] hds: [] hls: — configId: 1 groupName: moriahhls localStreamName: moriah1080p30 status: current: description: Streaming uniqueStreamId: 3 targetFolder: /var/evo-webroot/moriahhls/moriah1080p30 — configId: 2 groupName: moriahhls localStreamName: moriah720p30 status: current: description: Streaming uniqueStreamId: 4 targetFolder: /var/evo-webroot/moriahhls/moriah720p30 — configId: 3 groupName: moriahhls localStreamName: moriah480p30 status: current: description: Streaming uniqueStreamId: 6 targetFolder: /var/evo-webroot/moriahhls/moriah480p30 metalistener: [] mss: [] process: [] pull: [] push: [] record: [] webrtc: [] listStreams Command entered successfully! Available streams — audio: bytesCount: 3149274 codec: AAAC farIp: 69.61.168.159 name: moriah1080p30 nearIp: 50.28.10.87 outStreamsUniqueIds: — 3 processId: 4597 processType: origin type: INR uniqueId: 1 video: bytesCount: 66256845 codec: VH264 — audio: bytesCount: 2092610 codec: AAAC farIp: 69.61.168.159 name: moriah720p30 nearIp: 50.28.10.87 outStreamsUniqueIds: — 4 processId: 4597 processType: origin type: INR uniqueId: 2 video: bytesCount: 32651422 codec: VH264 — audio: bytesCount: 3149274 codec: AAAC farIp: inStreamUniqueId: 1 name: moriah1080p30 nearIp: processId: 4597 processType: origin type: OFHLS uniqueId: 3 video: bytesCount: 66256845 codec: VH264 — audio: bytesCount: 2092610 codec: AAAC farIp: inStreamUniqueId: 2 name: moriah720p30 nearIp: processId: 4597 processType: origin type: OFHLS uniqueId: 4 video: bytesCount: 32651422 codec: VH264 — audio: bytesCount: 2079010 codec: AAAC farIp: 69.61.168.159 name: moriah480p30 nearIp: 50.28.10.87 outStreamsUniqueIds: — 6 processId: 4597 processType: origin type: INR uniqueId: 5 video: bytesCount: 14700487 codec: VH264 — audio: bytesCount: 2079010 codec: AAAC farIp: inStreamUniqueId: 5 name: moriah480p30 nearIp: processId: 4597 processType: origin type: OFHLS uniqueId: 6 video: bytesCount: 14700487 codec: VH264
erika Staff answered 5 years ago
Hi solidbit,   Based on your logs for service evostreamms start: For createHLSstream: description: Waiting for stream (the localstreamname cannot be found) But in your listStreams, the localstreamnames called for createHLS are present.   May I know how you ingest your source and the createHLSStream command you sent? Also, can you try to restart EMS and check again?    Thank you!
solidbit answered 5 years ago
I’ve restarted Evostream multiple times, still same issue is present. In both cases (running start vs running start_console), I’m pushing an RTMP stream in on port 1935 via Telestream’s Wirecast software. I have authentication setup and have validated all passwords and user names for the pushed-in stream. The streaming setup with Wirecast remains the same through all repeated tests. You are correct in seeing that the server states that it is waiting for stream when running “start”. That is the issue. Both cases wirecast shows that it is connecting and streaming, server shows inbound traffic and activity occurring, but the Evostream server app doesn’t pickup and recognize the stream under “start” only works under “start_console”. I ran a couple hour long stream last Saturday, using “start_console”, and it ran without fault. Again, after successfully streaming we immediately attempted to start up the server via “start”, everything started up, Wirecast showed it connecting, but no local stream was recognized. Thoughts on where to dig into next?

Offcanvas

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