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
RE: Some Liferay services are unavailable after upgrading from 6.2 to 7.1
Hi,
after a (almost) succesful upgrade from 6.2 to 7.1 with the latest liferay studio (3.3.1 I think), we started the server and we were missing some menu entries like categories, DDLs etc. Running "diag" in gogo shell, the modules are started, but with "dm na" we have a lot of unaailable services:
g! dm na<br> [71]
com.liferay.asset.category.property.service<br> [42]
com.liferay.portal.spring.extender.internal.context.ModuleApplicationContextRegistrator
unregistered<br> com.liferay.asset.util.AssetHelper service
required unavailable<br> [122]
com.liferay.layout.page.template.service<br> [48]
com.liferay.portal.spring.extender.internal.context.ModuleApplicationContextRegistrator
unregistered<br>
com.liferay.dynamic.data.mapping.service.DDMStructureLinkLocalService
service required unavailable<br> [228]
com.liferay.dynamic.data.lists.service<br> [52]
com.liferay.portal.spring.extender.internal.context.ModuleApplicationContextRegistrator
unregistered<br>
com.liferay.dynamic.data.mapping.service.DDMStructureLinkLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMStructureLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMStructureVersionLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.storage.StorageEngine service
required unavailable<br> [311] com.liferay.journal.service<br>
[56]
com.liferay.portal.spring.extender.internal.context.ModuleApplicationContextRegistrator
unregistered<br>
com.liferay.dynamic.data.mapping.service.DDMStorageLinkLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMStructureLinkLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMStructureLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMTemplateLinkLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMTemplateLocalService
service required unavailable<br> [427]
com.liferay.dynamic.data.mapping.service<br> [19]
com.liferay.portal.spring.extender.internal.configuration.ServiceConfigurationInitializer
unregistered<br> com.liferay.portal.kernel.model.Release
(&(release.bundle.symbolic.name=com.liferay.dynamic.data.mapping.service)(&(release.schema.version>=2.0.0)(!(release.schema.version>=2.1.0)))(|(!(release.state=*))(release.state=0)))
service required unavailable<br> [62]
com.liferay.portal.spring.extender.internal.context.ModuleApplicationContextRegistrator
unregistered<br> com.liferay.portal.kernel.model.Release
(&(release.bundle.symbolic.name=com.liferay.dynamic.data.mapping.service)(&(release.schema.version>=2.0.0)(!(release.schema.version>=2.1.0)))(|(!(release.state=*))(release.state=0)))
service required unavailable<br>
com.liferay.portal.kernel.configuration.Configuration
(&(configuration.bundle.symbolic.name=com.liferay.dynamic.data.mapping.service)(name=portlet))
service required unavailable<br>
com.liferay.portal.kernel.configuration.Configuration
(&(configuration.bundle.symbolic.name=com.liferay.dynamic.data.mapping.service)(name=service))
service required unavailable<br> [910]
com.liferay.portal.workflow.kaleo.forms.service<br> [81]
com.liferay.portal.spring.extender.internal.context.ModuleApplicationContextRegistrator
unregistered<br>
com.liferay.dynamic.data.lists.service.DDLRecordLocalService service
required unavailable<br>
com.liferay.dynamic.data.lists.service.DDLRecordService service
required unavailable<br>
com.liferay.dynamic.data.lists.service.DDLRecordSetLocalService
service required unavailable<br>
com.liferay.dynamic.data.lists.service.DDLRecordSetService service
required unavailable<br>
com.liferay.dynamic.data.lists.service.persistence.DDLRecordPersistence
service required unavailable<br>
com.liferay.dynamic.data.lists.service.persistence.DDLRecordSetPersistence
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMTemplateLinkLocalService
service required unavailable<br> [937]
com.liferay.screens.service<br> [83]
com.liferay.portal.spring.extender.internal.context.ModuleApplicationContextRegistrator
unregistered<br>
com.liferay.asset.publisher.util.AssetPublisherHelper service
required unavailable<br>
com.liferay.dynamic.data.lists.service.DDLRecordLocalService service
required unavailable<br>
com.liferay.dynamic.data.lists.service.DDLRecordService service
required unavailable<br>
com.liferay.dynamic.data.lists.service.persistence.DDLRecordPersistence
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMStructureVersionLocalService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.DDMStructureVersionService
service required unavailable<br>
com.liferay.dynamic.data.mapping.service.persistence.DDMStructureVersionPersistence
service required unavailable<br>
com.liferay.journal.service.JournalArticleLocalService service
required unavailable<br>
com.liferay.journal.service.JournalArticleResourceLocalService
service required unavailable<br>
com.liferay.journal.service.JournalArticleService service required
unavailable<br>
com.liferay.journal.service.persistence.JournalArticlePersistence
service required unavailable<br>
com.liferay.journal.service.persistence.JournalArticleResourcePersistence
service required unavailable
In the boot logs there are no exceptions, but if we go, for example at the system settings, we get a NPE in some view.jsp, I suppose because the needed service is null (we will check it with the sources).
Is it a common error in the upgrade process?
Thank you in advance,
Harry
Hi Charalampos,
When you get this:
com.liferay.portal.kernel.model.Release (&(release.bundle.symbolic.name=com.liferay.dynamic.data.mapping.service)(&(release.schema.version>=2.0.0)(!(release.schema.version>=2.1.0)))(|(!(release.state=*))(release.state=0))) service required unavailable
It means that the DDM Service was not upgraded properly, please, check the upgrade.log to know waht happened. You can also execute upgrade:check in the Gogo Shell to verify in which point this process stopped. If you don't get any clue, check the Release_ record for that module and verify the state and schema version.
Please, don't startup the server until this module is upgrade completely since several other modules depend on this (Journal, DDL, Assets, etc.) and you will miss a lot of funcionalities.
I hope it helps.
Hi Alberto,
the upgrade process ends successfully every time we try it out. The only exceptions we get has to do with some structures and some files from the D&M that don't exist in the data folder. In the Release_ table, the portal module is verified (has the value 1). The DDM module was not verified. I can give you some more info related to this table and the problems in the migrations log file, if this could help...
Hi Charalampos,
It seems that DDM Service Upgrade or Verify process failed silently, which is the value for the state field for the Release_ record of that module? Please, attach the whole record here.
Thanks.
Hi Alberto,
here a screenshot of the table:
Hi Charalampos,
The upgrade for DDM Service run succesfully but the verify process after that failed (state 2 means that). Could you attach the fragment of the log where the DDMServiceVerifyProcess failed? If you don't have it, please set state_ as 0 and run the db upgrade tool again.
Best regards.
Hi Alberto,
it seems there is a field "Importance" which causes the problem, but what should we do about it? Its part of the implementation, we cannot remove it... Is it perhaps because of the locales? Sometimes locales causes problems. The default locale is "el_GR" and the secondary is "en_US" in both isntallations 6.2 and 7.1.
I attached four files:
- Importance_field_error.txt: the error of the importance
- NoSuchStructureVersionException.txt: another error from the migration
- news-general-structure_text.xml: the structure which contains the importance field
- result_after_migration_of_core.txt: This file contains some instructions from the end of the migration
After some research we found that the problem was in a translation of the structure:
<meta-data locale="en_US"> <entry
name="label"> <![CDATA[0]]> </entry> </meta-data>
The structure had only the greek language as available locales, and the Importance had also the "en_US". We cleaned up the additional translation and the db migration worked...
Powered by Liferay™