manticoresoftware / manticoresearch

Easy to use open source fast database for search | Good alternative to Elasticsearch now | Drop-in replacement for E in the ELK soon
https://manticoresearch.com
GNU General Public License v3.0
8.95k stars 497 forks source link

Unable to kill default searchd #2294

Open cappadaan opened 4 months ago

cappadaan commented 4 months ago

Bug Description:

I think this issue started around 6.2.12.

The default searchd process (which we do not need) starts automatically and cannot be killed because it restarts:

[manticore@manticore maintenance]$ ps aux | grep manticoresearch/manticore.conf mantico+ 24071 0.0 0.0 55652 3600 ? S 10:14 0:00 /usr/bin/searchd --config /etc/manticoresearch/manticore.conf mantico+ 24072 0.3 0.1 2034912 31200 ? Sl 10:14 0:01 /usr/bin/searchd --config /etc/manticoresearch/manticore.conf

[manticore@manticore maintenance]$ kill -9 24071;kill -9 24072;

[manticore@manticore maintenance]$ ps aux | grep manticoresearch/manticore.conf mantico+ 24262 0.0 0.0 55652 6288 ? S 10:21 0:00 /usr/bin/searchd --config /etc/manticoresearch/manticore.conf mantico+ 24263 2.5 0.0 2034912 15024 ? Sl 10:21 0:00 /usr/bin/searchd --config /etc/manticoresearch/manticore.conf

Manticore Search Version:

6.3.0

Operating System Version:

AlmaLinux

Have you tried the latest development version?

None

Internal Checklist:

To be completed by the assignee. Check off tasks that have been completed or are not applicable.

- [ ] Implementation completed - [ ] Tests developed - [ ] Documentation updated - [ ] Documentation reviewed - [ ] Changelog updated
tomatolog commented 4 months ago

not quite sure how the daemon process got started if it control by systemd you need to use that to start \ stop \ daemon

sanikolaev commented 4 months ago

I agree with @tomatolog . Most likely, the process is just restarted by systemd. Use systemd to stop it instead of killing it manually to prevent this issue from happening.

cappadaan commented 4 months ago

This issue is that I never started this. Manticore "started" this after a yum update, which it should not do.

sanikolaev commented 3 months ago

@cappadaan how do I reproduce it? Install Manticore, then run yum update and Manticore will be started automatically? I can't reproduce it in Ubuntu Focal:

root@2f0ede59a187:/# wget https://repo.manticoresearch.com/manticore-repo.noarch.deb && sudo dpkg -i manticore-repo.noarch.deb && sudo apt -y update && sudo apt -y install manticore manticore-extra
...

root@2f0ede59a187:/# ps aux|grep searchd
root         682  0.0  0.0   3312   720 pts/0    S+   11:37   0:00 grep --color=auto searchd

root@2f0ede59a187:/# apt update

root@2f0ede59a187:/# ps aux|grep searchd
root         992  0.0  0.0   3312   724 pts/0    S+   11:38   0:00 grep --color=auto searchd

Same with apt upgrade.

cappadaan commented 3 months ago

I think it started after installing the dev version, about 6 months ago with

sudo yum -y --enablerepo manticore-dev install manticore manticore-extra manticore-common manticore-server manticore-server-core manticore-tools manticore-executor manticore-buddy ma nticore-backup manticore-columnar-lib manticore-server-core-debuginfo manticore-tools-debuginfo manticore-columnar-lib-debuginfo manticore-icudata

sanikolaev commented 3 months ago

Sorry I missed you said yum update and tried in Ubuntu, but I've just tried and yum update also doesn't reproduce the issue. The only way I can reproduce it is by doing:

systemctl start manticore
kill `cat /var/run/manticore/searchd.pid`
kill `cat /var/run/manticore/searchd.pid`
kill `cat /var/run/manticore/searchd.pid`
[root@932cca0b23ed /]# cat /var/log/manticore/searchd.log |grep acce
[Thu Jun 20 04:01:43.445 2024] [512] accepting connections
[Thu Jun 20 04:02:54.537 2024] [580] accepting connections
[Thu Jun 20 04:03:33.029 2024] [648] accepting connections
[Thu Jun 20 04:03:35.518 2024] [712] accepting connections

If you can reproduce Manticore starting by its own without systemctl start, please let us know how to do it.