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: Caused by: com.liferay.portal.lpkg.deployer.LPKGVerifyException:
Hi All,We are getting below error in Liferay CE 7.1 and this creates cron job (kinsing) which utilize our CPU to 100%. Any solution for this?Caused by: com.liferay.portal.lpkg.deployer.LPKGVerifyException: Existing LPKG bundle Liferay CE Collaboration - Liferay CE Flags - API_1.0.0 [881] has the same symbolic name and version as LPKG file /data/liferay-ce-portal-7.1.0-ga1/osgi/marketplace/Liferay CE Collaboration - Liferay CE Flags - API.lpkg
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGVerifier.verify(DefaultLPKGVerifier.java:117)
... 190 more
2020-04-29 09:54:50.620 ERROR [Start Level: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][DefaultLPKGDeployer:476] Unable to deploy LPKG file /data/liferay-ce-portal-7.1.0-ga1/osgi/marketplace/Liferay CE Foundation - Liferay CE Security SSO - API.lpkg
com.liferay.portal.lpkg.deployer.LPKGVerifyException: com.liferay.portal.lpkg.deployer.LPKGVerifyException: Existing LPKG bundle Liferay CE Foundation - Liferay CE Security SSO - API_1.0.0 [621] has the same symbolic name and version as LPKG file /data/liferay-ce-portal-7.1.0-ga1/osgi/marketplace/Liferay CE Foundation - Liferay CE Security SSO - API.lpkg
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGVerifier.verify(DefaultLPKGVerifier.java:127)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer.deploy(DefaultLPKGDeployer.java:118)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer._instalLPKGs(DefaultLPKGDeployer.java:467)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer._activate(DefaultLPKGDeployer.java:350)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer.activate(DefaultLPKGDeployer.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)Caused by: com.liferay.portal.lpkg.deployer.LPKGVerifyException: Existing LPKG bundle Liferay CE Foundation - Liferay CE Security SSO - API_1.0.0 [621] has the same symbolic name and version as LPKG file /data/liferay-ce-portal-7.1.0-ga1/osgi/marketplace/Liferay CE Foundation - Liferay CE Security SSO - API.lpkg
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGVerifier.verify(DefaultLPKGVerifier.java:117)
... 190 more
2020-04-29 09:54:50.632 INFO [Start Level: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][BundleStartStopLogger:35] STARTED org.apache.felix.dependencymanager.shell_3.2.0 [50]
2020-04-29 09:54:50.633 INFO [Start Level: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][BundleStartStopLogger:35] STARTED com.liferay.util.taglib_3.1.3 [1049]
2020-04-29 09:54:50.666 INFO [Refresh Thread: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][BundleStartStopLogger:38] STOPPED com.liferay.portal.osgi.web.servlet.jsp.compiler_3.0.1 [43]
/kinsing-773302304
2020-04-29 09:54:51.303 WARN [http-nio-8080-exec-29][ReferenceIndirector:223] Failed to acquire the Context necessary to lookup an Object.
javax.naming.NamingException: Could not resolve Reference to Object! [Root exception is java.lang.ClassCastException: LifExp cannot be cast to javax.naming.spi.ObjectFactory]
at com.mchange.v2.naming.ReferenceableUtils.referenceToObject(ReferenceableUtils.java:103)
at com.mchange.v2.naming.ReferenceIndirector$ReferenceSerialized.getObject(ReferenceIndirector.java:118)
at com.mchange.v2.ser.SerializableUtils.fromByteArray(SerializableUtils.java:125)
at com.mchange.v2.c3p0.impl.C3P0ImplUtils.parseUserOverridesAsString(C3P0ImplUtils.java:318)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource$1.vetoableChange(WrapperConnectionPoolDataSource.java:110)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:375)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:271)
at com.mchange.v2.c3p0.impl.WrapperConnectionPoolDataSourceBase.se…
Awaiting for reply
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGVerifier.verify(DefaultLPKGVerifier.java:117)
... 190 more
2020-04-29 09:54:50.620 ERROR [Start Level: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][DefaultLPKGDeployer:476] Unable to deploy LPKG file /data/liferay-ce-portal-7.1.0-ga1/osgi/marketplace/Liferay CE Foundation - Liferay CE Security SSO - API.lpkg
com.liferay.portal.lpkg.deployer.LPKGVerifyException: com.liferay.portal.lpkg.deployer.LPKGVerifyException: Existing LPKG bundle Liferay CE Foundation - Liferay CE Security SSO - API_1.0.0 [621] has the same symbolic name and version as LPKG file /data/liferay-ce-portal-7.1.0-ga1/osgi/marketplace/Liferay CE Foundation - Liferay CE Security SSO - API.lpkg
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGVerifier.verify(DefaultLPKGVerifier.java:127)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer.deploy(DefaultLPKGDeployer.java:118)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer._instalLPKGs(DefaultLPKGDeployer.java:467)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer._activate(DefaultLPKGDeployer.java:350)
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGDeployer.activate(DefaultLPKGDeployer.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)Caused by: com.liferay.portal.lpkg.deployer.LPKGVerifyException: Existing LPKG bundle Liferay CE Foundation - Liferay CE Security SSO - API_1.0.0 [621] has the same symbolic name and version as LPKG file /data/liferay-ce-portal-7.1.0-ga1/osgi/marketplace/Liferay CE Foundation - Liferay CE Security SSO - API.lpkg
at com.liferay.portal.lpkg.deployer.internal.DefaultLPKGVerifier.verify(DefaultLPKGVerifier.java:117)
... 190 more
2020-04-29 09:54:50.632 INFO [Start Level: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][BundleStartStopLogger:35] STARTED org.apache.felix.dependencymanager.shell_3.2.0 [50]
2020-04-29 09:54:50.633 INFO [Start Level: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][BundleStartStopLogger:35] STARTED com.liferay.util.taglib_3.1.3 [1049]
2020-04-29 09:54:50.666 INFO [Refresh Thread: Equinox Container: 00a3005b-d189-001a-1d6d-d1ad277304d5][BundleStartStopLogger:38] STOPPED com.liferay.portal.osgi.web.servlet.jsp.compiler_3.0.1 [43]
/kinsing-773302304
2020-04-29 09:54:51.303 WARN [http-nio-8080-exec-29][ReferenceIndirector:223] Failed to acquire the Context necessary to lookup an Object.
javax.naming.NamingException: Could not resolve Reference to Object! [Root exception is java.lang.ClassCastException: LifExp cannot be cast to javax.naming.spi.ObjectFactory]
at com.mchange.v2.naming.ReferenceableUtils.referenceToObject(ReferenceableUtils.java:103)
at com.mchange.v2.naming.ReferenceIndirector$ReferenceSerialized.getObject(ReferenceIndirector.java:118)
at com.mchange.v2.ser.SerializableUtils.fromByteArray(SerializableUtils.java:125)
at com.mchange.v2.c3p0.impl.C3P0ImplUtils.parseUserOverridesAsString(C3P0ImplUtils.java:318)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource$1.vetoableChange(WrapperConnectionPoolDataSource.java:110)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:375)
at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:271)
at com.mchange.v2.c3p0.impl.WrapperConnectionPoolDataSourceBase.se…
Awaiting for reply
Stop Liferay, then delete the liferay/osgi/state folder. It is the work directory of osgi an will be rebuild when you start the server. Then please check the osgi subdirectories for duplicates. Look especially for "Liferay CE Foundation - Liferay CE Security SSO - API.lpkg".
If there are two of them, diff them to check if they are identical. If the are the same, just move one of them away. If they are different, you need to unpack them and check the versions. Maybe compare them to the original package in the Liferay bundle zip file.
Then start the server again.
If there are two of them, diff them to check if they are identical. If the are the same, just move one of them away. If they are different, you need to unpack them and check the versions. Maybe compare them to the original package in the Liferay bundle zip file.
Then start the server again.
thanks for replying me....i doing as per your reply but when i removed osgi of state folder then my site was not loading and it give me internal server error....
Can you paste the first exception here? Do you have some custom modules deployed?
Christoph Rabel:
The question is long solved on one of the many crossposts of this question. Keyword is "kinsing", you'll need to patch your installation. Read recent security announcements, and search for it on slack (where this question was crossposted and answered).
Can you paste the first exception here? Do you have some custom modules deployed?
@Pratik: Don't crosspost. This generates duplicate work, as demonstrated here.
We have liferay 7.1.0-ga1 with tomcat 9.0.6we have observed the malware in the same with the name kinsing created.
File always created in /tomcat/bin directory of the liferay.Location of the file is : liferay-ce-portal-7.1.0-ga1/tomcat-9.0.6/bin/
Filename format: kinsing
Actual file created as/data/liferay-ce-portal-7.1.0-ga1/tomcat-9.0.6/bin/kinsing495435542as well as
/var/tmp/kinsing
File always created in /tomcat/bin directory of the liferay.Location of the file is : liferay-ce-portal-7.1.0-ga1/tomcat-9.0.6/bin/
Filename format: kinsing
Actual file created as/data/liferay-ce-portal-7.1.0-ga1/tomcat-9.0.6/bin/kinsing495435542as well as
/var/tmp/kinsing
pratik joshi:
Did you read the recent security announcements and search for the keyword on slack?
We have liferay 7.1.0-ga1 with tomcat 9.0.6
What you posted here today informs us that you've been hit by that malware, what it doesn't contain is a question. And the answer to a prospective question could be found within the referenced resources. You'll need to patch your system. Ideally rebuild a clean system - Slack contains a few instructions on how to clean up your system. However, as you can't trust a system that has been hit by malware, the safe thing is to restore from clean backup to a new system.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™