Manticore don't show index via SHOW TABLES;

Hi,
I made plain index like https://www.sqlshack.com/manticore-search-a-continuation-of-the-sphinx-search-engine/
and got a problem. Manticore don’t show index via SHOW TABLES;
Can anyone please help me? Thanks a lot for any tips!

OS Win7 x64

I connect like this
MySQL -P9306 -h127.0.0.1
mysql> reload indexes;
Query OK, 0 rows affected (0.00 sec)
mysql> show tables;
Empty set (0.00 sec)

But index files were created in a proper place.
I:\MySQL\Manticore\Data\index\film
04.05.2022 21:29 .
04.05.2022 21:29 …
04.05.2022 21:29 8 144 .new.spa
04.05.2022 21:29 38 731 .new.spd
04.05.2022 21:29 950 .new.spe
04.05.2022 21:29 990 .new.sph
04.05.2022 21:29 16 050 .new.sphi
04.05.2022 21:29 1 749 .new.spi
04.05.2022 21:29 128 .new.spm
04.05.2022 21:29 340 .new.spp
04.05.2022 21:29 5 256 .new.spt

Index building command line
C:/Manticore/bin/indexer --config “C:\Manticore\manticore.conf_actor.in” --all --rotate
generated this output:
Manticore 4.2.0 15e927b28@211223 release
Copyright (c) 2001-2016, Andrew Aksyonoff
Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
Copyright (c) 2017-2021, Manticore Software LTD (https://manticoresearch.com)
using config file ‘C:\Manticore\manticore.conf_actor.in’…
indexing index ‘film’…
collected 1000 docs, 0.0 MB
creating lookup: 1.0 Kdocs, 100.0% done
sorted 0.0 Mhits, 100.0% done
total 1000 docs, 93842 bytes
total 0.048 sec, 1918588 bytes/sec, 20444.88 docs/sec
total 3 reads, 0.000 sec, 16.6 kb/call avg, 0.0 msec/call avg
total 13 writes, 0.000 sec, 9.2 kb/call avg, 0.0 msec/call avg
rotating indices: successfully sent SIGHUP to searchd (pid=12820).
Manticore version 4.2.0 15e927b28@211223 release

Searchd.log:
[Wed May 4 21:29:40.626 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 21:29:40.626 2022] [7484] rotating finished

My config file:
searchd {
listen = 127.0.0.1:9312
listen = 127.0.0.1:9306:mysql
listen = 127.0.0.1:9308:http
log = i:/MySQL/Manticore/log/searchd.log
query_log = i:/MySQL/Manticore/log/query.log
pid_file = i:/MySQL/Manticore/run/searchd.pid
data_dir = i:/MySQL/Manticore/data
query_log_format = sphinxql
seamless_rotate = 1
preopen_indexes = 1
binlog_path = i:/MySQL/Manticore/data/binlog
mysql_version_string = 8.0.29
}
source base
{
type = mysql
sql_host = localhost
sql_user = admin
sql_pass = mysql
sql_db = sakila
sql_port = 3306
}

source film: base
{
sql_query = select film_id, description from film;
sql_attr_uint = film_id
}
index film {
type = plain
morphology = stem_en
stopwords = C:/Manticore/share/stopwords/en
min_word_len = 3
source = film
path = i:/MySQL/Manticore/data/index/film/
}

could you check startup log of a daemon as if demon loads 0 indexes on start it will not rotate or pick index after

Today log seems to be ok…
[Wed May 4 20:37:12.026 2022] [6980] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=1)
[Wed May 4 20:37:52.881 2022] [6980] shutdown daemon version ‘4.2.0 15e927b28@211223 release’ …
[Wed May 4 20:37:52.881 2022] [6980] shutdown complete
[Wed May 4 20:38:20.631 2022] [14540] starting daemon version ‘4.2.0 15e927b28@211223 release’ …
[Wed May 4 20:38:20.631 2022] [14540] listening on 127.0.0.1:9312 for sphinx and http(s)
[Wed May 4 20:38:20.631 2022] [14540] listening on 127.0.0.1:9306 for mysql
[Wed May 4 20:38:20.631 2022] [14540] listening on 127.0.0.1:9308 for sphinx and http(s)
[Wed May 4 20:38:20.653 2022] [2280] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:38:20.653 2022] [2280] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:38:20.653 2022] [2280] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:38:20.653 2022] [2280] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:38:20.653 2022] [2280] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:38:20.653 2022] [2280] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:38:20.653 2022] [2280] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:38:20.653 2022] [2280] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:38:20.653 2022] [2280] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:38:20.653 2022] [2280] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:38:20.653 2022] [2280] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:38:20.653 2022] [2280] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:38:20.653 2022] [2280] binlog: finished replaying total 4 in 0.000 sec
[Wed May 4 20:38:20.655 2022] [14540] accepting connections
[Wed May 4 20:38:20.655 2022] [15340] prereading 0 indexes
[Wed May 4 20:38:20.655 2022] [15340] prereaded 0 indexes in 0.000 sec
[Wed May 4 20:43:18.363 2022] [14540] shutdown daemon version ‘4.2.0 15e927b28@211223 release’ …
[Wed May 4 20:43:18.363 2022] [14540] shutdown complete
[Wed May 4 20:43:32.149 2022] [3276] starting daemon version ‘4.2.0 15e927b28@211223 release’ …
[Wed May 4 20:43:32.149 2022] [3276] listening on 127.0.0.1:9312 for sphinx and http(s)
[Wed May 4 20:43:32.150 2022] [3276] listening on 127.0.0.1:9306 for mysql
[Wed May 4 20:43:32.150 2022] [3276] listening on 127.0.0.1:9308 for sphinx and http(s)
[Wed May 4 20:43:32.171 2022] [1460] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:43:32.171 2022] [1460] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:43:32.171 2022] [1460] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:43:32.171 2022] [1460] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:43:32.171 2022] [1460] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:43:32.171 2022] [1460] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:43:32.171 2022] [1460] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:43:32.171 2022] [1460] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:43:32.171 2022] [1460] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:43:32.171 2022] [1460] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:43:32.172 2022] [1460] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:43:32.172 2022] [1460] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:43:32.172 2022] [1460] binlog: replaying log i:/MySQL/Manticore/data/binlog/binlog.001
[Wed May 4 20:43:32.172 2022] [1460] binlog: replay stats: 0 commits; 0 updates, 0 reconfigure; 0 pq-add; 0 pq-delete; 0 pq-add-delete, 0 indexes
[Wed May 4 20:43:32.172 2022] [1460] binlog: finished replaying i:/MySQL/Manticore/data/binlog/binlog.001; 0.0 MB in 0.000 sec
[Wed May 4 20:43:32.172 2022] [1460] binlog: finished replaying total 5 in 0.000 sec
[Wed May 4 20:43:32.173 2022] [7484] prereading 0 indexes
[Wed May 4 20:43:32.173 2022] [7484] prereaded 0 indexes in 0.000 sec
[Wed May 4 20:43:32.173 2022] [3276] accepting connections
[Wed May 4 20:43:37.473 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 20:43:37.473 2022] [6380] rotating finished
[Wed May 4 20:48:10.353 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 20:48:10.354 2022] [6380] rotating finished
[Wed May 4 20:52:22.104 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 20:52:22.104 2022] [7868] rotating finished
[Wed May 4 20:57:45.400 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 20:57:45.400 2022] [6380] Config changed (read 366 chars)
[Wed May 4 20:57:45.400 2022] [6380] WARNING: No indexes found in config came to rotation. Abort reloading
[Wed May 4 20:57:45.400 2022] [6380] rotating finished
[Wed May 4 20:58:24.401 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 20:58:24.402 2022] [7484] Config changed (read 366 chars)
[Wed May 4 20:58:24.402 2022] [7484] WARNING: No indexes found in config came to rotation. Abort reloading
[Wed May 4 20:58:24.402 2022] [7484] rotating finished
[Wed May 4 20:59:20.214 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 20:59:20.214 2022] [1460] rotating finished
[Wed May 4 20:59:29.914 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 20:59:29.914 2022] [6380] Config changed (read 366 chars)
[Wed May 4 20:59:29.914 2022] [6380] WARNING: No indexes found in config came to rotation. Abort reloading
[Wed May 4 20:59:29.915 2022] [6380] rotating finished
[Wed May 4 21:29:40.626 2022] [3276] caught SIGHUP (seamless=0, in_rotate=0, need_rotate=0)
[Wed May 4 21:29:40.626 2022] [7484] rotating finished

seems index definition is not in the config

Oh, I thought that index will be find by daemon automatically. Initailly I started daemon only with searchd section in config. If I start daemon with whole config its crashes on start with no errors in log

daemon can not load index that it could not see at startup
you could issue RELOAD INDEXES as described Manticore Search Manual: Data creation and modification > Adding data from external storages > Rotating a table

however it might be better to investigate why daemon got crashed on startup as it could crash the same way on index load

Could you check your index data with indextool like indextool.exe -c your.conf index_name

However to issue check you need to index your data with indexes without rotate option as rotate is only for index that was already loaded by daemon but not for a new index.

I am stupid like a staff… It was data_dir option again. After erasing data_dir from whole config daemon didn’t crash and index appeared.

c:\Manticore\bin\indextool.exe -c c:/Manticore/manticore.conf_actor.in --check film
using config file ‘c:/Manticore/manticore.conf_actor.in’…
checking index ‘film’…
checking schema…
checking dictionary…
checking data…
checking rows…
checking attribute blocks index…
checking kill-list…
checking dead row map…
checking doc-id lookup…
check passed, 0.0 sec elapsed

Thanks a lot!!!