Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
After db_upgrade.sh Control Panel->Server Admin still shows 7.1.0 GA1
Hi all,
I downloaded the liferay tools for 7.1.0 GA3 copied them over to the liferay directory, edited the config files and ran the upgrade script. There was a error about the eliasticsearch6 directory not being writable but the script completed and everything looks. I have pasted the error below in case it is relevant.
When I log into liferay the version still says 7.1.0 GA1 instead of 7.1.0 GA3. Is this normal or have I done something wrong?
java.lang.IllegalStateException: failed to obtain node locks,
tried
[[/var/lib/liferay/data/elasticsearch6/indices/LiferayElasticsearchCluster]]
with lock id [0]; maybe these locations are not writable or multiple
nodes were started without incre<br> asing
[node.max_local_storage_nodes] (was [1])?<br> at
org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:244)<br>
at
org.elasticsearch.node.Node.<init>(Node.java:263)<br>
at
com.liferay.portal.search.elasticsearch6.internal.connection.EmbeddedElasticsearchNode.<init>(EmbeddedElasticsearchNode.java:48)<br>
at
com.liferay.portal.search.elasticsearch6.internal.connection.EmbeddedElasticsearchNode.lambda$newInstance$0(EmbeddedElasticsearchNode.java:41)<br>
at
com.liferay.portal.search.elasticsearch6.internal.connection.PluginJarConflictCheckSuppression.execute(PluginJarConflictCheckSuppression.java:39)<br>
at com.liferay.portal.search.elasticsearch6.internal.connection.EmbeddedElasticsearchNode.newInstance(EmbeddedElasticsearchNode.java:40)
Mark Clarke:I downloaded the liferay tools for 7.1.0 GA3 copied them over to the liferay directory, edited the config files and ran the upgrade script. There was a error about the eliasticsearch6 directory not being writable but the script completed and everything looks. I have pasted the error below in case it is relevant.
When I log into liferay the version still says 7.1.0 GA1 instead of 7.1.0 GA3. Is this normal or have I done something wrong?
I guess "copying over" the existing installation is the problem: I assume that there were jar files which are now left over from the previous version, as well as some from the new version. Also the OSGi state folder might not reflect what you actually have.
The version string on the HelloWorld portlet might come from the OSGi state folder, but it's most likely not your only problem. I'd unzip a clean version in an empty folder and start that one on the new database.
Actually, I don't think the script changes the reported version.
The only real source of what you have is the output from the patching tool's "info" command.
Hi Mark,
As Olaf and David have already pointed out, download the upgrade tool is not enough, that tool has to point to the 7.1.0 GA3 resourcers (portal-iml.jar, portal-service.jar, osgi modules, other jars, etc.)
Please, do that to be able to upgrade your 7.1.0 GA1 database to 7.1.0 GA3
I hope it helps.
Thanks all. I thought the update script would download the new version of liferay as part of its process. I have replaced the war file and lib/ext directories with the new dependencies and reran the update script. It all looks good now.
Powered by Liferay™