Crazy Big Searchd logs!

I have a log file running astray:

sharetribe/log$ tail production.searchd.log.2
[Tue Aug 22 17:39:18.211 2017] [10690] watchdog: main process 30841 killed dirtily with signal 7, core dumped, will be restarted
[Tue Aug 22 17:39:18.211 2017] [10690] watchdog: main process 30845 forked ok
[Tue Aug 22 17:39:18.314 2017] [10690] watchdog: main process 30845 killed dirtily with signal 7, core dumped, will be restarted
[Tue Aug 22 17:39:18.314 2017] [10690] watchdog: main process 30849 forked ok
[Tue Aug 22 17:39:18.415 2017] [10690] watchdog: main process 30849 killed dirtily with signal 7, core dumped, will be restarted
[Tue Aug 22 17:39:18.415 2017] [10690] watchdog: main process 30851 forked ok
[Tue Aug 22 17:39:18.516 2017] [10690] watchdog: main process 30851 killed dirtily with signal 7, core dumped, will be restarted
[Tue Aug 22 17:39:18.517 2017] [10690] watchdog: main process 30853 forked ok
[Tue Aug 22 17:39:18.618 2017] [10690] watchdog: main process 30853 killed dirtily with signal 7, core dumped, will be restarted
[Tue Aug 22 17:39:18.618 2017] [10690] watchdog: main process 30855 forked ok

The file consumes about a gig every few days; which is obviously not a good thing. Stopping and starting searchd using rake ts:start (and stop respectively) has no effect… The search function also works properly.

Any ideas?

Thanks!

It must have just been a bunk instance of the process. I stopped searchd using ‘rake ts:stop’, then just used ‘pkill -f searchd’ to kill the rogue processes and it seems to have cleared it up!