|
Troubleshoot live streaming (HTTP)Use the Services window (Windows) or the service window (Linux)
to verify that the Flash Media Server (FMS), Flash Media Administration
Server, and FMSHttpd services are running.
Verify that the request URL is correct. See URLs for publishing and playing live streams over HTTP.
Verify that the server is listening to the port to which
the client is trying to connect. The rootinstall/logs/edge.xx.log
file shows on which ports the server is listening.
By default,
Flash Media Server listens on port 80 and proxies HTTP requests
to Apache HTTP Server on port 8134. Proxying traffic can cause issues
with HTTP streaming. If Flash Media Server is listening on port
80, use port 8134 in the request URL. For example, http://fms.example.com:8134/hds-live/livepkgr/_definst_/liveevent/livestream.f4m.
Otherwise,
configure Apache HTTP Server to listen on port 80 and configure Flash
Media Server not to listen on port 80. See Configure ports for HTTP streaming.
To allow a Flash media player hosted on another web server
to access content from the Flash Media Server web server, copy a
crossdomain.xml file to the rootinstall/webroot directory.
The crossdomain.xml file grants a web client permission to handle
data across multiple domains. For more information, see Cross-domain policy file specification.
In Flash Media Live Encoder, select the Encoding Options
tab, choose Output from the Panel options menu, and verify the following:
The value of FMS URL is rtmp://fms-dns-or-ip/livepkgr.
If you’re testing on the same server as Flash Media Server, you
can use the value localhost for fms-dns-or-ip.
For a single stream, the value of Stream is livestream?adbe-live-event=liveevent.
For adaptive bitrate streaming, the value of Stream is livestream%i?adbe-live-event=liveevent.
Flash
Media Live Encoder uses this value to create unique stream names.
To use another encoder, provide your own unique stream names, for
example, livestream1?adbe-live-event=liveevent, livestream2?adbe-live-event=liveevent.
Check the logs for errors. Flash Media Server logs are located
in the rootinstall/logs folder. The master.xx.log file and
the core.xx.log file show startup failures.
Apache logs are
located in the rootinstall/Apache2.2/logs folder.
Use the Administration Console to verify that the encoder
and the client connected to the livepkgr application.
See Connect to the Administration Console.
Troubleshoot live streaming (RTMP)Use the Services window (Windows) or the service window (Linux)
to verify that the Flash Media Server (FMS) and Flash Media Administration
Server services are running.
If you’re using the Apache HTTP
server, verify that the FMSHttpd service is running.
Use the Administration Console to verify that the encoder
and the client connected to the live application.
See Connect to the Administration Console.
Verify that the server is listening to the port to which
the client is trying to connect. The rootinstall/logs/edge.xx.log
file shows on which ports the server is listening. By default, the
server listens on ports 1935 and 80. If the server is not listening
on port 1935, open the rootinstall/fms.ini file, set ADAPTOR.HOSTPORT =
:1935,80 and restart the server.
In the access.00.log file,
the s-uri and cs-uri-stem fields
indicate the port to which the client attempted to connect. Unless
you specify a port number in the URL, RTMP and RTMFP clients connect
to the server over port 1935 and fall back to port 80.
For
more information, see Port requirements.
In Flash Media Live Encoder, select the Encoding Options
tab, choose Output from the Panel options menu, and verify the following:
The value of FMS URL is rtmp://fms-dns-or-ip/live.
If you’re testing on the same server as Flash Media Server, you
can use the value localhost for fms-dns-or-ip.
For a single stream, the value of Stream is livestream.
For adaptive bitrate streaming, the value of Stream is livestream%i.
Verify that the request URL is correc. See URLs for publishing and playing live streams over RTMP.
The live service does not support DVR recording.
Use
the DVRCast application available from Flash
Media Server Tools. For more information, see the article Using DVRCast with Flash Media Live Encoder in the
Flash Media Server Developer Center.
Check the logs for errors. Flash Media Server logs are located
in the rootinstall/logs folder. The master.xx.log file and
the core.xx.log file show startup failures.
Apache logs are
located in the rootinstall/Apache2.2/logs folder.
Troubleshoot on-demand streaming (HTTP)Note: When
you play a video over HTTP, the client does not connect to the vod
application. Instead, Apache serves the video to the client.
Use the Services window (Windows) or the service window (Linux)
to verify that the Flash Media Server (FMS) and FMSHttpd services
are running.
Verify that the server is listening to the port to which
the client is trying to connect. The rootinstall/logs/edge.xx.log
file shows on which ports the server is listening.
By default,
Flash Media Server proxies requests on port 80 to Apache HTTP Server
on port 8134. Proxying HTTP streaming traffic can cause issues.
If Flash Media Server is listening on port 80, use port 8134 in
the request URL. For example, http://fms.example.com:8134/hds-vod/sample1_1500.f4v.f4m. Otherwise,
configure Apache HTTP Server to listen on port 80 and configure Flash
Media Server not to listen on port 80. See Configure ports for HTTP streaming.
Verify that the request URL is correct. See URLs for playing on-demand streams over HTTP.
By default, Apache streams on-demand media from the rootinstall/webroot/vod
folder. To change this location, see Content storage (HDS and HLS).
Check the logs for errors. Apache logs are located in the
rootinstall/Apache2.2/logs folder.
Troubleshoot on-demand streaming (RTMP)Use the Services window (Windows) or the service window (Linux)
to verify that the Flash Media Server (FMS) and Flash Media Administration
Server services are running.
If you’re using the Apache HTTP
Server, verify that the FMSHttpd service is running.
Use the Administration Console to verify that the client
is connected to the vod application.
See Connect to the Administration Console.
Verify that the server is listening to the port to which
the client is trying to connect. The rootinstall/logs/edge.xx.log
file shows on which ports the server is listening. By default, the
server listens on ports 1935 and 80. If the server is not listening
on port 1935, open the rootinstall/fms.ini file, set ADAPTOR.HOSTPORT =
:1935,80 and restart the server.
In the access.00.log file,
the s-uri and cs-uri-stem fields
indicate the port to which the client attempted to connect. Unless
you specify a port number in the URL, RTMP and RTMFP clients connect
to the server over port 1935 and fall back to port 80.
For
more information, see Port requirements.
Open the Administration Console (rootinstall/tools/fms_adminConsole.htm) and
choose View Applications to verify that the client is connecting
to the vod application. To reset your password, see Reset Administration Console password.
Verify that the request URL is correct. See URLs for playing on-demand media files over RTMP
Do not include the /media folder in the stream URL to play
the file. When you specify a filename, for example, mp4:mymediafile.f4v,
the server is configured to look for /applications/vod/media/mymediafile.f4v.
Verify that the rootinstall/applications/vod directory
is installed. If any files are missing, uninstall and reinstall
the server.
Check the logs. Flash Media Server logs are located in the rootinstall/logs folder.
The master.xx.log file and the core.xx.log file show startup failures.
Troubleshoot multicast streaming (RTMFP)Use the Services window (Windows) or the service window (Linux)
to verify that the Flash Media Server (FMS) and Flash Media Administration
Server services are running.
If you’re using the Apache HTTP
Server, verify that the FMSHttpd service is running.
Use the Administration Console to verify that the encoder
and the client connected to the multicast application.
See Connect to the Administration Console.
Follow the steps in the tutorial Multicast media (RTMFP).
Verify that the correct ports are open. The rootinstall/logs/edge.xx.log
file shows on which ports the server is listening.
Open UDP
1935 and 19350-65535. If the server is located behind a NAT, specify
its public (outside NAT) address in the rootinstall/conf/_defaultRoot_/Adaptor.xml
file in the Adaptor/RTMFP/Core/HostPortList element. See Configure ports.
Check the logs. Flash Media Server logs are located in the rootinstall/logs folder.
The master.xx.log file and the core.xx.log file show startup failures.
|
|
|
