|
Home > Archive > WebSphere Portal Server > May 2007 > Update from 6.0 to 6.0.1 failed: unable to start up server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Update from 6.0 to 6.0.1 failed: unable to start up server
|
|
|
| I am doing the update from the 6.0 to 6.0.1, I followed every setep as the online instructions. But always get error message as followings from the details panel:
. . .
sync.DbStorageGroup=WPSSG
sync.DbTablespace=SYNCREGTBS
sync.DbType=cloudscape
sync.DbUrl=jdbc:db2j:wpsdb;create=true
sync.DbUser=db2admin
sync.DbVcat=DSN810
sync.DbVolumes=*
sync.XDbName=sync6TCP
templates.dir=C:\PROGRA~1\IBM\WEBSPH~1\PORTAL~1/config/templates
thisdir=C:/PROGRA~1/IBM/WEBSPH~1/PORTAL~1/config/DBTransfer
useDomainQualifiedUserNames=false
user.country=CN
user. dir=C:\PROGRA~1\IBM\WEBSPH~1\PORTAL~1\co
nfig
user.home=C:\Documents and Settings\JHUANG
user.install. root=C:\ibm\WebSphere\profiles\wp_profil
e
user.language=zh
user.name=jhuang
user.timezone=Australia/Sydney
user.variant=
vaultProperties=accessmanagervault.properties
vaultType=AccessManager
was.install.root=C:/Program Files/IBM/WebSphere6/AppServer
was.platform.script.ext=.bat
was.repository.root=C:/ibm/WebSphere/profiles/wp_profile/config
was.root=C:/Program Files/IBM/WebSphere6/AppServer
wmm.DataSourceName=wpdbDS
wmm.Db32KBufferPoolName=BP32K
wmm.Db4KBufferPoolName=BP0
wmm.DbName=wpsdb
wmm.DbNameOnZos=WPSTST02
wmm.DbNode=wpsNode
wmm.DbPassword=PASSWORD_REMOVED
wmm.DbSchema=
wmm.DbStorageGroup=WPSSG
wmm.DbType=cloudscape
wmm.DbUrl=jdbc:db2j:wpsdb;create=true
wmm.DbUser=db2admin
wmm.DbVcat=DSN810
wmm.DbVolumes=*
wmm.XDbName=wps6TCP
work.dir=C:/PROGRA~1/IBM/WEBSPH~1/PORTAL~1/config/work
wps.classes.dir=C:/PROGRA~1/IBM/WEBSPH~1/PORTAL~1/bin
ws.ext.dirs=C:/Program Files/IBM/WebSphere6/AppServer/java/lib;C:/Program Files/IBM/WebSphere6/AppServer/classes;C:/Program Files/IBM/WebSphere6/AppServer/lib;C:/Program Files/IBM/WebSphere6/AppServer/installedChannels;C:/Program Files/IBM/WebSphere6/AppS
erver/lib/ext;C:/Program Files/IBM/WebSphere6/AppServer/web/help;C:/Program Files/IBM/WebSphere6/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;../bin;../shared/app;
wsadminConnType=NONE
---- End dump of properties ----
BUILD FAILED
file:../config/actions/was_cfg.xml:1109: Portal Server failed to start.
Total time: 20 minutes 49 seconds
And if check the log file, find out that the reason is that server failed to start up:
2007-05-08T12:42:47+10:00 Result: [exectimeout] Timeout reached. Destroying process.
2007-05-08T12:42:47+10:00 Result: [exectimeout] Executing command: completed
2007-05-08T12:42:47+10:00 Result: [exectimeout] Return code = timedout
2007-05-08T12:42:47+10:00 Result: [echo] Return code = timedout
2007-05-08T12:42:47+10:00 Result: [echo] action-start-portal-server-service may have timed out.
2007-05-08T12:42:47+10:00 Result: [echo] Checking for server availability.
2007-05-08T12:42:47+10:00 Result: StdErr:
2007-05-08T12:42:47+10:00 Result: StdErr: BUILD FAILED
2007-05-08T12:42:47+10:00 Result: StdErr: file:../config/actions/was_cfg.xml:1109: Portal Server failed to start.
2007-05-08T12:42:47+10:00 Result: StdErr:
2007-05-08T12:42:47+10:00 Result: StdErr: Total time: 20 minutes 48 seconds
2007-05-08T12:42:47+10:00 Error 112 -- Return code (1) differs from the expected code (0).
2007-05-08T12:42:47+10:00 Validating platform for (Linux, Solaris, SunOS, AIX, HP-UX, s390)
2007-05-08T12:42:47+10:00 platform check is negative.
2007-05-08T12:42:47+10:00 Validating platform for (OS/400)
2007-05-08T12:42:47+10:00 platform check is negative.
2007-05-08T12:42:47+10:00 Processing virtual script UnConfigPTF
2007-05-08T12:42:47+10:00 Product File Update is not active; skipping update step.
2007-05-08T12:42:47+10:00 Input Jar File : C:\TEMP\ptfs\WP_PTF_601\components\wp.ptf.preconfig\update.jar
2007-05-08T12:42:47+10:00 Target Directory : C:\Program Files\IBM\WebSphere6\PortalServer
2007-05-08T12:42:47+10:00 Backup Jar File : C:\Program Files\IBM\WebSphere6\PortalServer\versio
n\backup\20070508_121157_WP_PTF_601_wp.ptf.preconfig_undo.jar
2007-05-08T12:42:47+10:00 Warnings Issued : 0
2007-05-08T12:42:47+10:00 Log File : C:\Program Files\IBM\WebSphere6\PortalServer\versio
n\log\20070508_121157_WP_PTF_601_wp.ptf.preconfig_install.log
2007-05-08T12:42:47+10:00
2007-05-08T12:42:47+10:00 Errors were noted: 1
2007-05-08T12:42:47+10:00 Extractor functionality may be compromised!
2007-05-08T12:42:47+10:00
2007-05-08T12:42:47+10:00 View the log for processing details.
2007-05-08T12:42:47+10:00 Closing Log
2007-05-08T12:42:47+10:00 Closing log file: C:\Program Files\IBM\WebSphere6\PortalServer\versio
n\log\20070508_121157_WP_PTF_601_wp.ptf.preconfig_install.log
However, the portal server is started while it takes about 30 mins to startup. Is this long time startup cause this problem, or anything else? Any help will be very appreciated.
hj
| |
|
| Can you uninstall the patch set, check that portal starts up, clear the logs and then re-attach them when you run the patch install again ?
make sure you have set your usernames and passwords for WAS and WPS (WasPassword and PortalAdminPwd) before you run the patch upgrade.
|
|
|
|
|