Open docwhat opened 9 years ago
You don't mention it, but I'm guessing that this is occurring in a winrm session to a windows guest ? If so, you might want to check out https://support.microsoft.com/kb/2842230
Switching from chef_zero to chef_solo seemed to fix it. I'm not sure why, though.
@robcoward Yes, it is a winrm session to a windows guest. That's lovely that winrm has such a hard limit. I'm guessing chef_zero is using a lot more memory because it emulates a whole chef-server and chef-client?
Is there a way a separate session can be run that honors the MaxMemoryPerShellMB
value from winrm? Or maybe a service should be created for chef_zero/chef_solo and it run manually by winrm?
That would work around most/all the cases, no?
Our solution was to use packer to create our own custom vagrant box file and AWS ami with the microsoft patch applied. Once the patch is applied to your vm, the memory errors go away.
Whenever
Mixlib::ShellOut
(e.g. theexecute
command in a recipe) is used, the executed process runs out of memory.The cookbooks I'm using have only done
chef-service-manager
andgem
(from 'chef-sugar') and both are ruby commands. So I don't know if it is a ruby-specific problem or not.It's very odd because the commands run fine by hand as Administrator.
Ciao!
Example: