Wednesday, May 11, 2011

Suse ES networking problem on vmware

After restarting vmware of SES, from time to time, the network interface got changed.
As a result, the network connection would stop working.

The resolution to this issue is to manually edit /etc/udev/rules.d/70-persistent-net.rules file. This file has two entries related to network cards:


# PCI device 0x8086:0x10f5 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:ac:ee:0d:d5", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x10f5 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:ac:e0:fd:23", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

The first entry with eth0 is the original virtual machine MAC address. The second entry is the new NIC with the new MAC address.

You must change the MAC address in the first entry from eth0 to eth1 and remove the second entry.

After a reboot, the cloned virtual machine has network connectivity.

The original source of this solution is http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021624 .

Tuesday, May 03, 2011

Resolving SoapUI starting failure on Linux RedHat ES.

The binary zipfile of SoapUI would not work directly with Linux RH ES.
When the soapui.sh is executed, some error would be reported and the process aborts.
It turned out that it's a known issue, what needs to be done is uncommenting existing line in the soapui.sh script.
# JAVA_OPTS="$JAVA_OPTS -Dsoapui.jxbrowser.disable=true"

The original solution is described here:
https://www.eviware.com/forum/viewtopic.php?t=2802 .

NX: a good remote GUI for Linux

Installing and configuring NX on Linux is easy.
Step1: download all the packages including nxclient, nxnode, nxserver from the server.
Step2: (I downloaded the tar file for installation) copy those tar.gz file to /usr directory. --> the /usr directory is a requirement for installation. Otherwise, you'll get errors such as "could not create configuration file".
Step3: execute installation scripts, as described in http://www.nomachine.com/download-package.php?Prod_Id=2522.
Step4: start the server by using "nxserver --start" command.

Use NX client is also easy. You just need to download and install the NXclient on your windows machine. With the SSH credential, you should be able to access the server which has just been configured.