While you try to patch the problem itself, maybe an interim patch to
get a more informative status would also greatly help. As for now,
systemclt says the service is "active" when it actually didn't start
and absolutely no information is available in the logs.


‚óŹ elasticsearch.service - LSB: Starts elasticsearch
   Loaded: loaded (/etc/init.d/elasticsearch; generated; vendor preset: enabled)
   Active: active (exited) since jeu. 2016-08-18 03:40:52 CEST; 1s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 26542 ExecStop=/etc/init.d/elasticsearch stop (code=exited, 
status=0/SUCCESS)
  Process: 26549 ExecStart=/etc/init.d/elasticsearch start (code=exited, 
status=0/SUCCESS)


When starting the daemon by hand, I got the YAMLException and a 130
error code, so I'm wondering why those processes are said to have
exited with code 0.

Regards,
Pierre
-- 
pie...@nothos.net
OpenPGP 0xD9D50D8A

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to