-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vagrant ports for sensu-enterprise-server are off #735
Comments
The vagrant port does seem to be off by one (4568 instead of 4567) which may be a red herring though. I'm looking into why there's nothing listening on port 4567 or 4568 inside the underlying VM, which is likely the root cause of the issue. |
Also observed this, which may be directly related to why the API isn't bound to the TCP port:
|
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jul 12, 2017
Without this patch the sensu-enterprise server is quickly crashing with a JVM out of memory error when started inside the sensu-server-enterprise VM. This patch addresses the problem by bumping up the allocated RAM for the VM from 512m to 768m while also bringing down the JVM heap size from 2GB to 256m. Resolves sensu#735
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jul 12, 2017
Without this patch the sensu-enterprise server is quickly crashing with a JVM out of memory error when started inside the sensu-server-enterprise VM. This patch addresses the problem by bumping up the allocated RAM for the VM from 512m to 768m while also bringing down the JVM heap size from 2GB to 256m. The API has been tested with the following commands, with no other VM's running: vagrant up sensu-server-enterprise curl -s http://admin:secret@127.0.0.1:4567/clients \ | jq -r 'map(.name | split(".") | .[0]) | sort | .[]' Resolves sensu#735
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jul 12, 2017
Without this patch the sensu-enterprise server is quickly crashing with a JVM out of memory error when started inside the sensu-server-enterprise VM. This patch addresses the problem by bumping up the allocated RAM for the VM from 512m to 768m while also bringing down the JVM heap size from 2GB to 256m. The API has been tested with the following commands, with no other VM's running: vagrant up sensu-server-enterprise curl -s http://admin:secret@127.0.0.1:4567/clients \ | jq -r 'map(.name | split(".") | .[0]) | sort | .[]' Resolves sensu#735
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jul 13, 2017
Without this patch the sensu-enterprise server is quickly crashing with a JVM out of memory error when started inside the sensu-server-enterprise VM. This patch addresses the problem by bumping up the allocated RAM for the VM from 512m to 768m while also bringing down the JVM heap size from 2GB to 256m. The API has been tested with the following commands, with no other VM's running: vagrant up sensu-server-enterprise curl -s http://admin:secret@127.0.0.1:4567/clients \ | jq -r 'map(.name | split(".") | .[0]) | sort | .[]' Resolves sensu#735
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jul 13, 2017
Without this patch the sensu-enterprise server is quickly crashing with a JVM out of memory error when started inside the sensu-server-enterprise VM. This patch addresses the problem by bumping up the allocated RAM for the VM from 512m to 768m while also bringing down the JVM heap size from 2GB to 256m. The API has been tested with the following commands, with no other VM's running: vagrant up sensu-server-enterprise curl -s http://admin:secret@127.0.0.1:4567/clients \ | jq -r 'map(.name | split(".") | .[0]) | sort | .[]' Resolves sensu#735
ghoneycutt
added a commit
that referenced
this issue
Jul 13, 2017
(#735) Fix sensu-server-enterprise Vagrant VM
Fix released in v2.22.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently one cannot test the API when using sensu-enterprise-server from the host. I believe that the redirected ports should be different in the Vagrantfile.
The text was updated successfully, but these errors were encountered: