Hi guys, I have an extreme urgent issue where under a heavy load, we are seeing the system hang when entering any command on centos 6.3 and places the system state in a D state. Raid is... [by sohk220]
I am having an issue with one of my servers where it places processes under heavy load onto an uninterruptible D state. I have included the output here. ffff88026ab959b8 000000000000004... [by sohk220]
2 identical machines (DELL Power Edge T320) with a hardware raid.
one machine is running for a while now, one machine hasn't even been set up at all
The running machine has a RAID 0+1. 4 disks (4TB each) in total all together
cloning the running machine with everything on there and everything like it is configured on the second machine.
I have an application on OSX that repeatedly goes into a Not Responding state and has to be force killed. I was hoping to automate it, but when inspecting the process with ps I don't see anything that corresponds with the Not Responding state.
I'm trying to wrap my head around Puppet, to be able to tweak our automatic build/deployment process.
The one thing that I'm missing at the moment is a concept of a "state" the machine can be in: if I understand it correctly, Puppet assumes that there is one final desired state, and it does everything to reach it and then to maintain it.
However, let's say that I'd like to have my system in diff