topic Severe Solr install problems in Alfresco Archive

Severe Solr install problems

sjordi — Fri, 04 May 2012 14:24:53 GMT

Hi,I'm trying to install Alfresco 4.01 Enterprise in my test VM under CentOS 6 64-bit.Alfresco 3 went smoothly, but I can't find a way to have 4.x up and running.The install went all by default except I'm using MySQL and passed it the MySQL jdbc and drivers instead of PostGrWhen tomcat starts, it bu

Re: Severe Solr install problems

mrogers — Fri, 04 May 2012 14:47:39 GMT

You have various errors like java.net.BindException: Address already in use <null>:8080 so it looks like you already have something running.

Re: Severe Solr install problems

sjordi — Sun, 06 May 2012 07:50:07 GMT

Ok,
I'll check this once back at work.
Should be the problem, but I don't know what would listen to 8080, it's a "naked" Linux machine.
A good "lsof" will tell me :shock:

Re: Severe Solr install problems

bisana — Sun, 06 May 2012 12:34:28 GMT

SEVERE: Error initializing endpoint
java.net.BindException: Address already in use <null>:8080
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:549)

You need to kill the other process

ps aux | grep tomcat
ps aux | grep alf

Kill the process, restart the alfresco, check the catalina.out using "tail -f " and give feedback
thanks

Re: Severe Solr install problems

sjordi — Mon, 07 May 2012 07:07:38 GMT

both ps aux return

/opt/alfresco/current/java/bin/java -Djava.util.logging.config.file=/opt/alfresco/current/tomcat/conf/logging.properties -XX:MaxPermSize=512m -Xms128m -Xmx1024m -XX:-DisableExplicitGC -Djava.awt.headless=true -Dalfresco.home=/opt/alfresco/current -Dcom.sun.management.jmxremote -Dsun.security.ssl.allowUnsafeRenegotiation=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/opt/alfresco/current/tomcat/endorsed -classpath /opt/alfresco/current/tomcat/bin/bootstrap.jar -Dcatalina.base=/opt/alfresco/current/tomcat -Dcatalina.home=/opt/alfresco/current/tomcat -Djava.io.tmpdir=/opt/alfresco/current/tomcat/temp org.apache.catalina.startup.Bootstrap start

netstat -vat returns

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 *:8009                      *:*                         LISTEN
tcp        0      0 *:mysql                     *:*                         LISTEN
tcp        0      0 *:52429                     *:*                         LISTEN
tcp        0      0 *:webcache                  *:*                         LISTEN
tcp        0      0 *:ssh                       *:*                         LISTEN
tcp        0      0 localhost:smtp              *:*                         LISTEN
tcp        0      0 *:pcsync-https              *:*                         LISTEN
tcp        0      0 localhost:mxi               *:*                         LISTEN
tcp        1      0 localhost:40967             localhost:webcache          CLOSE_WAIT
tcp        1      0 localhost:35080             localhost:webcache          CLOSE_WAIT
tcp        0      0 localhost:pcsync-https      localhost:52796             ESTABLISHED
tcp        0      0 localhost:35982             localhost:pcsync-https      ESTABLISHED
tcp        1      0 localhost:51163             localhost:webcache          CLOSE_WAIT
tcp        0      0 localhost:52796             localhost:pcsync-https      ESTABLISHED
tcp        1      0 localhost:38433             localhost:webcache          CLOSE_WAIT
tcp        0    500 nar.ville-ge.ch:ssh         volcano.ville-ge.ch:50061   ESTABLISHED
tcp        1      0 localhost:46177             localhost:webcache          CLOSE_WAIT
tcp        1      0 localhost:38458             localhost:webcache          CLOSE_WAIT
tcp        0      0 localhost:pcsync-https      localhost:35982             ESTABLISHED‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

So what should I actually kill?
Tomcat is launched automatically by the alfresco.sh file anyway…
Sorry, but I'm a bit at lost here.

Re: Severe Solr install problems

bisana — Mon, 07 May 2012 08:48:13 GMT

First make sure you have shutdown the server

 /pathwhereyouhavelafrescofolder/alfresco.sh stop    ‍

most probable you may have java process related alfresco running you should kill the processor of the service
like

 
ps aux | grep alf
‍‍‍

