Solaris Express Developer Edition Web Stack Release Notes

Chapter 1 Web Stack Release Notes

This release notes describes configuration and runtime issues and bugs that are known to be problems in the current release. Issues listed in this release notes apply to components Apache HTTP, PHP, Ruby on Rails, Squid, , MySQL and PostgreSQL. Issues include information that you should know about, including prerequisites, tips, and troubleshooting hints.

This document contains the following sections:

What's New in This Release

For information on what's new in this release, see Chapter 1, What’s New in Solaris Express, in Solaris Express Developer Edition What’s New

Systems Requirements for Web Stack

For information on system requirements, see System Requirements in Solaris Express Developer Edition Installation Guide: Laptop Installations

Getting Started with Web Stack

For information on how to get started with web stack, see Chapter 2, Getting Started, in Web Stack Getting Started Guide.

Known Issues in Web Stack

This section lists the important known issues and limitations at the time of SXDE 01/08 release.

Table 1–1 Known Issues in SXDE 01/08 release

Problem ID 



Starting apache22 (Apache 2.2 SMF service) with server_type=worker and enable_bit=true launches 64 bit prefork.


Add the following line to the /usr/apache2/2.2/bin/isainfo/envvars file.

if [ -f /etc/apache2/2.2/envvars ]; then
. /etc/apache2/2.2/envvars

where the value of isainfo parameter can amd64 or sparc


Apache SSL default configuration file is not compatible with Nevada. 


Unable to start Apache 64 bit mode on 32 bit architecture. 


When you initialize the Web Stack Admin as a root user, the Web application development options window displays the Start Servers button, which should be the Stop Servers button.


Upgrade Apache HTTP Server 1.3.0 to Apache HTTP Server 1.3.41 as there are cross-site scripting (XSS) vulnerability in the mod_imap module.


The rbconfig.rb file contains invalid paths and requires a C compilation.


Compilation/configuration of the new apache module with apxs fails.


Upgrading to Apache 2.0 to 2.2 fails. 


Apache service fails to start. 


Rename ssl.conf to ssl.conf.example. This file is present in the following location: /etc/apache2/2.2/conf.d/.


Upgrade Apache 2.2.x to 2.2.8 in order to fix security vulnerabilities. 


Upgrading of Apache 2.0 to 2.2 fails. 


The Order command with storage_engine=archive fails.


The post-installation script does not jump start.  


Apache 1.3 Webapp module is unable to communicate with Tomcat 5.5 in Nevada. 


SMF service for MySQL and Apache do not have a description in the user interface. 


Ruby installs soft links to its versioning directories. 


Ruby displays GPLv2 text in upgrade_log.


Gem installs content into /usr directory, which is a read only directory.


Default index.html does not have sufficient information/content.


Package dependencies are missing in Ruby. 


Add the following packages to Ruby: 

  • SUNWlibms

  • SUNWopenssl-libraries

  • SUNWTk

  • SUNWTcl

  • SUNWxwrtl

  • SUNWxwplt

  • SUNWzlib

Change the Ruby directory structure from/usr/local/bin/ruby to /usr/bin/ruby


RPATH and RUNPATH fail in PHP .


Apache parent process creates the semaphore and the child process inherits the semaphore ids. The semaphore gets destroyed when the child process exits. 


PHP and CGI tests fail while using the delivered php.ini.


SUNWphp524-mysql / SUNWphp524-pgsql has packaging issues.


PHP should restrict the environment variables from being set programmatically. 


Remove all the references of MySQL 4.0 from the source. 


SUNWmysql5/SUNWmysql5u has packaging issues.


MySQL attempts to write into /usr, which is a read only directory.


RUNPATH and RPATH errors are encountered in the SUNWmysql5u package.


Add MySQL manage property to MySQL SMF. This allows the non-root users to manage MySQL SMF. 


My SQL SMF should test for the existence of MySQL/MySQL user and group. 


The ri (Ruby interactive) command, which lists documentation for all Ruby classes that do not work with Ruby in Nevada.


Dependency problems exist in SUNWapchd/SUNWapchr/SUNWapchu in Nevada and Solaris 10 update 1 release.


The Ruby man pages are not linked from the /usr/share/man directory.


The Getting Started Guide is only visible after Web Stack admin initialization. 


MySQLtest fails due to bad reference file. 


MySQL user exists at Web Stack Admin initialization and generates error in logs. 


The Web Stack Getting Started guide needs update. 


For updated information, see http://docsview.sfbay/coll/1792.1


MySQL module integrated with PHP is incorrectly linked to 4.0 version of MySQL client. 


create the following symbolic link 

ln -sf /usr/mysql/5.0/lib/mysql/ /usr/mysql/5.0/lib/mysql/ 

No ID 

The default Web Stack Admin initialization script configures MySQL database with super user privileges and with no password assigned.


The most important steps in securing MySQL is to change the database administrator's password, which is empty by default. 

Ensure that MySQL is running and execute the following command: 

chrootuid /chroot/mysql mysql /usr/local/mysql/libexec/mysqld &.

Run the following command to change password: 

/usr/local/mysql/bin/mysql -u root
mysql> SET PASSWORD FOR root@localhost=PASSWORD('new_password');

How to Report Problems and Provide Feedback

If you have problems with Solaris Express Developer Edition, contact Sun customer support using one of the following mechanism:

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Send your comments to Sun using the "Send comments" link at:

Please include identifying information with your comments, such as the part number and the title of the book.

Additional Sun Resources

Useful Sun Java Systems information can be found at the following locations:

Searching Sun Product Documentation

Besides searching Sun product documentation from the web site, you can use a search engine of your choice by typing the following syntax in the search field:


For example, to search for "Solaris Express", type the following:

Solaris Express

To include other Sun web sites in your search (for example,,,, use in place of docs.sun.comin the search field.