1. Home
  2. Portal
  3. Upgrade from 6.1.1 CE to 7.1.2 GA3. Internal Server Error

Upgrade from 6.1.1 CE to 7.1.2 GA3. Internal Server Error

Jamie Sammons, modified 3 Years ago.
Upgrade from 6.1.1 CE to 7.1.2 GA3. Internal Server Error
New Member Post: 1 Join Date: 5/8/22 Recent Posts

Hi,

I am about to update an old 6.1.1 CE-installation to the latest version with the intermediate step (7.1.2 GA3) as suggested by the help page and need a little help to figure out how to overcome some difficulties I am currently facing.
Setup: tomcat 9.0.10 (from the bundle) with OpenJDK 1.8.0_332 and Postgresql 10.20

portal-ext.properties:

jdbc.default.driverClassName=org.postgresql.Driver
jdbc.default.url=jdbc:postgresql://localhost:5432/...
jdbc.default.username=..
jdbc.default.password=...
dl.store.impl=com.liferay.portal.store.file.system.FileSystemStore
#setup.wizard.enabled=false
password.encryption.algorithm.legacy=SHA

app-server.properties:

dir=...\tomcat-9.0.10
extra.lib.dirs=/bin
global.lib.dir=/lib
portal.dir=/webapps/ROOT
server.detector.server.id=tomcat

portal-upgrade-database.properties:
 

jdbc.default.driverClassName=org.postgresql.Driver
jdbc.default.url=jdbc:postgresql://localhost:5432/..
jdbc.default.username=...
jdbc.default.password=..


portal-upgrade-ext.properties: 

liferay.home=../../
module.framework.bas.dir=../../osgi

com.liferay.portal.search.configuration.IndexStatusManagerConfiguration.config:

indexReadOnly="true"

 

The db_update-script finishes with minor warnings: 

[default-2][BaseDB:487] ERROR: Index »ix_8db864a9« does not exist: drop index IX_8DB864A9;_ [Sanitized]
[main][UpgradeProcess:447]Attempting to upgrade table LayoutBranch by recreating the table due to: ERROR: Column »layoutbranchid« of relation »layoutbranch« already exists.
​​​​​​​[Elasticsearch initialization thread][EmbeddedElasticsearchConnection:288] Liferay is configured to use embedded Elasticsearch as its search engine. Do NOT use embedded Elasticsearch in production. Embedded Elasticsearch is useful for development and demonstration purposes. Refer to the documentation for details on the limitations of embedded Elasticsearch. Remote Elasticsearch connections can be configured in the Control Panel.

The tomcat does start just fine, however when I push the "Finish Configuration"-button on the “Basic Configuration”-page, that shows when the tomcat starts automatically, the only thing that shows up is

Sadly the tomcat-log does not give any useful information, but “ERROR [http-nio-8080-exec-1][status_jsp:872] null”

Have someone faced similar issues and can point me in to the right direction?

Thx.

upgrade