22:33 <jewart> well, EOFError is just the client saying that the HTTP request was narfed really, so it doesn't know much other than what it was just asking for
22:34 <jewart> which -l debug helps you find
22:34 <Eulipion> right
22:35 <Eulipion> so what gets left of a chef server when u delete a cookbook, but dont purge it?
22:35 <Eulipion> therein lies the culprit
22:36 <jewart> I believe it deletes any files that came with it
22:36 <jewart> when Chef stores data it stores data keyed by the file hash
22:36 <jewart> to dedupe
22:36 <jewart> So if you --purge, any other cookbook that relies on those files would stop working
22:37 <jewart> premature optimization possibly
22:38 <Eulipion> like it not detecting a change?
22:38 <jewart> well, let's say you upload cookbooks x, y and z22:38 <jewart> and they all have a file foo.rb in them22:38 <jewart> and that's the same file22:38 <jewart> chef stores them as hashes to dedupe data (which may be a premature optimization that causes other problems but that's a different cat to skin)22:39 <jewart> so if you remove the cookbook, I think it just removes the records, but if you --purge, it deletes the files
The Subject is "Failed Chef run on node cloud30-prod-global-afsweb-002.aerohive.com"If you ssh this host, and run sudo chef-client by hand, always work?--On Wed, Oct 15, 2014 at 7:32 AM, Mingfei Hua < " target="_blank"> > wrote:The chef client is running as crontab, sometimes I got error of “EOFError: end of file reached”, help to check attached email for detail. It’s not occurred every time, 2-3 time per week for 40 nodes running chef-client every half an hour.
Sincerely,
Mingfei Hua
-- Tiago Cruz
Archive powered by MHonArc 2.6.16.