Init script start does not sleep long enough to ensure successful start #353
Comments
@promisedlandt Seems that this issue is related to https://github.com/sensu/sensu-build I believe we are still planning to ship an embedded runit with the Sensu packages, killing the need for these init scripts. @joemiller Thoughts? Should we attack runit now? |
@portertech Not sure how that's related, but apparently runit can run under sysv-init, so I'm cool with that. It would solve #354 as well I believe, as runit doesn't need pidfiles? Off topic: I got some days off next month, is there anywhere in Sensu I can help out with mediocre programming and low sysadmin skills? |
Yeah, might be a good time to try to embed runit now. We'll have to take a On Thu, Aug 23, 2012 at 1:47 AM, Nils Landt notifications@github.comwrote:
|
@promisedlandt Not sure about where to code right now, but a blog post, docs or being helpful in #sensu are great ways to make sensu more successful. More plugins/handlers are always great too ;) |
sensu-0.9.12.beta.5-5 has an embedded runit w/ some tooling. /opt/sensu/bin/sensu-ctl configure |
In the init script start function, there's a section:
However, errors like not being able to connect to RabbitMQ occur on my low-power system only after about 4 seconds.
On the other hand, increasing the sleep time would be an inconvenience when everythign works fine, so I'm not sure what a good solution would be here.
The text was updated successfully, but these errors were encountered: