Job for manticore.service failed because the control process exited with error code.

General Discussions - English
1

Hi folks,

This is my first usage of Manticore, and I’m a bit stuck. The good news, is that the index built successfully and searching works (yay!), however:

[root ~]# systemctl start manticore
Job for manticore.service failed because the control process exited with error code.
See "systemctl status manticore.service" and "journalctl -xe" for details.





[root ~]# systemctl status manticore.service
● manticore.service - Manticore Search Engine
   Loaded: loaded (/run/systemd/generator.early/manticore.service; generated)
   Active: failed (Result: exit-code) since Mon 2023-05-22 23:55:56 EDT; 1h 36min ago
  Process: 12990 ExecStart=/usr/bin/searchd --config /etc/manticoresearch/manticore.conf $_ADDITIONAL_SEARCHD_PARAMS (code=exited, status=1/FAILURE)
  Process: 12988 ExecStartPre=/usr/bin/install -omanticore -gmanticore -m755 -d /var/run/manticore (code=exited, status=0/SUCCESS)

May 22 23:55:56 myserver.com systemd[1]: manticore.service: Service RestartSec=100ms expired, scheduling restart.
May 22 23:55:56 myserver.com systemd[1]: manticore.service: Scheduled restart job, restart counter is at 5.
May 22 23:55:56 myserver.com systemd[1]: Stopped Manticore Search Engine.
May 22 23:55:56 myserver.com systemd[1]: manticore.service: Start request repeated too quickly.
May 22 23:55:56 myserver.com systemd[1]: manticore.service: Failed with result 'exit-code'.
May 22 23:55:56 myserver.com systemd[1]: Failed to start Manticore Search Engine.





[root ~]# searchd
Manticore 6.0.4 1a3a4ea82@230314 (columnar 2.0.4 5a49bd7@230306) (secondary 2.0.4 5a49bd7@230306)
Copyright (c) 2001-2016, Andrew Aksyonoff
Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
Copyright (c) 2017-2023, Manticore Software LTD (https://manticoresearch.com)

[41:14.176] [16531] using config file '/etc/manticoresearch/manticore.conf' (5293 chars)...
starting daemon version '6.0.4 1a3a4ea82@230314 (columnar 2.0.4 5a49bd7@230306) (secondary 2.0.4 5a49bd7@230306)' ...
listening on 127.0.0.1:9308 for sphinx and http(s)
precaching table 'index_site_0l8eac2aipxu6mkw_main'
precaching table 'index_site_0l8eac2aipxu6mkw_delta'
precached 2 tables in 0.033 sec

As you can see, running systemctl start manticore results in an error. This seems odd, because just starting searchd works fine.

This is on AlmaLinux v8.8.0

Any assistance would be greatly appreciated. Thanks!

2

Hi

journalctl -u manticore can give you more details. I can assume you made a typical mistake: ran indexer and/or searchd under root which resulted in in creating files under root and then when you attempted to do systemctl start manticore it tried to start searchd under user manticore which was impossible.

3

Thanks for your reply.

The indexer was run as the manticore user, but the searchd log file was indeed owned by root. That was the issue. Rectifying that permission error resolved the issue above.

4

OK, great!

BTW systemctl enable manticore should work fine in the next release and in the latest dev package.