-
Notifications
You must be signed in to change notification settings - Fork 972
How to find errors on AVideo Platform
To effectively manage the AVideo Platform, it is essential to receive feedback about the server's performance and any errors that may be occurring.
AVideo Platform and Encoder store activity and error logs in /your/path/to/AVideo/videos/avideo.log
and /your/path/to/AVideo/Encoder/videos/avideo.log
, respectively.
To monitor AVideo Platform service responses and activities, use the following command:
tail -n 200 -f /var/www/html/AVideo/videos/avideo.log
In addition to the AVideo logs, it may also be necessary to check the logs of the operating system, such as Apache error, Apache log, mail log, etc.
Checking the Apache log can be an important step in troubleshooting installation issues with AVideo. It provides valuable information about errors and warnings that can help you diagnose and resolve the problem. By following these simple steps, you can quickly check the Apache log and get your AVideo installation back up and running in no time.
- First, log in to your server using SSH or a terminal window.
- Navigate to the Apache logs directory. This directory may vary depending on your server setup, but it is usually located at /var/log/apache2 or /var/log/httpd.
- Look for the error log file. This is typically named error.log or error_log.
- Open the error log file in a text editor or viewer. You may need root or administrator permissions to do so.
- Look for any errors or warnings related to AVideo. These errors will usually include information about what went wrong and where the issue occurred.
- Once you have identified the issue, you can take steps to resolve it.
If you're encountering problems during the video encoding process, it is imperative to inspect both the encoder and streamer logs, as these logs provide critical information about the operations taking place behind the scenes.
The video encoding process comprises two primary steps:
- File Submission: This step involves the initial communication between the streamer and encoder when you submit a file for encoding.
- File Transfer: After encoding, the file gets transferred from the encoder to the desired destination.
To diagnose issues arising during these steps, follow these guidelines:
By inspecting the logs during file submission, you can identify any communication problems between the streamer and encoder.
-
Streamer Log and Encoder Log:
tail -n 200 -f /your/path/to/AVideo/videos/avideo.log /your/path/to/AVideo/Encoder/videos/avideo.log
Keep these logs open and active. Now, try submitting a file for encoding. Monitor both logs for any error messages or anomalies that pop up during the file submission process.
Once the encoding is finished, the encoded video file gets transferred to its intended location. To ensure that this step is completed without issues:
-
Streamer Log and Encoder Log:
tail -n 200 -f /your/path/to/AVideo/videos/avideo.log /your/path/to/AVideo/Encoder/videos/avideo.log
Again, monitor both logs for any error messages or issues that might appear during the file transfer process after encoding.
If you're having issues playing a video, refer to the following guide: https://github.com/WWBN/AVideo/wiki/What-to-do-if-your-video-does-not-play
For live streams, refer to the following guide: https://github.com/WWBN/AVideo/wiki/What-to-do-if-your-live-does-not-play
To check if your Nginx RTMP server is running, you can follow these steps:
- Access the Nginx URL and port in your web browser. For example:
https://mysite.com:8443
. - If you see the Nginx page, it means your server is running.
- To check your stats page, access the following URL:
https://mysite.com:8443/stats
. - If the stats page opens successfully, it confirms that your Nginx RTMP server is running correctly.
If any of these pages do not open, you can try the following troubleshooting steps:
- Restart your Nginx server. You can refer to the following guide for instructions on how to restart Nginx: How to Restart Nginx.
- Review your Nginx installation to ensure that it is properly configured. You can refer to the following guide for guidance on setting up your own stream server using Nginx: Set up my own Stream Server.
If you're experiencing issues with your interactive functionality, this may be due to JavaScript errors or conflicts. Refer to the following guides for diagnosing and resolving JavaScript issues:
-
To diagnose JavaScript issues in different browsers: https://github.com/WWBN/AVideo/wiki/Using-Your-Browser-Console-to-Diagnose-JavaScript-Errors
-
To find errors on JavaScript or Ajax requests: https://github.com/WWBN/AVideo/wiki/Check-Ajax-answer