NOTE: If you are not familiar with linux, don't try this, get the thalia ops team involved. These are very rough notes, more a reminder to developers who have already done these things. If you have not, please involve ops rather than trying to do it yourself.
1. Is alfresco running? Go to http://mv.ezproxy.com.ezproxyberklee.flo.org/alfresco
If not, stop and start alfresco:
cd /home/alfresco/faces/jsp/dashboards/container.jsp -2.1.1-enterprise
./alfresco.sh stop (wait for 2 minutes for Alfresco to completely stop)
./alfresco.sh start (look at ./alfresco.log to make sure it indeed starts)
retest step 1
2. Is the IME running? go to http://mv.ezproxy.com.ezproxyberklee.flo.org/libraries
If not, can we access the manager: http://mv.ezproxy.com.ezproxyberklee.flo.org/manager/html
If not, are tomcat and apache running? http://mv.ezproxy.com.ezproxyberklee.flo.org
Try to stop and start the web server: Try:
/etc/init.d/web stop Wiki Markup
/etc/init.d/web start
look at the log file at /home/apache-tomcat-5.5.23/logs/catalina.out to make sure that tomcat starts with no problems
If the log file complains about address in use:
ps -aux | grep tomcat (how many tomcat process are running)
ps -aux | grep alfresco (which one is the alfresco tomcat process)
Wiki Markup |
---|
Don't touch the alfresco tomcat process. Kill the other tomcat processes listed: stop ps \-aux \| grep tomcat There should only be 2 \-\- one for tomcat, one for the tomcat within alfresco. If there are more than this, kill the tomcats that are NOT alfresco. kill \-9 \[id for thalia tomcat serverservers\] ps \-aux \| grep tomcat again to make sure there is only the alfresco process running then /etc/init.d/web start to start the thalia web server \\ \\server |
3. If things still don't work, reboot the entire server:
shutdown -r now
When the server comes back up:
start alfresco first
cd /home/alfresco-2.1.1-enterprise
./alfresco.sh start
check the alfresco.log and go to http://mv.ezproxy.com.ezproxyberklee.flo.org/alfresco/ to verify if Alfresco is running now
now start the IME web server:
/etc/init.d/web start
check catalina.out to see if there are problems.