9.1. Installation and Configuration

9.1.1. Installation on Oracle Linux Platforms Fails Due Missing Packages
9.1.2. Configuration on Oracle Linux Platforms Fails Because the RDP Broker Cannot Be Enabled
9.1.3. Oracle VDI Configuration Is Failing to Import svc_vdadb.xml
9.1.4. Can I Try Out MySQL or Set up an Evaluation Oracle VDI Remote Database?
9.1.5. Do I Need to Configure Sun Ray Software Separately?
9.1.6. Adding a Host to a Oracle VDI Center Fails With a Sun Ray Server Software Replication Error
9.1.7. Reconfiguring Oracle VDI Fails With "Error While Configuring Database"
9.1.8. Oracle VDI Configuration Fails to Create Database Tables With Remote Windows Databases That Use UTF-8

9.1.1. Installation on Oracle Linux Platforms Fails Due Missing Packages

When you install Oracle VDI on Oracle Linux platforms, the installation script checks whether the required packages are installed on the system. If any packages are missing, Oracle VDI uses the yum command to download and install them. The installation fails if the missing packages cannot be installed, and a message is displayed that lists the missing packages, for example:

Checking for required libraries and packages...

13 packages are missing but cannot be installed because the software manager yum
 does not have access to the repositories or the repositories are invalid:
libaio-devel, sysstat, dhcp, compat-openldap, glib, libdb-4.2.so()(64bit), libXp
.so.6, /usr/lib/libaio.so, /usr/lib64/libaio.so, /usr/lib/libXpm.so, /usr/lib/li
bXm.so.3, /usr/lib/libglib-1.2.so.0, /usr/lib/libcdda_paranoia.so

Error: The software manager yum cannot install the required packages.
See the log file '/var/log/vda-install.2011_09_26_06:03:26.log' for additional i
nformation.

The required packages might not be able to be downloaded because no repositories are configured for yum, or if there are other problems, for example incorrect proxy configuration or network connectivity issues.

To resolve the installation problem, ensure that yum is configured properly and is working. Then install Oracle VDI again.

If you want to install the missing required packages manually, the packages are listed in the log file for the failed installation in /var/log.

9.1.2. Configuration on Oracle Linux Platforms Fails Because the RDP Broker Cannot Be Enabled

When you configure Oracle VDI on Oracle Linux platforms, the configuration might fail because the RDP Broker cannot be enabled. A message is displayed that lists the log file for the failed configuration in /var/log, for example:

RDP Broker Configuration
   + Registering RDP broker...
   + Starting RDP broker...
RDP Broker cannot be enabled.

Error: 
The configuration of Oracle VDI 3.4.1 has failed.

See the log file '/var/log/vda-config.2011_09_27_09:14:56.log' for additional in
formation.

Messages might also be displayed in the SELinux alert browser, if is enabled..

If this error occurs, check the log files in /opt/SUNWvda-rdpb/var/log for the following error message:

2011/09/27 09:10:00.118 Broker start
2011/09/27 09:10:00.188 ERROR:   Cannot open library VBoxRT.so:
	/opt/SUNWvda-rdpb/bin/../lib/VBoxRT.so: cannot restore segment prot afte
r reloc: Permission denied.
2011/09/27 09:10:00.188 ERROR:   RDP server init failed.
2011/09/27 09:10:00.188 Broker stop

The problem is caused by the SELinux setting for your system.

To resolve the problem:

  1. Change the SELinux setting to permissive or disabled.

    Use the SELinux Administration Tool (system-config-selinux), or the /usr/sbin/setenforce 0 command (this command changes the setting to permissive). Alternatively, edit /etc/selinux/config and change the entry SELINUX=enforcing to either SELINUX=disabled or SELINUX=permissive.

  2. Unconfigure Oracle VDI.

    You must unconfigure before you can configure Oracle VDI again.

    /opt/SUNWvda/sbin/vda-config -u
  3. Configure Oracle VDI.

    /opt/SUNWvda/sbin/vda-config

9.1.3. Oracle VDI Configuration Is Failing to Import svc_vdadb.xml

vda-config is failing to import svc_vdadb.xml because TEMP/application/database/vdadb does not get deleted. This is most commonly seen if a terminal is killed during uninstallation or configuration of Oracle VDI (vda-config/install -u), when the uninstallation/unconfiguration is run from the same Sun Ray session.

