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: Catalian.out errors
5882731 modifierades för 15 År sedan.
Regular Member
Inlägg: 180
Anslutningsdatum: 2010-09-15
Senaste inlägg
I have moved a liferay 6.0.5 mySQL database onto a new machine and pointed a 6.0.6 install. This worked well and the database upgraded fine. But when I have mounted the NFS share to the new machines ( 2 machines in cluster ) Im gettinga few errors in the launch.Both are openBSD machines with mysl DB and solr installed. The first one is
The next is an error with lucene and the NFS lock. Im really clueless to either of these not sure if the 2 machines are trying access the same image or files at the same time which is causing the lock when its launched?
Will provide full logs if needed.
Any advice would be helpful thanks.
com.liferay.portal.NoSuchLayoutSetException: No LayoutSet exists with the key {groupId=0, privateLayout=false}
12:04:59,318 ERROR [IndexAccessorImpl:446] Initializing Lucene writer failed for 0
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/home/Liferay-606_v0.1/data/lucene/0/write.lock: java.io.FileNotFound$The next is an error with lucene and the NFS lock. Im really clueless to either of these not sure if the 2 machines are trying access the same image or files at the same time which is causing the lock when its launched?
Will provide full logs if needed.
Any advice would be helpful thanks.
4753419 modifierades för 15 År sedan.
Liferay Legend
Inlägg: 7942
Anslutningsdatum: 2010-03-24
Senaste inlägg
Liferay by default uses local file system for its Lucene index. I assume that you've changed Liferay to use Solr instead of Lucene. Unfortunately, it seems Liferay still goes to Lucene on startup.
How did you setup your cluster and what are you sharing with your NFS?
#
# Designate whether Lucene stores indexes in a database via JDBC, file
# system, or in RAM.
#
#lucene.store.type=jdbc
lucene.store.type=file
#lucene.store.type=ram
#
# Set this to true if you want the portal to replicate an index write across
# all members of the cluster. This is useful in some clustered environments
# where you wish each server instance to have its own copy of the Lucene
# search index. This is only relevant when using the default Lucene indexing
# engine.
#
lucene.replicate.write=false
How did you setup your cluster and what are you sharing with your NFS?
#
# Designate whether Lucene stores indexes in a database via JDBC, file
# system, or in RAM.
#
#lucene.store.type=jdbc
lucene.store.type=file
#lucene.store.type=ram
#
# Set this to true if you want the portal to replicate an index write across
# all members of the cluster. This is useful in some clustered environments
# where you wish each server instance to have its own copy of the Lucene
# search index. This is only relevant when using the default Lucene indexing
# engine.
#
lucene.replicate.write=false
5882731 modifierades för 15 År sedan.
Regular Member
Inlägg: 180
Anslutningsdatum: 2010-09-15
Senaste inlägg
I have set the 2 machines to cluster in tomcat with the ehcahing set in my portal-ext. So they are clustered fine without session replication just now.
That is my portal-ext. I do not have any setting for Lucene in there. If i am using solr what can I do to disable lucene?
jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://192.168.1.xx:3306/lportalx?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username=lportalx
jdbc.default.password=lportalx
#redirect.url.security.mode=ip
#redirect.url.ips.allowed=127.0.0.1,liferay.xxxxxx
redirect.url.security.mode=domain
redirect.url.domains.allowed=
http.proxyHost=proxyxxxx
https.proxyHost=proxyxxx
https.proxyPort=80x
http.proxyPort=80x
http.nonProxyHosts="localhost"
breadcrumb.show.parent.groups=true
breadcrumb.show.guest.group=false
net.sf.ehcache.configurationResourceName=/ehcache/hibernate-clustered.xml
ehcache.multi.vm.config.location=/ehcache/liferay-multi-vm-clustered.xml
That is my portal-ext. I do not have any setting for Lucene in there. If i am using solr what can I do to disable lucene?
4753419 modifierades för 15 År sedan.
Liferay Legend
Inlägg: 7942
Anslutningsdatum: 2010-03-24
Senaste inlägg
Try specifying different addresses on following properties on each server.
#
# Set the directory where Lucene indexes are stored. This is only referenced
# if Lucene stores indexes in the file system.
#
lucene.dir=${liferay.home}/data/lucene/
#
# FileSystemHook
#
dl.hook.file.system.root.dir=${liferay.home}/data/document_library
jcr.jackrabbit.repository.root=${liferay.home}/data/jackrabbit
#
# Set the directory where Lucene indexes are stored. This is only referenced
# if Lucene stores indexes in the file system.
#
lucene.dir=${liferay.home}/data/lucene/
#
# FileSystemHook
#
dl.hook.file.system.root.dir=${liferay.home}/data/document_library
jcr.jackrabbit.repository.root=${liferay.home}/data/jackrabbit
5882731 modifierades för 15 År sedan.
Regular Member
Inlägg: 180
Anslutningsdatum: 2010-09-15
Senaste inlägg
Mnaged to get rid of the NFS locks during boot up but this error is still appearing when trying to upload JPEG images and at other points even when just navigating pages. The logs are just exploding in volume. Nothing seems to be broken apart from being unable to upload JPEG's.
and this is the error displayed on the page when you attempt to upload a jpeg
The NFS locks were permission issues with the OS.
Thanks
William
com.liferay.portal.NoSuchLayoutSetException: No LayoutSet exists with the key {groupId=0, privateLayout=false}and this is the error displayed on the page when you attempt to upload a jpeg
java.lang.NoClassDefFoundError: com/sun/image/codec/jpeg/ImageFormatExceptionThe NFS locks were permission issues with the OS.
Thanks
William
Community
Company
Feedback