puppet-elasticsearch: instance won't start on Ubuntu 14.04

I’m running a box attempting to configure elasticsearch, kibana and logstash.

I’m trying to determine if the elasticsearch instance is running, but it doesn’t appear to be:

vagrant@env1:~$ sudo service elasticsearch status
 * elasticsearch is not running
vagrant@env1:~$ sudo service elasticsearch start
 * Starting Elasticsearch Server                                                             [ OK ] 
vagrant@env1:~$ sudo service elasticsearch status
 * elasticsearch is not running

and

vagrant@env1:~$ sudo /etc/init.d/elasticsearch status
 * elasticsearch is not running
vagrant@env1:~$ sudo /etc/init.d/elasticsearch start
 * Starting Elasticsearch Server                                                             [ OK ] 
vagrant@env1:~$ sudo /etc/init.d/elasticsearch status
 * elasticsearch is not running

and

vagrant@env1:~$ curl -XGET localhost:9200/_nodes/_all/process?pretty
curl: (7) Failed to connect to localhost port 9200: Connection refused

firewall rules:

vagrant@env1:~$ sudo iptables --list
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination    

my configuration is:

class { 'elasticsearch': 
    package_url => 'https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-1.3.2.deb',
}

elasticsearch::instance { 'es-01': }

and this doesn’t work either:

vagrant@env1:~$ sudo /etc/init.d/elasticsearch-es-01 status
 * elasticsearch is not running
vagrant@env1:~$ sudo /etc/init.d/elasticsearch-es-01 start
 * Starting Elasticsearch Server es-01                                        [ OK ] 
vagrant@env1:~$ sudo /etc/init.d/elasticsearch-es-01 status
 * elasticsearch is not running

I’m new to Elasticsearch, puppet and this module and this is getting quite frustrating. Do you have any insight into what the problem might be or how I’ve managed to misconfigure your module?