Workaround after getting the error:

  1. To recover the SVC repository's snapshot, run the following.

    # /lib/svc/bin/restore_repository
    1. When prompted with Enter Response [boot], select manifest_import instead of the default, boot.

    2. Choose the correct snapshot (manifest_import-200904??_??? - the time of backup will be in DDMMYY format).

    3. After the system reboots, check to see that svc:/TEMP/application/database/vdadb:default has been removed.

  2. Run the Oracle VDI configuration as usual.

9.1.4. Can I Try Out MySQL or Set up an Evaluation Oracle VDI Remote Database?

Yes! The MySQL Sandbox is a quick and easy way to setup MySQL or try out Oracle VDI remote database setup.

You can find it here: https://launchpad.net/mysql-sandbox.

To install a simple MySQL server just execute:

<mysql-sandbox-path>/make_sandbox <absolute-path-to-your-mysql.tar.gz>

On Oracle Solaris platforms, you might have to add /usr/sfw/bin to your path in order to make mysql_sandbox work.

More documentation about MySQL Sandbox can be found at: https://launchpad.net/mysql-sandbox

9.1.5. Do I Need to Configure Sun Ray Software Separately?

A separate installation of Sun Ray Software is not necessary because Sun Ray Software is installed and automatically set up as part of the Oracle VDI installation and configuration.

9.1.6. Adding a Host to a Oracle VDI Center Fails With a Sun Ray Server Software Replication Error

When you add a Host to a Oracle VDI Center, it might fail with the following error message:

Sun Ray Server Software Configuration
   + Configuring Sun Ray Server Software...

Error: There was an error configuring Sun Ray Server Software replication

See the log file '/var/log/vda-config.2012_04_05_16:12:43.log' for additional information.

If the log file shown in the error message contains a Signature mismatch - check configuration message, it is possible that the Sun Ray group signature has been changed using the Sun Ray administration tools. These tools do not update Oracle VDI. See Section 8.8.7, “Synchronizing the Sun Ray Group Signature and Data Store Password” for details of how to synchronize the group signature.

9.1.7. Reconfiguring Oracle VDI Fails With "Error While Configuring Database"

When you reconfigure Oracle VDI on a host, the configuration can fail with an Error While Configuring Database message and a reference to a log file for additional information.

On an Oracle VDI primary host, the log file typically contains the following:

MySQL Database Server Configuration
+ Initializing database...
...
/opt/SUNWvda/mysql/bin/mysqld: File './mysql-bin.index' not found (Errcode: 13)
110630 23:59:59 [ERROR] Aborting

110630 23:59:59 [Note] /opt/SUNWvda/mysql/bin/mysqld: Shutdown complete
...
Error: Error while configuring database.     

On an Oracle VDI secondary host, the log file typically contains the following:

MySQL Database Slave Configuration
...
+ Initializing database...
110630 23:59:59 [ERROR] Fatal error: Can't change to run as user 'vdadb' ;  
Please check that the user exists!
110630 23:59:59 [ERROR] Aborting
110630 23:59:59 [Note] /opt/SUNWvda/mysql/bin/mysqld: Shutdown complete
...
Error: Error while configuring database.   

The problem is caused by the presence of a /var/opt/SUNWvda/mysql directory, which has data from a previous Oracle VDI configuration.

To resolve this problem:

  1. Log in as root on the Oracle VDI host.

  2. Unconfigure Oracle VDI on the host.

    # /opt/SUNWvda/sbin/vda-config -u
  3. Remove the directory /var/opt/SUNWvda/mysql.

  4. Configure Oracle VDI on the host.

    # /opt/SUNWvda/sbin/vda-config

9.1.8. Oracle VDI Configuration Fails to Create Database Tables With Remote Windows Databases That Use UTF-8

On Windows platforms, MySQL limits key sizes to 767 bytes. Due to this limit, the Oracle VDI configuration process fails when using a remote MySQL database on Windows platforms that have UTF-8 enabled.

There are two possible workarounds for this issue.

  1. Modify the /etc/opt/SUNWvda/vda-schema-create.sql file on your primary Oracle VDI host and configure Oracle VDI software again.

    Change the line:

    UNIQUE INDEX distinguished_name (`distinguished_name` ASC, `ud_id` ASC) ,

    to:

    UNIQUE INDEX distinguished_name (`distinguished_name`(250) ASC, `ud_id` ASC) ,

    This workaround might cause problems assigning users to pools or desktops if the distinguished name (DN) of the user is longer than 250 characters.

  2. Change the character set of the MySQL database to latin1 and configure Oracle VDI again.

    This workaround causes problems logging in users who have UTF-8 characters in their user name.