Archive for the tag 'failed'

VMware Workstation 6.04 linux x64 unrecoverable error

Ivan Versluis June 25th, 2008

I am running Ubuntu 8.04 LTS Desktop Edition 64bit edition and after I installed VMWare Workstation 6.04 Linux x64 edition I got the following error when trying to start my virtual machines sitting on a NTFS USB disk volume.

VMware Workstation unrecoverable error: (vcpu-0)
Failed to allocate page for guest RAM!
A log file is available in “/media/USB_DATA/NET-DC-01/vmware.log”.  Please request support and include the contents of the log file.
To collect data to submit to VMware support, select Help > About and click “Collect Support Data”. You can also run the “vm-support” script in the Workstation folder directly.
We will respond on the basis of your support entitlement.

image

Please click OK and locate the vm file. Open the vmx file with nano or another text editor and add the setting below. Save the file and try to start the virtual machine again.

mainMem.useNamedFile = “FALSE”

This setting doesn’t use named-file - use for VMs on USB-disks or other slow disks
Windows: useNamedFile= “FALSE” causes memory to be backed by the host’s swap space.
Linux: useNamedFile= “FALSE” causes a hidden file to be created in a temporary directory, which is immediately deleted when you power off the VM

Failed to lock the file! VMWare virtual disk (vmdk)

Ivan Versluis March 12th, 2008

I copied one of my Windows XP virtual machine running on a VMWare Server 1.02 host locally to my workstation. After the files were copied I opened the vmx file with VMWare Workstation 6 and received the error below after trying to start the virtual machine. I made one snapshot on the VMWare Server host.

Cannot open the disk ‘C:\VM-machines\Windows XP-001\Windows XP Professional-000001.vmdk’ or one of the snapshot disks it depends on. Reason: Failed to lock the file.

 

clip_image002

Locate the virtual machine in Windows Explorer and delete any .lck folders

clip_image004

Start the virtual machine. If this fails try to Map the virtual hard disk to Z:\

clip_image006

clip_image008

I than disconnect the virtual hard disk and retried. The virtual machine boot without any problem; my snapshot was valid.

Openfiler service fails to start

Ivan Versluis February 28th, 2008

image At some point my lab Openfiler was assigned static ip address and the iSCSI target stopped to function; also it was not reachable by the web interface at tcp port id 446 anymore. Several reboots did not help to solve the problem.

What happened? The network interface configuration was changed. One of the eth config files was changed from DHCP to a static ip address.

vi /etc/sysconfig/network

[root@net-nas-01 sysconfig]# cat network
NETWORKING=yes
HOSTNAME=net-nas-01.networknet.nl
GATEWAY=192.168.100.254

vi /etc/sysconfig/network-scripts/ifcfg-eth0

[root@net-nas-01 network-scripts]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
IPADDR=192.168.100.12
BOOTPROTO=static
NETMASK=255.255.255.0
NETWORK=192.168.100.0
GATEWAY=192.168.100.254
BROADCAST=192.168.100.255
ONBOOT=yes

Openfiler service failed if you checked the services (# service –status-all). The problem is Openfiler service checks the FQDN in the hosts file located in the etc directory.

[root@net-nas-01 ~]# service openfiler –full-restart
Stopping openfiler:                                        [FAILED]
Starting openfiler:                                        [FAILED]
[root@net-nas-01 ~]# service openfiler -configtest
Usage: openfiler {start|stop|restart|condrestart|reload|status|fullstatus|graceful|help|configtest}
[root@net-nas-01 ~]# service openfiler configtest
httpd: Could not determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName
Syntax OK
[root@net-nas-01 ~]# cd /etc
[root@net-nas-01 etc]# cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost

Go and modify the hosts file. To modify the hosts file run this command –> vi /etc/hosts and make sure the FQDN names for 127.0.0.1 and the static ip address are set correct.

 

[root@net-nas-01 etc]# service openfiler –full-restart
Stopping openfiler:                                        [FAILED]
Starting openfiler:                                        [  OK  ]
[root@net-nas-01 etc]# cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1                 net-nas-01.networknet.nl
192.168.100.12            net-nas-01.networknet.nl
[root@net-nas-01 etc]#

For more information go to Openfiler website.

CactiEZ 0.30 Device Tracking Management error save failed

Ivan Versluis January 29th, 2008

After installing CactiEZ 0.30 and you start using the Device Tracking Management (MacTrack plugin) area you may receive the following error when creating new site or device.

2008-01-29_134623

Error: save Failed.

 

This error is being generated by the Cacti system because there are no tables in the Cacti database.

Login on the console or with a ssh shell and execute the following commands

cd /var/www/html/plugins/mactrack

php database_upgrade.php

2008-01-29_135443

I have couple other issues after scanning a cisco switch, which I will need to follow up on the cactiusers.org forum. The device type list is empty in the newest version of CactiEZ and you will need to populate this yourself now.