[Bug 236840] textproc/elasticsearch6: Elasticsearch 6 service doesn't start at boot time with clear_tmp_enable="YES" in /etc/rc.conf
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Nov 3 16:08:19 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236840
--- Comment #2 from Nemesis11 <felix at zwame.pt> ---
Thank you for reviewing this bug.
Just an update. I had this machine with FreeBSD 12.1 with the latest updates
and I upgraded it to version 12.2 and I can confirm that this bug is still
valid.
If I have the clear_tmp_enable="YES" service enabled in /etc/rc.conf, the
elasticcsearch 6 service will fail to start.
After the boot, if I start the elasticsearch 6 service manually, it will start
with no problem.
If I comment clear_tmp_enable="YES" service, the elasticsearch 6 service will
start automatically at boot, with no problem.
I can replicate the problem in a second machine, that has more services then
this one (nginx, mariadb104-server, etc), and it only happens with the
elasticsearch 6 service.
I'm using the latest trimestral elasticsearch 6 package. Version
elasticsearch6-6.8.12.
Output before and after the FreeBSD 12.2 update, with the
clear_tmp_enable="YES" service enabled, at boot:
felix at elasticforum2:~ % doas uname -a
FreeBSD elasticforum2 12.1-RELEASE-p10 FreeBSD 12.1-RELEASE-p10 GENERIC amd64
felix at elasticforum2:~ % doas service elasticsearch status
elasticsearch is not running.
felix at elasticforum2:~ % doas uname -a
FreeBSD elasticforum2 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC amd64
felix at elasticforum2:~ % doas service elasticsearch status
elasticsearch is not running.
Thank you and Best Regards.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
More information about the freebsd-elastic
mailing list