Closed dkindlund closed 14 years ago
dkindlund
commented
14 years ago Author: kindlund What are the specs of this server? I'll need CPU, RAM and HD specifications. Also, are there any other CPU or RAM-intensive processes running on the host system? Any other VMs running (aside from Firewall VM)?
-- Darien
dkindlund
commented
14 years ago Author: Justin ajwilder@usa.net Darien,
Running on an intel dual core 4g ram, 80g drive. Other than the VM, Gnome is the only resource intensive process.
No other VM are running or registered.
I can see the master vm get registered in the VM console just before it dies.
Justin
dkindlund
commented
14 years ago Author: kindlund Okay, start up "master.vmx" manually via the VMware Remote Console. Does the console ask you any sort of question upon power up? For example, "Do you wish to create a new UUID?"
If power on happens and the master.vmx automatically boots up (and logs into Windows OS as Administrator and loads the Agent code inside the VM just fine), then try this unit test:
{{{ cd ~/honeyclient perl -Ilib t/honeyclient_manager_vm_clone.t }}}
-- Darien
dkindlund
commented
14 years ago Author: Justin ajwilder@usa.net For whatever reason VMware had issue with the master.vmx config. I had to set:
ide0:0.mode = "independent-persistent"
in order to eliminate the VMware error.
Will this change how honeyclient behaves?
thx Justin
dkindlund
commented
14 years ago Author: kindlund Perhaps.
Before the honeyclient manager runs, the master.vmx line should read:
{{{ ide0:0.mode = "persistent" }}}
WHILE the honeyclient manager is running, this line in the master.vmx is automatically changed to:
{{{ ide0:0.mode = "undoable" }}}
You can try testing it, to see if there are any issues when running the manager.
-- Darien
dkindlund
commented
14 years ago Author: Justin ajwilder@usa.net There may have been another issues. resetting to independent-persistent, booting, shutdown, re-editing back to "persistent" then booting solved the problem whatever it was.
Thx for your help over the last few days!
Justin
dkindlund
commented
14 years ago Author: kindlund Glad to hear. Closing this ticket.
-- Darien
It looks like vmware-cmd crashes at some point. It leaves a core file within the vm/master directory.
perl -Ilib t/honeyclient_manager_vm.t executes without errors.
Master VM registers and loads without a problem manually.
startManager.pl Output {{{
Oct 7 09:26:53 10.10.0.1 bin/StartManager.pl: WARN HoneyClient::Manager::VM::_connectVM - Could not connect to VM (/home/vm/master/master.vmx). (0: Success) Oct 7 09:26:53 10.10.0.1 bin/StartManager.pl: ERROR HoneyClient::Util::SOAP::_handleFault - Error occurred during processing. HoneyClient::Manager::VM->_connectVM(): Could not connect to VM (/home/vm/master/master.vmx). HoneyClient::Manager::VM->_connectVM(): {'err' => bless( {'errNo' => '0','errStr' => 'Success'}, 'err' )}
}}}
Syslog:
{{{ Oct 7 09:26:46 SigmaApex vmware-authd[11879]: The "/usr/lib/vmware/bin/vmware-vmx" process did not start properly. Exit 0x0 Oct 7 09:26:49 SigmaApex vmware-authd[11883]: The "/usr/lib/vmware/bin/vmware-vmx" process did not start properly. Exit 0x0 Oct 7 09:26:53 SigmaApex vmware-authd[11889]: The "/usr/lib/vmware/bin/vmware-vmx" process did not start properly. Exit 0x0
}}}
thx! Justin