FATAL: IOError: Cannot open or read /var/chef/cache/cookbooks/monit/attributes/default.rb!


#1

Hi,

I am bootstrapping my node automatically with a bash script and I get
the below error about 50% of the time. Well…when I bootstrap
manually it works 100% of the time. How can I make chef more robust
since these types of errors have implications for failover. I am
using hosted chef

[Mon, 09 Jul 2012 08:02:20 +0100] INFO: Storing updated
cookbooks/chef-client/LICENSE in the cache.
[Mon, 09 Jul 2012 08:02:21 +0100] INFO: Storing updated
cookbooks/chef-client/metadata.rb in the cache.
[Mon, 09 Jul 2012 08:02:22 +0100] INFO: Storing updated
cookbooks/chef-client/metadata.json in the cache.
[Mon, 09 Jul 2012 08:02:23 +0100] INFO: Storing updated
cookbooks/chef-client/CONTRIBUTING in the cache.
[Mon, 09 Jul 2012 08:02:25 +0100] INFO: Storing updated
cookbooks/chef-client/README.md in the cache.
[Mon, 09 Jul 2012 08:02:26 +0100] INFO: Storing updated
cookbooks/chef-client/CHANGELOG.md in the cache.
[Mon, 09 Jul 2012 08:02:27 +0100] INFO: Storing updated
cookbooks/redis26/recipes/default.rb in the cache.
[Mon, 09 Jul 2012 08:02:28 +0100] INFO: Storing updated
cookbooks/redis26/README.md in the cache.
[Mon, 09 Jul 2012 08:02:29 +0100] INFO: Storing updated
cookbooks/redis26/metadata.rb in the cache.
[Mon, 09 Jul 2012 08:02:29 +0100] ERROR: Running exception handlers
[Mon, 09 Jul 2012 08:02:29 +0100] FATAL: Saving node information to
/var/chef/cache/failed-run-data.json
[Mon, 09 Jul 2012 08:02:29 +0100] ERROR: Exception handlers complete
[Mon, 09 Jul 2012 08:02:29 +0100] FATAL: Stacktrace dumped to
/var/chef/cache/chef-stacktrace.out
[Mon, 09 Jul 2012 08:02:29 +0100] FATAL: IOError: Cannot open or read
/var/chef/cache/cookbooks/monit/attributes/default.rb!


#2

Fix whatever is causing the IOError: it has little to do with Chef.

–AJ

On 9 July 2012 19:13, David Montgomery davidmontgomery@gmail.com wrote:

Hi,

I am bootstrapping my node automatically with a bash script and I get
the below error about 50% of the time. Well…when I bootstrap
manually it works 100% of the time. How can I make chef more robust
since these types of errors have implications for failover. I am
using hosted chef

[Mon, 09 Jul 2012 08:02:20 +0100] INFO: Storing updated
cookbooks/chef-client/LICENSE in the cache.
[Mon, 09 Jul 2012 08:02:21 +0100] INFO: Storing updated
cookbooks/chef-client/metadata.rb in the cache.
[Mon, 09 Jul 2012 08:02:22 +0100] INFO: Storing updated
cookbooks/chef-client/metadata.json in the cache.
[Mon, 09 Jul 2012 08:02:23 +0100] INFO: Storing updated
cookbooks/chef-client/CONTRIBUTING in the cache.
[Mon, 09 Jul 2012 08:02:25 +0100] INFO: Storing updated
cookbooks/chef-client/README.md in the cache.
[Mon, 09 Jul 2012 08:02:26 +0100] INFO: Storing updated
cookbooks/chef-client/CHANGELOG.md in the cache.
[Mon, 09 Jul 2012 08:02:27 +0100] INFO: Storing updated
cookbooks/redis26/recipes/default.rb in the cache.
[Mon, 09 Jul 2012 08:02:28 +0100] INFO: Storing updated
cookbooks/redis26/README.md in the cache.
[Mon, 09 Jul 2012 08:02:29 +0100] INFO: Storing updated
cookbooks/redis26/metadata.rb in the cache.
[Mon, 09 Jul 2012 08:02:29 +0100] ERROR: Running exception handlers
[Mon, 09 Jul 2012 08:02:29 +0100] FATAL: Saving node information to
/var/chef/cache/failed-run-data.json
[Mon, 09 Jul 2012 08:02:29 +0100] ERROR: Exception handlers complete
[Mon, 09 Jul 2012 08:02:29 +0100] FATAL: Stacktrace dumped to
/var/chef/cache/chef-stacktrace.out
[Mon, 09 Jul 2012 08:02:29 +0100] FATAL: IOError: Cannot open or read
/var/chef/cache/cookbooks/monit/attributes/default.rb!