-
Notifications
You must be signed in to change notification settings - Fork 657
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
Health-Monitor fails to start because of NATS? #2524
Comments
Set log level for health_monitor to debug, but that barely did anything and also didn't show any errors.
|
After scaling the BOSH director to a bigger vm_type the issue got resolved. It seems like the director was just 'too slow' to come up in time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
During a bosh create-env (using bosh-deployment) the director is not able to start, it fails during step
Waiting for instance 'bosh/0' to be running... Failed (00:05:02)
When checking the VM the health-monitor state is flapping between
not running
andconnection failed
.After a monit restart all, all jobs are able to start without any issues.
The environment that is currently showing the issues is running around 1300 deployments on the director.
To Reproduce
Unfortunately currently I do not know general approach to reproduce the issue
Expected behavior
Health-Monitor should be able to start without a monit restart all.
Logs
nats.logs
After monit restart the output of nats changes
healthmonitor.log
after restart of nats
Versions (please complete the following information):
Deployment info:
If possible, share your (redacted) manifest and any ops files used to deploy
BOSH or any other releases on top of BOSH.
If you used any deployment strategy it'd be helpful to point it out and share as
much about it as possible (e.g. bosh-deployment, PCF, genesis, spiff, etc)
Additional context
https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1712235399314399
The text was updated successfully, but these errors were encountered: