HoneyClient::Manager::VM Testing Failed

Hi Devinder,

It looks like you tried 'make test' on the HoneyClient::Manager::VM package and ran into the following errors:

ok 69 - fullCloneVM(src_config => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx', dest_dir => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm_clone')
Can't locate auto/threads/is_running.al in @INC (@INC contains: lib/ /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at lib//HoneyClient/Manager/VM.pm line 4745
END failed--call queue aborted.

not ok 74 - getIPaddrVM(config => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx')
#   Failed test 'getIPaddrVM(config => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx')'
#   at t/honeyclient_manager_vm.t line 795.
#                   undef
#     doesn't match '/[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}/'
# The getIPaddrVM() call failed.  Attempted to retrieve the IP address of test VM (/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx).

These are two separate issues, but I will try to help you resolve both in this ticket. For both of these issues, please post your replies as comments to this ticket — please do not create a new ticket.

The first issue is:

ok 69 - fullCloneVM(src_config => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx', dest_dir => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm_clone')
Can't locate auto/threads/is_running.al in @INC (@INC contains: lib/ /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at lib//HoneyClient/Manager/VM.pm line 4745
END failed--call queue aborted.

For this issue, it appears as though your 'threads' and 'threads::shared' perl libraries are not properly upgraded. To upgrade these libraries, type the following commands, as root:

# cpan
> install threads
...

> install threads::shared
...

> install threads
threads is up to date (1.63).

> install threads::shared
threads::shared is up to date (1.12).

Once you've done this, please confirm that test 69 no longer gives you this error.

The second issue is:

not ok 74 - getIPaddrVM(config => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx')
#   Failed test 'getIPaddrVM(config => '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx')'
#   at t/honeyclient_manager_vm.t line 795.
#                   undef
#     doesn't match '/[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}/'
# The getIPaddrVM() call failed.  Attempted to retrieve the IP address of test VM (/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx).

This error could happen, if the perl code does not have proper access to your syslog file. If your main syslog file is '/var/log/messages', then be sure this file is set with 644 permissions, by typing the following, as root:

# chmod 644 /var/log/messages

If your main syslog file is somewhere else, then you need to edit your etc/honeyclient.xml file and change the following entry accordingly:

<HoneyClient>
    <Manager>
        <VM>
            <dhcp_log description="The absolute path to the file that contains the DHCP logs, when a new VM gets a DHCP lease from the VMware Server / GSX server." default="/var/log/messages">
                /var/log/messages
            </dhcp_log>
        </VM>
    </Manager>
</HoneyClient>

Please let me know if this helps.

Regards,

— Darien

Replying to kindlund:

Hi Kinlund,

Thanks for the help.

I managed to solve error 69. Error 74 not solved yet although i had # Chmod 644 /var/log/messages.

Is it because i dont have WinXPPro Installed in the VM. my host machine is running on ubuntu 6 Regards Devinder

It looks like you tried 'make test' on the HoneyClient::Manager::VM package and ran into the following errors: {{{ ok 69 - fullCloneVM(src_config ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx', dest_dir ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm_clone') Can't locate auto/threads/is_running.al in @INC (@INC contains: lib/ /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at lib//HoneyClient/Manager/VM.pm line 4745 END failed—call queue aborted. not ok 74 - getIPaddrVM(config ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx') # Failed test 'getIPaddrVM(config ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx')' # at t/honeyclient_manager_vm.t line 795. # undef # doesn't match '/[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}/' # The getIPaddrVM() call failed. Attempted to retrieve the IP address of test VM (/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx). }}} These are two separate issues, but I will try to help you resolve both in this ticket. For both of these issues, please post your replies as comments to this ticket — please do not create a new ticket. The first issue is: {{{ ok 69 - fullCloneVM(src_config ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx', dest_dir ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm_clone') Can't locate auto/threads/is_running.al in @INC (@INC contains: lib/ /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at lib//HoneyClient/Manager/VM.pm line 4745 END failed—call queue aborted. }}} For this issue, it appears as though your 'threads' and 'threads::shared' perl libraries are not properly upgraded. To upgrade these libraries, type the following commands, as root: {{{ # cpan

install threads

…

install threads::shared

…

install threads

threads is up to date (1.63).

install threads::shared

threads::shared is up to date (1.12). }}} Once you've done this, please confirm that test 69 no longer gives you this error. The second issue is: {{{ not ok 74 - getIPaddrVM(config ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx') # Failed test 'getIPaddrVM(config ⇒ '/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx')' # at t/honeyclient_manager_vm.t line 795. # undef # doesn't match '/[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}/' # The getIPaddrVM() call failed. Attempted to retrieve the IP address of test VM (/home/devinder/HoneyClient-Manager-0.99/t/test_vm/winXPPro.vmx). }}} This error could happen, if the perl code does not have proper access to your syslog file. If your main syslog file is '/var/log/messages', then be sure this file is set with 644 permissions, by typing the following, as root: {{{ # chmod 644 /var/log/messages }}} If your main syslog file is somewhere else, then you need to edit your etc/honeyclient.xml file and change the following entry accordingly: {{{ #!xml <HoneyClient> <Manager> <VM> <dhcp_log description="The absolute path to the file that contains the DHCP logs, when a new VM gets a DHCP lease from the VMware Server / GSX server." default="/var/log/messages"> /var/log/messages </dhcp_log> </VM> </Manager> </HoneyClient> }}} Please let me know if this helps. Regards, — Darien

Hi Devinder,

No, you do not need to install Windows XP in a new VM in order to run these tests.

The issue is simply that the code is trying to extract IP information from your primary syslog file and it is unable to do so.

Once you run this test, could you please post the last 100 lines of your /var/log/messages file to this ticket?

Thanks,

— Darien

Issue resolved. Follow-up details:

After chatting with Devinder directly, we were able to resolve both issues. The original fixes suggested worked. Apparently, he was using Ubuntu as the host system and by default, Ubuntu drops all DEBUG level messages from /var/log/messages.

So, in order to fix this, we had to edit the /etc/syslog.conf file and append a *.* to the /var/log/messages line, as follows:

...,*.*    /var/log/messages

Then, we restarted the syslogd daemon, by issuing:

/etc/init.d/sysklogd restart

Once done, the /var/log/messages file was properly populated with "vmnet-dhcpd" messages.

Hi Darien I am not sure (Step #15) on the set up for this task. Do i create the directory /vm/master-vms/Agent.Master-23/winXPPro.cfg but i dont have the .cfg file.

<HoneyClient>

<Manager>

<VM>

<master_vm_config description="The full absolute path to the VM configuration file on the host system that will be used by all subsequent cloned VMs.">

/vm/master-vms/Agent.Master-23/winXPPro.cfg

</master_vm_config>

</VM>

</Manager>

</HoneyClient>

and what should i put for these variables found in /etc/honeyclient.xml

<!— HoneyClient::Manager::FW Options —>

<FW>

<!— TODO: Update this. —> <address description="eth0 interface static IP">

192.168.0.128

</address> <!— TODO: Update this. —> <port description="Default FW port number" default="8083">

8083

</port> <!— TODO: Update this. —> <primaryDns description="Primary DNS IP Address">

128.29.154.150

</primaryDns> <!— TODO: Update this. —> <secondaryDns description="Secondary DNS IP address">

128.29.40.1

</secondaryDns> <!— TODO: Update this. —> <gsx_gateway description="IP address of GSX or VMware Server">

10.0.0.1/32

</gsx_gateway> <!— TODO: Update this. —> <fwGateway description="Gateway IP address of the Firewall">

10.0.0.254/32

</fwGateway> <!— TODO: Update this. —> <honeyclientnet description="CIDR notation for honeyclient netblock">

10.0.0.0/24

Regards, Devinder

Replying to kindlund:

Issue resolved. Follow-up details: After chatting with Devinder directly, we were able to resolve both issues. The original fixes suggested worked. Apparently, he was using Ubuntu as the host system and by default, Ubuntu drops all DEBUG level messages from /var/log/messages. So, in order to fix this, we had to edit the /etc/syslog.conf file and append a *.* to the /var/log/messages line, as follows: {{{ …,*.* /var/log/messages }}} Then, we restarted the syslogd daemon, by issuing: {{{ /etc/init.d/sysklogd restart }}} Once done, the /var/log/messages file was properly populated with "vmnet-dhcpd" messages.

Responded to this issue in ticket #83.