which gives result similar to

  
 ps aux | grep alf
alfresco  9172  0.0  2.5 1024400 100948 ?      Sl   May02   0:02 /opt/legaldm/openoffice/program/soffice.bin -accept=socket,host=127.0.0.1,port=8100;urp;StarOffice.ServiceManager -env:UserInstallation=file:///opt/legaldm/alf_data/oouser -nologo -headless -nofirststartwizard -nocrashrep -norestore
alfresco  9666  1.7 29.4 3038284 1155664 ?     Sl   May02 124:15 /opt/legaldm/java/bin/java -Djava.util.logging.config.file=/opt/legaldm/tomcat/conf/logging.properties -XX:MaxPermSize=512m -Xms128m -Xmx1024m -XX:-DisableExplicitGC -Dalfresco.home=/opt/legaldm -Dcom.sun.management.jmxremote -Dsun.security.ssl.allowUnsafeRenegotiation=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/opt/legaldm/tomcat/endorsed -classpath /opt/legaldm/tomcat/bin/bootstrap.jar -Dcatalina.base=/opt/legaldm/tomcat -Dcatalina.home=/opt/legaldm/tomcat -Djava.io.tmpdir=/opt/legaldm/tomcat/temp org.apache.catalina.startup.Bootstrap start
‍‍‍‍‍

the digit in the secound row, in this case it is 9172 and 9666
you need to kill it by


kill -9 9172
kill -9 9666
‍‍‍‍

the restart the alfresco service
use tail -f to see the catalina.log for the status

Re: Severe Solr install problems

sjordi — Mon, 07 May 2012 09:25:55 GMT

Well,
I owe you.

You were right, the Alfresco Java process was still running despite the shutdown.

root       813  0.1  4.9 2871376 397364 ?      Sl   May04   4:15 /opt/alfresco/current/java/bin/java -Djava.util.logging.config.file=/opt/alfresco/current/tomcat/conf/logging.properties -XX:MaxPermSize=512m -Xms128m -Xmx1024m -XX:-DisableExplicitGC -Djava.awt.headless=true -Dalfresco.home=/opt/alfresco/current -Dcom.sun.management.jmxremote -Dsun.security.ssl.allowUnsafeRenegotiation=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/opt/alfresco/current/tomcat/endorsed -classpath /opt/alfresco/current/tomcat/bin/bootstrap.jar -Dcatalina.base=/opt/alfresco/current/tomcat -Dcatalina.home=/opt/alfresco/current/tomcat -Djava.io.tmpdir=/opt/alfresco/current/tomcat/temp org.apache.catalina.startup.Bootstrap start
‍‍

Killed -9 813 and restarted the alfresco service.
No erros in catalina.out despite something else probably linked to Open Office, which is not installed

ERROR [repo.content.JodConverterSharedInstance] [main] Unable to start JodConverter library. The following error is shown for informational purposes only.
 org.artofsolving.jodconverter.office.OfficeException‍‍

So what does this mean? What will happen during the next reboot? Where does this Java process come from?
Any way to remove it?
I'd like to make sure that during a next restart, the admin won't need to shtudown the Alfresco service, kill the Java process and restart Alfresco.

If you have any idea why the Java process interferes, that would be great.
Thanks for your help.

Re: Severe Solr install problems

bisana — Mon, 07 May 2012 09:55:32 GMT

So what does this mean? What will happen during the next reboot? Where does this Java process come from?

I guess the answer lies in this link
http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Ftasks%2Ftroubleshoot-openoffice.html

Now , if catalina.out is not showing any other errors, are you able to login through the share web interface, I guess you should be able to login
Regarding killing the java process after stooping alfresco, I don't have any idea. At present I am not taking seriously since still we are evaluating Alfresco for our needs, I think the next release may be able to solve the issue
Thanks

Re: Severe Solr install problems

sjordi — Mon, 07 May 2012 10:00:13 GMT

Ok then,
good luck.
We have Alfresco 3 here without troubles. Since I was upgrading to 4.0.1, I first installed it in a VM for evaluation purpose, in order to not jeopardize the entire production line.
Anyway, next time I'll reboot it, I'll check for that stupid java error/problem.

Thanks for your help.
Steve