Hello, @jess. Something that has been getting logged since last November is a failure to open a binlog file.
/opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log:[Wed Nov 1 16:51:13.308 2017] [ 1644] WARNING: binlog: replay error at pos=47302678)
/opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log:[Tue Nov 14 08:56:09.523 2017] [ 1642] FATAL: binlog: log open error: failed to open /opt/kaltura/log/sphinx/data/binlog.001: No such
file or directory
…
There are occasional binlog replay errors:
/opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log:[Wed Jan 3 11:51:40.959 2018] [ 1687] WARNING: binlog: replay error at pos=15584534)
/opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log:[Mon Jan 22 22:53:33.162 2018] [ 1668] WARNING: binlog: replay error at pos=5237622)
However, 99.9% of the errors have to do with binlog.001 or binlog.003.
/opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log:[Thu Jul 12 15:56:39.369 2018] [20691] FATAL: binlog: log open error: failed to open /opt/kaltura/log/sphinx/data/binlog.001: No such file or directory
/opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log:[Thu Jul 12 15:57:49.759 2018] [20774] FATAL: binlog: log open error: failed to open /opt/kaltura/log/sphinx/data/binlog.001: No such file or directory
Only binlog-002 exists.
[root@kaltura2 bin]# ls -lrt /opt/kaltura/log/sphinx/data
total 6124
-rw------- 1 kaltura kaltura 6264845 Jun 21 13:15 binlog.002
-rw------- 1 kaltura kaltura 12 Jun 23 07:31 binlog.meta
-rw------- 1 kaltura kaltura 0 Jul 12 16:00 binlog.lock
[root@kaltura2 bin]# file /opt/kaltura/log/sphinx/data/binlog.002
/opt/kaltura/log/sphinx/data/binlog.002: data