APAR status |
Closed as fixed if next.
| Error description
.
To recreate:
Insert WAS 3.5 install CD for Solaris.
Go to /cdrom/adv_sun_128/spool
Run WebSphereInstallSun.sh
.
Choose installation type 2 (Custom)
Directory to which WebSphere will be installed is /opt
Directory where the WebSphere install packages are located is
/cdrom/adv_sun_128/spool
Security information is specific to the machine you are working
on.
.
A table of WebSphere Install Packages will appear. Three items
are checked as default (items 1,2, and 7). Deselect item 7
(WebServer Plugins). The only items remaining should be 1 and 2.
.
Database type is number 1 (DB2).
Database name is was
database home directory is /opt/IBMdb2/v6.1
user name for DB2 instance is db2inst1
password is db2inst1
WebSphere will use the URL jdbc:db2:was to access DB2.
.
Save configuration is N
.
Press enter to begin the installation. You will see the
following:To recreate:Insert WAS 3.5 install CD for Solaris.Go to /cdrom/adv_sun_128/spoolRun WebSphereInstallSun.sh.Choose installation type 2 (Custom)Directory to which WebSphere will be installed is /optDirectory where the WebSphere install packages are located is/cdrom/adv_sun_128/spoolSecurity information is specific to the machine you are workingon..A table of WebSphere Install Packages will appear. Three itemsare checked as default (items 1,2, and 7). Deselect item 7(WebServer Plugins). The only items remaining should be 1 and 2..Database type is number 1 (DB2).Database name is wasdatabase home directory is /opt/IBMdb2/v6.1user name for DB2 instance is db2inst1password is db2inst1WebSphere will use the URL jdbc:db2:was to access DB2..Save configuration is N.Press enter to begin the installation. You will see the
.
Check the log file at /tmp/WebSphere.instl
A copy of the configuration file was made and is located at
/opt/IBMWebAS/bin/admin.config.bak
A backup of the file is made and is located at
/opt/IBMWebAS/bin/startupServer.sh.bak
A copy of the configuration file was made and is located at
/opt/IBMWebAS/properties/initial_setup.config.bak
./WebSphereInstallSUN.sh[1047]: 24107 Segmentation Fault
A copy of the /opt/IBMWebAS/properties/sas.server.props file was
made and is located at
/opt/IBMWebAS/properties/sas.server.props.bak
A copy of the /opt/IBMWebAS/properties/sas.client.props file was
made and is located at
/opt/IBMWebAS/properties/sas.client.props.bak
Installation of WebSphere completed
Check the /tmp/WebSphere.instl log file for errors
# exit
.
The Segmentation Fault error is on the 8th line above.
.
NOTE: This error does NOT occur when the WebServer Plugin is
selected for WebSphere Install Packages. If the default install
packages are accepted (items 1, 2, and 7), the installation
completes successfully.
.
I do not know if the WebServer Plugin is required for a native
install. This customer did not want the plugin installed, only
the application server, administration server, and the console.
But even if the plugin is required, the script should not throw
a segmentation error, it should give a meaningful message.
.
I recreated this problem, and I've placed a copy of the screen
output showing all questions and my responses in
wasdoc0\wasus\reichca\segerr.txt. following:.Check the log file at /tmp/WebSphere.instlA copy of the configuration file was made and is located at/opt/IBMWebAS/bin/admin.config.bakA backup of the file is made and is located at/opt/IBMWebAS/bin/startupServer.sh.bakA copy of the configuration file was made and is located at/opt/IBMWebAS/properties/initial_setup.config.bak./WebSphereInstallSUN.sh[1047]: 24107 Segmentation FaultA copy of the /opt/IBMWebAS/properties/sas.server.props file wasmade and is located at/opt/IBMWebAS/properties/sas.server.props.bakA copy of the /opt/IBMWebAS/properties/sas.client.props file wasmade and is located at/opt/IBMWebAS/properties/sas.client.props.bakInstallation of WebSphere completedCheck the /tmp/WebSphere.instl log file for errors# exit.The Segmentation Fault error is on the 8th line above..NOTE: This error does NOT occur when the WebServer Plugin isselected for WebSphere Install Packages. If the default installpackages are accepted (items 1, 2, and 7), the installationcompletes successfully..I do not know if the WebServer Plugin is required for a nativeinstall. This customer did not want the plugin installed, onlythe application server, administration server, and the console.But even if the plugin is required, the script should not throwa segmentation error, it should give a meaningful message..I recreated this problem, and I've placed a copy of the screenoutput showing all questions and my responses inwasdoc0\wasus\reichca\segerr.txt. Local fix
The workaround given the customer was to perform the install and
choose the plugin. This will not affect what they are trying to
do, it just means they have something extra installed
that they may not need or use. Problem summary
This is a 3.5 CD issue. The defect will be held open
and fixed if there is to be a reship of 3.5 on CD. Problem conclusionTemporary fixComments
APAR information | APAR number | PQ51391 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED FIN | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-08-10 | Closed date | 2001-08-22 | Last modified date | 2001-08-22 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels | R350 PSY | UP |
|