0.3.13: service doesn't successfully start

[heffergm]

This is a regression from 0.3.10 which I had been using previously. From what I see, the installation proceeds normally on a fresh install. I have skip_restart = true set and skip_start I do not override (so it is false).

The delayed start command is issued to the service:

[2015-04-14T19:22:11+00:00] INFO: ark[elasticsearch] sending start action to service[elasticsearch] (delayed)
[2015-04-14T19:22:11+00:00] INFO: Processing service[elasticsearch] action start (elasticsearch::default line 72)
[2015-04-14T19:22:11+00:00] INFO: service[elasticsearch] started

However, the service does not actually start. I'm left with an empty PID file in /usr/local/var/run, and no logs. Manually starting the service succeeds (with an error that appears to be a failed grep of the empty PID file).

[karmi]

Hi, yeah, I think there are many errors related to the init script template -- we're trying to finish the refactoring of the cookbook in the next as soon as possible, so we get rid of these legacy problems...

[khoan]

I'm on cookbook 0.3.12 and elasticsearch 1.3.8 used to start as a init.d service. But elasticsearch 1.5.2 and 1.6.0 doesn't start on ubuntu 14.04 LTS anymore.

ubuntu@apricot:~$ sudo service elasticsearch start
PID file found in /usr/local/var/run/apricot_localdomain.pid
Starting Elasticsearch... [OK]
ubuntu@apricot:~$ curl localhost:9200
curl: (7) Failed to connect to localhost port 9200: Connection refused
ubuntu@apricot:~$ ps aux | grep java
ubuntu   15375  0.0  0.1  10460   928 pts/0    S+   00:49   0:00 grep --color=auto java
ubuntu@apricot:~$ java -version
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)

ubuntu@apricot:~$ vi /etc/init.d/elasticsearch
# remove --background --quiet options in start-stop-daemon

ubuntu@macadamia:~$ sudo service elasticsearch start
PID file found in /usr/local/var/run/macadamia_localdomain.pid
Starting Elasticsearch...[2015-07-06 01:02:04,121][INFO ][node                     ] [macadamia.localdomain] version[1.6.0], pid[16777], build[cdd3ac4/2015-06-09T13:36:34Z]
[2015-07-06 01:02:04,122][INFO ][node                     ] [macadamia.localdomain] initializing ...
[2015-07-06 01:02:04,178][INFO ][plugins                  ] [macadamia.localdomain] loaded [marvel, cloud-aws], sites [marvel]
[2015-07-06 01:02:04,324][INFO ][env                      ] [macadamia.localdomain] using [1] data paths, mounts [[/data (/dev/xvdi)]], net usable_space [49.8gb], net total_space [49.9gb], types [xfs]
{1.6.0}: Initialization Failed ...
1) NoSuchMethodError[org.elasticsearch.discovery.zen.ZenDiscovery.<init>(Lorg/elasticsearch/common/settings/Settings;Lorg/elasticsearch/cluster/ClusterName;Lorg/elasticsearch/threadpool/ThreadPool;Lorg/elasticsearch/transport/TransportService;Lorg/elasticsearch/cluster/ClusterService;Lorg/elasticsearch/node/settings/NodeSettingsService;Lorg/elasticsearch/cluster/node/DiscoveryNodeService;Lorg/elasticsearch/discovery/zen/ping/ZenPingService;Lorg/elasticsearch/Version;Lorg/elasticsearch/discovery/DiscoverySettings;)V]2) IllegalStateException[This is a proxy used to support circular references involving constructors. The object we're proxying is not constructed yet. Please wait until after injection has completed to use this object.]
 [OK]

trying upgrading plugins elasticsearch/elasticsearch-cloud-aws to version 2.5.0...

[martinb3]

Hi there -- we've recently re-written the cookbook (the next branch @karmi was referring to) and we're now testing on Ubuntu 14.04 in CI. Unless it's plugins that are stopping elasticsearch itself, feel free to try our newest cookbook version in Git.

[khoan]

sorry to waste your time.

Lest anyone gets bitten, matching elasticsearch-cloud-aws version to elasticsearch does the trick.

[martinb3]

No problem. I've created #330 to see if we can do anything better in the future.