New install fails to configure

General Discussions - English
1

Trying a new install of Manticore Search 5.0.2-220530 on Ubuntu 22.04.1 LTS.

The install goes fine until it’s time for the configuration. Then, I get this:

Job for manticore.service failed because the control process exited with error code.
See "systemctl status manticore.service" and "journalctl -xeu manticore.service" for details.
invoke-rc.d: initscript manticore, action "start" failed.
● manticore.service - Manticore Search Engine
     Loaded: loaded (/run/systemd/generator.early/manticore.service; generated)
     Active: activating (auto-restart) (Result: exit-code) since Mon 2023-01-02 22:16:12 UTC; 16ms ago
    Process: 1136844 ExecStartPre=/usr/bin/install -omanticore -gmanticore -m755 -d /var/run/manticore (code=exited, status=0/SUCCESS)
    Process: 1136849 ExecStart=/usr/bin/searchd --config /etc/manticoresearch/manticore.conf $_ADDITIONAL_SEARCHD_PARAMS (code=exited, status=1/FAILURE)
        CPU: 7ms
dpkg: error processing package manticore-server (--configure):
 installed manticore-server package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of manticore:
 manticore depends on manticore-server (= 5.0.2-220530-348514c86); however:
  Package manticore-server is not configured yet.

dpkg: error processing package manticore (--configure):
 dependency problems - leaving unconfigured

I tried running systemctl status manticore.service and this is what I got:

× manticore.service - Manticore Search Engine
     Loaded: loaded (/run/systemd/generator.early/manticore.service; generated)
     Active: failed (Result: exit-code) since Mon 2023-01-02 22:16:13 UTC; 7min ago
    Process: 1136939 ExecStartPre=/usr/bin/install -omanticore -gmanticore -m755 -d /var/run/manticore (code=exited, status=0/SUCCESS)
    Process: 1136940 ExecStart=/usr/bin/searchd --config /etc/manticoresearch/manticore.conf $_ADDITIONAL_SEARCHD_PARAMS (code=exited, status=1/FAILURE)
        CPU: 9ms

I also tried manually re-running the configuration by executing sudo /usr/bin/searchd --config /etc/manticoresearch/manticore.conf $_ADDITIONAL_SEARCHD_PARAMS and I got this:

Manticore 5.0.2 348514c86@220530 dev (columnar 1.15.4 2fef34e@220522) (secondary 1.15.4 2fef34e@220522)
Copyright (c) 2001-2016, Andrew Aksyonoff
Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
Copyright (c) 2017-2022, Manticore Software LTD (https://manticoresearch.com)

[52:28.567] [1138366] using config file '/etc/manticoresearch/manticore.conf' (29779 chars)...
WARNING: key 'read_timeout' is deprecated in /etc/manticoresearch/manticore.conf line 744; use 'network_timeout' instead.
WARNING: key 'max_children' was permanently removed from configuration. Refer to documentation for details.
WARNING: key 'workers' is deprecated in /etc/manticoresearch/manticore.conf line 815; use 'default value' instead.
starting daemon version '5.0.2 348514c86@220530 dev (columnar 1.15.4 2fef34e@220522) (secondary 1.15.4 2fef34e@220522)' ...
listening on all interfaces for sphinx and http(s), port=[redacted]
listening on all interfaces for mysql, port=[redacted]
precaching index 'clsindx'
Index header format is not json, will try it as binary...
Crash!!! Handling signal 11

Any insight?

EDIT: I looked at the /etc/manticoresearch/manticore.conf file and it appears to be a holdover of a sphinx configuration file from a previous installation of sphinx search that I thought I fully deleted. (I guess not.) I’m not sure if this is really my problem or not. Also not sure how to get back to a clean install of manticore from here.

2

So the problem is:

precaching index 'clsindx'
Index header format is not json, will try it as binary...
Crash!!! Handling signal 11

You probably had /etc/manticoresearch/manticore.conf before installing Manticore and since you said you had a previous installation of Sphinx I’m assuming it refers to a Sphinx index Manticore cannot read and crashes.

how to get back to a clean install of manticore from here.

Review your config and consider removing it before installing Manticore. To reinstall just install the packages again. Also, apt remove mantcore* may help in some individual cases.

3

I think it finally worked after I manually deleted /etc/manticoresearch/ and ran

sudo apt remove --purge manticore*

Then I restarted the install process as set forth in the documentation.

sudo wget https://repo.manticoresearch.com/manticore-repo.noarch.deb
sudo dpkg -i manticore-repo.noarch.deb
sudo apt update
sudo apt install manticore manticore-columnar-lib

Now I have the basic manticore.conf in /etc/manticoresearch/:

common {
    plugin_dir = /usr/local/lib/manticore
}

searchd {
    listen = 127.0.0.1:9312
    listen = 127.0.0.1:9306:mysql
    listen = 127.0.0.1:9308:http
    log = /var/log/manticore/searchd.log
    query_log = /var/log/manticore/query.log
    pid_file = /var/run/manticore/searchd.pid
    data_dir = /var/lib/manticore
    query_log_format = sphinxql
}

Thank you for your help.