It’s a race on whether runsvdir has picked up the new service or not.
You likely need to set a retries value on the service resource that
causes the error, as it will succeed later.
On Wed, Apr 18, 2012 at 10:22 AM, David Montgomery
What does that mean?
I do this
Why the variability? There should be no variance for runit deciding to work.
On Thu, Apr 19, 2012 at 12:55 AM, Akzhan Abdulin
Runit cookbook has some assumptions like timings before start.
I suppose that You use “user ‘root’” property. Try to remove it to
exclude any chpst-behaviour (but chpst can’t do your original behaviour).
2012/4/18 David Montgomery email@example.com
When I use the runit cookbook, about 10% of the time I get the below
error and it kills the run. When I log int the box and I start, stop,
restart manually there is not a problem. So, why is there this issue
with the runit cookbook?
Wed, 18 Apr 2012 16:38:15 +0000] ERROR: Exception handlers complete
[Wed, 18 Apr 2012 16:38:15 +0000] FATAL: Stacktrace dumped to
[Wed, 18 Apr 2012 16:38:15 +0000] FATAL: Chef::Exceptions::Exec:
service[pixelServerMonitor] (rtb_server::default line 147) had an
error: Chef::Exceptions::Exec: /usr/bin/chpst -u root /usr/bin/sv
restart /etc/service/pixelServerMonitor returned 1, expected 0
Adam Jacob, Chief Customer Officer
T: (206) 619-7151 E: firstname.lastname@example.org