Chassis / Chassis_Elasticsearch

A Chassis extension for Elasticsearch
1 stars 3 forks source link

Elasticsearch won't start #20

Closed mikeselander closed 4 years ago

mikeselander commented 4 years ago

I've got bad news 😬 after the recent merges today, Elasticsearch won't start for me. I'm using an Altis v3 stack and after pulling down the fresh Chassis extension it won't start up when provisioning.

I get the following trace from a provision:

==> servus-altis.local: Running action triggers before provision ...
==> servus-altis.local: Running trigger...
==> servus-altis.local:
==> servus-altis.local: Running provisioner: shell...
    servus-altis.local: Running: /var/folders/cd/2hthn83x7x189xt7m_jxcqrw0000gn/T/vagrant-shell20200403-79269-8jvj74.sh
==> servus-altis.local: Running provisioner: shell...
    servus-altis.local: Running: inline script
    servus-altis.local: Notice: Compiled catalog for servus-altis.local in environment production in 1.46 seconds
    servus-altis.local: Notice: /Stage[main]/Cavalcade/Service[cavalcade]/ensure: ensure changed 'stopped' to 'running'
    servus-altis.local: Notice: /Stage[main]/Main/Package[git-core]/ensure: created
    servus-altis.local: Notice: /Stage[main]/Chassis::Hosts/Exec[upgrade pip]/returns: executed successfully
    servus-altis.local: Notice: /Stage[main]/Intl/Apt::Ppa[universe]/Exec[add-apt-repository-universe]/returns: executed successfully
    servus-altis.local: Notice: /Stage[main]/Chassis_openssl/File[/vagrant/servus-altis.local.cert]/mode: mode changed '0777' to '0644'
    servus-altis.local: Notice: /Stage[main]/Chassis_openssl/File[/vagrant/servus-altis.local.key]/mode: mode changed '0777' to '0644'
    servus-altis.local: Notice: /Stage[main]/Chassis::Php/Remove_php_version[7.4]/Package[php7.4-common]/ensure: removed
    servus-altis.local: Notice: /Stage[main]/Apt::Update/Exec[apt_update]: Triggered 'refresh' from 1 event
    servus-altis.local: Notice: /Stage[main]/Apcu/Package[php7.2-apcu]/ensure: created
    servus-altis.local: Notice: /Stage[main]/V8js::Extension/Exec[pecl channel-update pecl.php.net]/returns: executed successfully
    servus-altis.local: Notice: /Stage[main]/Chassis::Php/Service[php7.2-fpm]: Triggered 'refresh' from 2 events
    servus-altis.local: Notice: /Stage[main]/Chassis_elasticsearch/Elasticsearch::Instance[es]/Elasticsearch::Service[es]/Elasticsearch::Service::Systemd[es]/Service[elasticsearch-instance-es]/ensure: ensure changed 'stopped' to 'running'
    servus-altis.local: Notice: Failed to connect to the ES instance within timeout window of 30 seconds; giving up.
    servus-altis.local: Error: Failed to apply catalog: Failed to open TCP connection to 0.0.0.0:9200 (Connection refused - connect(2) for "0.0.0.0" port 9200)
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I had to destroy the machine and re-up for it to work again; provisioning wouldn't clear the issue.

  1. What operating system do you use? Mac OSX

  2. What version of Vagrant are you running? 2.2.7

  3. Are you using VirtualBox or VMWare and which version are you using? Virtualbox

BronsonQuick commented 4 years ago

Thanks for the bug report! I can replicate this so I'll see if I can fix it now too #blamebronson