I verified everything this morning, and I actually had no issues running any commands against the host including ones that locked it up yesterday... until about the fifth or sixth script test containing esxcli commands. Suddenly it began the exact same behavior as yesterday. I didn't get a chance to change proxy policies, but I confirmed I'm directly on the network beside the hosts. No firewall, no proxy, etc. The issue seemed to occur after using esxcli via PowerCLI several times. I've been locked for 20 minutes or so at the $esxcli = Get-EsxCli line... again haha. Image may be NSFW.
Clik here to view.
At this point, SSH is still up so I plan to push in all my perennially-reserved flags and reboot (goes from 2.5 hours+ to 4 minutes after those are set). I'll see what happens from there I suppose.
Edit: After utilizing esxcli from the SSH console the scripts then worked correctly again. However, after several script tests the issue started again, and again using esxcli from SSH console allowed scripts to run without freezing. The scripts that cause lockup are not the same each time, but as far as I can recall they've all involved esxcli commands from PowerCLI. My best guess at this point is that something is causing esxcli to hang and that running a command from the console is somehow kick-starting it. I wish I had more time to dig into this one, but my work here will be done soon.
Message was edited by: LikeABrandit
