-
Notifications
You must be signed in to change notification settings - Fork 639
Troubleshooting
Please get Thread Dump by using the following REST methods:
GET http://AMS_URL:5080/rest/threads-info
GET http://AMS_URL:5080/rest/thread-dump-json
GET http://AMS_URL:5080/rest/thread-dump-raw
You can easily call these methods via the browser address bar since all of them are GET methods.
Check whether there exists a dead-locked-thread by the threads-info
method.
Check blocked time of the threads got by thread-dump-json
method.
For more details, analyze threads by loading the raw dump file by the VisualVM tool.
Please get Memory Dump by using the following REST method:
GET http://AMS_URL:5080/rest/heap-dump
You can easily call this method via the browser address bar since all of it is a GET method.
Load the created heapdump.hprof file bt the VisualVM tool and make memory analyze.
Check for any leaks. You can also use Eclipse Memory Analyzer Tool tool to find leaks automatically.
Your device may not have the necessary h264 codec. Check your device codec compatibility from: https://mozilla.github.io/webrtc-landing/pc_test_no_h264.html
This issue( "NoStreamExist") due to your sending stream resolution is not enough for the configured Adaptive Bitrate values.
In WebRTC side, you can check your camera resolution capacity in below links: https://webrtchacks.github.io/WebRTC-Camera-Resolution/ https://webrtc.github.io/samples/src/content/getusermedia/resolution/
In RTMP side, you need to check your Video Resolution(Output Resolution) setting values in OBS Video section as an image -> https://imgur.com/a/JlVv04h Your Output resolution size should be high than your Adaptive Streaming setting.
If you want to stream 720HD, you need to provide the requirements at least 720p.
Be sure about video resolution in your adaptive settings is equals and less than the stream you send.
This is about browsers' policy rules. https://developers.google.com/web/updates/2017/09/autoplay-policy-changes https://developer.mozilla.org/en-US/docs/Web/Media/Autoplay_guide#The_autoplay_feature_policy
- Introduction
- Quick Start
- Installation
- Publishing Live Streams
- Playing Live Streams
- Conference Call
- Peer to Peer Call
- Adaptive Bitrate(Multi-Bitrate) Streaming
- Data Channel
- Video on Demand Streaming
- Simulcasting to Social Media Channels
- Clustering & Scaling
- Monitor Ant Media Servers with Apache Kafka and Grafana
- WebRTC SDKs
- Security
- Integration with your Project
- Advanced
- WebRTC Load Testing
- TURN Servers
- AWS Wavelength Deployment
- Multi-Tenancy Support
- Monitor Ant Media Server with Datadog
- Clustering in Alibaba
- Playlist
- Kubernetes
- Time based One Time Password
- Kubernetes Autoscaling
- Kubernetes Ingress
- How to Install Ant Media Server on EKS
- Release Tests
- Spaceport Volumetric Video
- WebRTC Viewers Info
- Webhook Authentication for Publishing Streams
- Recording Streams
- How to Update Ant Media Server with Cloudformation
- How to Install Ant Media Server on GKE
- Ant Media Server on Docker Swarm
- Developer Quick Start
- Recording HLS, MP4 and how to recover
- Re-streaming update
- Git Branching
- UML Diagrams