|AV-Sync might be broken errors
|Page 1 of 1|
|Author:||thekingofspain [ Sun Feb 13, 2022 1:01 pm ]|
|Post subject:||AV-Sync might be broken errors|
I am on a very static LinHES backend/front end server and have run into some errors as of late out of the blue.
Diving into this, the Front end logs are huge
Two issues jump out:
For the corrupted recordedseek table, i thought I fixed the issue running some mysql correct commands but never rechecked the logs to verify and the disk space warning never appeared again I thought all was good, but it was not. Here is the fix that removed this error from reoccurring:
mysql> Rename table recordedseek to recordedseek_bad;
mysql> Create table recordedseek like recordedseek_bad;
This fixed the decoded issue with fast forwarding and the logs.
However when testing the fast forwarding, I am still seeing the follow errors occuring about 30 times per second on video playback.
2022-02-13 12:13:48.869416 W AFD: Audio -1507 ms behind video but already 220 video frames queued. AV-Sync might be broken.
I am not noticing any audio video sync issues at all. 1.5s lag seems something anyone would notice.
Any thoughts on how to correct this issue or supress the the error from the logs since its filling them up such that a previous days frontend logs can not be view in vi because the file is bigger than /tmp (a first in my entire 35 years of using unix/linux btw).
ls -l /var/log/2022-02-12
-rw-r--r-- 1 root root 18076 Feb 12 23:50 mythtvquad_cron.log
-rw-r--r-- 1 root root 35394884 Feb 12 23:52 mythtvquad_frontend.log
-rw-r--r-- 1 root root 121193 Feb 12 23:58 mythtvquad_lighttpd.log
-rw-r--r-- 1 root root 30013 Feb 12 23:50 mythtvquad_maillog.log
-rw-r--r-- 1 root root 35732451 Feb 12 23:58 mythtvquad_messages.log
-rw-r--r-- 1 root root 6179110 Feb 12 23:58 mythtvquad_mythbackend.log
-rw-r--r-- 1 root root 68783 Feb 12 22:10 mythtvquad_mythcommflag.log
-rw-r--r-- 1 root root 464 Feb 12 19:27 mythtvquad_mythexpress.log
-rw-r--r-- 1 root root 3075 Feb 12 00:00 mythtvquad_mythfilldatabase.log
-rw-r--r-- 1 root root 42404092 Feb 12 23:52 mythtvquad_mythfrontend.log
-rw-r--r-- 1 root root 37308 Feb 12 21:59 mythtvquad_mythmetadatalookup.log
-rw-r--r-- 1 root root 84494 Feb 12 23:53 mythtvquad_myth_mtc.log
-rw-r--r-- 1 root root 379881 Feb 12 23:52 mythtvquad_mythpreviewgen.log
-rw-r--r-- 1 root root 3456 Feb 12 23:55 mythtvquad_rsyslogd.log
-rw-r--r-- 1 root root 608320 Feb 12 23:58 mythtvquad_sudo.log
-rw-r--r-- 1 root root 2390 Feb 12 22:42 mythtvquad_su.log
-rw-r--r-- 1 root root 13680 Feb 12 23:58 mythtvquad_xfs_defrag.log
|Author:||thekingofspain [ Thu Feb 17, 2022 12:05 am ]|
|Post subject:||Re: AV-Sync might be broken errors|
The mysql problem reappeared again, but I think they might be solved again..
For mysql, the table repair was failed because it could not create a temp file. The old temp file from the previous recordedseeked.tmp file was still in the mysql table directory. Deleting the file allowed the new recordedseek table to be repaired.
The frontend log problem seems to be corrected by changing the Playback > Advanced Playback > Audio Read Ahead value back to the default value of 100. Previously it had been set to 2000. I set it to 3000 and the log message jumped from 1xyz ms to 2xyz ms. With the default value of 100, no error messages are being logged currently. I think I touched this value a few years ago to tweak some playback issues which were eventually tracked down to a silent failing drive.
My speculation is that the huge logs allong with the n years of rows in the recordedseek table caused the intial failure. Once it triggered there was never enought disk space to recover fully.
|Page 1 of 1||All times are UTC - 6 hours|
|Powered by phpBB® Forum Software © phpBB Group