AnsweredAssumed Answered

Error al iniciar,   reader beneath

Question asked by antoniop2 on Aug 8, 2011
Después de varias semanas haciendo pruebas con  Alfresco3.4Enterprise WCMQS, he reiniciado el servidor y SORPRESA.. Alfresco no funciona.

El servidor es un UBUNTU 10.04


En el log aparece este mensaje



……….

13:34:58,478 INFO  [org.artofsolving.jodconverter.office.OfficeProcess] profile dir '/opt/alfresco-3.4.0/tomcat/temp/.jodconverter_socket_host-127.0.0.1_port-8101' already exists; deleting
13:35:07,088 INFO  [org.alfresco.repo.management.subsystems.ChildApplicationContextFactory] Startup of 'OOoJodconverter' subsystem, ID: [OOoJodconverter, default] complete
13:35:07,474 ERROR [org.alfresco.repo.search.impl.lucene.index.IndexInfo] Failed building filter reader beneath b21359fd-cf79-432d-bf63-2f5ad22dd837
java.io.EOFException
   at java.io.DataInputStream.readInt(DataInputStream.java:375)
   at org.alfresco.repo.search.impl.lucene.index.IndexInfo.getDeletions(IndexInfo.java:1091)
   at org.alfresco.repo.search.impl.lucene.index.IndexInfo.createMainIndexReader(IndexInfo.java:2056)
   at org.alfresco.repo.search.impl.lucene.index.IndexInfo.getMainIndexReferenceCountingReadOnlyIndexReader(IndexInfo.java:1219)
   at org.alfresco.repo.search.impl.lucene.AbstractLuceneBase.getSearcher(AbstractLuceneBase.java:168)
   at org.alfresco.repo.search.impl.lucene.ADMLuceneSearcherImpl.query(ADMLuceneSearcherImpl.java:287)
   at org.alfresco.repo.search.SearcherComponent.query(SearcherComponent.java:78)
   at org.alfresco.repo.node.index.AbstractReindexComponent.isTxnIdPresentInIndex(AbstractReindexComponent.java:500)
   at org.alfresco.repo.node.index.AbstractReindexComponent.isTxnPresentInIndex(AbstractReindexComponent.java:421)
…….


He mirado el ulimit y tengo:


ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 20
file size               (blocks, -f) unlimited
pending signals                 (-i) 16382
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65000
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) unlimited
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


¿Alguna idea?

Gracias

Outcomes