|Oracle® VM Template Builder Installation and User's Guide
Part Number E14391-01
This Appendix contains troubleshooting information for Oracle VM Template Builder and contains:
The Oracle VM Template Builder guest virtual machine opens the httpd and sshd ports. These are required to be open to access the web-based user interface and to log in remotely to the command-line shell, respectively.
If you can access the Oracle VM Template Builder web interface, but cannot perform template builds, make sure both the Oracle VM Template Builder service, and the web server service are started.
The Oracle VM Template Builder service (ovmtb) starts the daemon which performs the template builds. The ovmtb service is separate to the web server (httpd) service, which serves up the Oracle VM Template Builder user interface. You must have both the ovmtb and httpd services running to build templates in Oracle VM Template Builder. See Section 2.8, "Starting and Stopping Oracle VM Template Builder" for information on how to start the services.
The template build log file is, by default, located in:
If you must reset Oracle VM Template Builder to the initial setup, use the ovmtb-reconfig.sh script. As the root user, enter
Oracle VM Template Builder is reset back to the initial installation configuration settings.
This section describes the known issues in Oracle VM Template Builder and any known workarounds. The known issues are:
There is no online help provided in this release of Oracle VM Template Builder. Online help will be provided in future releases.
The Oracle VM Template Builder admin user's email address may fail to receive emails if you have installed Oracle VM Template Builder on to a guest virtual machine which uses DHCP to obtain an IP address.
Workaround: Modify the Oracle VM Template Builder email configuration settings and restart Oracle VM Template Builder and sendmail:
Modify the /var/www/html/ovmtb/setting.py file to contain the host name of the guest virtual machine on which Oracle VM Template Builder is installed. For example, if the email address is email@example.com on host.example.com, enter:
Restart Oracle VM Template Builder and sendmail:
# service ovmtb stop # service httpd stop # /etc/init.d/sendmail restart # service httpd start # service ovmtb start
The following error may be displayed when building a template:
... Mounting VM image... ERROR: losetup error - Please check the log (/var/log/modifyjeos.log) file! ERROR creating JeOS image files...
This error may occur when multiple templates are being built at the same time and all available loop devices are in use. If all loop devices are in use, Oracle VM Template Builder is unable to mount the disk image files, so cannot complete the build process.
Workaround: Modify the number of loop devices on the system by adding the following line to the /etc/modprobe.conf file and restarting the operating system.
options loop max_loop=64
The template build progress percentage displayed in the Template Projects table on the Template Projects screen, and in the template build log pages does not accurately display the time remaining for a template build. Depending on the configuration of the template, certain steps in the build process may take some time to complete while others may complete quickly.
Care should be taken when changing the parameters in the Oracle VM Template Builder configuration file, /var/www/html/ovmtb/settings.py. Changing the values in this file may result in failed builds, the inability to access completed builds from the web user interface, and SuspiciousOperation exceptions within the application. If more file system space is needed to hold the builds, it is recommended that you retain the default configuration parameters and, instead, add a new disk to the Oracle VM Template Builder guest virtual machine. To customize the guest virtual machine, see Section 2.9, "Customizing the Oracle VM Template Builder Guest Virtual Machine".
Future releases of the Oracle VM Template Builder will allow more fine grained control over the configuration settings.
Only one additional disk image is included in a template, even if multiple additional disks are requested to be included using the template build wizard.
Workaround: Edit the template configuration file (vm.cfg) to include the additional disks.