[chef] Re: is there a timeout attr for the service resource?

[Charles Johnson < >]

While it's not a timeout change, what you can do instead is set a retry.

All resources support a retries attribute, which takes an int as number of retries to attempt before marking the resource failed. There's also a retry_delay attribute, to set a timer between retries.

More info here: http://docs.opscode.com/chef/resources.html#attributes

On September 13, 2013 at 2:58:58 PM, ( ) wrote:

hai.

In a recipe, the service resource to start mysql threw an exception because it
took too long for it to start mysql. The node that runs this recipe should be
expected to possibly take several minutes to start mysql, since innodb is doing
a recovery.

[2013-09-13T21:37:46+00:00] DEBUG: service[mysql] supports status, running
[2013-09-13T21:47:56+00:00] DEBUG: Re-raising exception: Mixlib::ShellOut::CommandTimeout - service[mysql] (dbci::drone line 61) had an error: Mixlib::ShellOut::CommandTimeout: command timed out:
---- Begin output of /sbin/service mysql start ----
STDOUT: Starting MySQL (Percona Server)............

After this exception was thrown, mysql actually did finish successfully starting
up.

I looked for a way to set a timeout for the service resource, but didn't see
a way to do it. Can anyone advise?

thanks,
kallen