nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

[solved] Upgrading community 3.4.e -> 4.0.e - upgraded version hangs at startup.

toaijala

I'm currently trying to upgrade 3.4.e to 4.0.e on same server. But server hangs at startup.

My setup:
- Server Linux CentOs 6.4
- Mysql 5.1.69 (provided by Centos distro)
- Alfresco 3.4.e

What I've done to upgrade:
- installed 4.0.e, started it once to check it works against empty mysql db
- copied content from 3.4.e/alf_data to 4.0.e/alf_data (and configured alfresco to use the exsisting 3.4.e db)

When I start server it applies alot of patches but hangs at this line

 2013-06-19 11:24:06,434  INFO  [admin.patch.PatchExecuter] [main] Applying patch 'patch.updateMimetypes4' (Rationalise mimetypes for PhotoShop and AutoCad).‍

I actually waited for hours without progress. Server won't stop gently (says connection refused) so I have to kill it. Once I restarted the server it progresses to:

 2013-06-19 11:28:00,726  INFO  [admin.patch.PatchExecuter] [main] Checking for patches to apply …
 2013-06-19 11:28:01,705  INFO  [admin.patch.PatchExecuter] [main]      Applying patch 'patch.updateMimetypes4' (Rationalise mimetypes for PhotoShop and AutoCad).
 2013-06-19 11:28:01,736  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Starting 'Authentication' subsystem, ID: [Authentication, managed, ldap1]
 2013-06-19 11:28:01,858  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Startup of 'Authentication' subsystem, ID: [Authentication, managed, ldap1] complete‍‍‍‍

but then hangs again.

Any idea why updated alfresco 4.0.e won't start?

I noticed that it starts openoffice around the time when it hangs, is this the cause? how can I fix it?

root     14772  0.1  1.0 457360 40508 pts/1    Sl   11:28   0:00 /opt/alfresco-4.0.e/openoffice/program/soffice.bin -accept=socket,host=127.0.0.1,port=8100;urp;StarOffice.ServiceManager -env:UserInstallation=file:///opt/alfresco-4.0.e/alf_data/oouser -nologo -headless -nofirststartwizard -nocrashrep -norestore‍‍

I have repeated the upgrade process from scratch twice, and both times got the same behavior. Any suggestions how to fix this?

Find more posts tagged with

Comments

toaijala

I tried to disable openoffice using global properties files and it dosen't seem to start it anymore, however tomcat hangs as before so I guess it's not openoffice related.

bisana

OpenOffice is not an issue
I think you missed this step
The installation dir of " 3.4.e" installation should be moved/ renamed to a different name
<strong>Install 4.0.e (installation dir name should be the same name of 3.4.e ) </strong>
copy alf_data
rest as u did, I think it should work in this way

toaijala

Right now I have folders
/opt/alfresco-3.4.e (old installation)
/opt/alfresco-4.0.e (new installation)

I copied alf_data from old to new
Do you mean I have to now rename /opt/alfresco-4.0.e to /opt/alfresco-3.4.e?
or re-install 4.0.e to folder /opt/alfresco-3.4.e (after I have moved old?)

bisana

You can
rename /opt/alfresco-4.0.e to /opt/alfresco-3.4.e // In this case you need to check the alfresco-global.properties to reflect the changes

or
you can do
re-install 4.0.e to folder /opt/alfresco-3.4.e (after you moved old installation)

bisana

Always norm is that you keep your alfresco installation dir a name, do not name it with version no

Some where u have done mistake in the installation folder, other wise up gradation is simple
can U recheck and do it again

For testing
(a) Is your old instance running properly, restart it and check it
(b) shutdown
© take alf_data backup and DB backup
– For clarity, we will
(d) On another machine create a DB and restore the DB
(e) In the second machine install Alfresco 4 and dont start the service
(f) copy alf_data dir to the new install
(g) After keeping required jar files(if u are using mysql) in lib and cross checking the alfresco-global.properties
(i) start the serive
This is for testing , to avoid the confusion which u are while doing it in the same machine, try out in another machine, 100% it should work. I have have done it 'n' no of times

toaijala

Thank you for your patience
This is exactly how I have done it,

I'm doing all this on a separate server.
I have a production server running 3.4 the goal is to update this at somepoint, but I'm doing all this testing on TEST server
So:
I have:
- installed 3.4 on test server
- copied alf_data and mysqldump on the test server from production
- it's running 3.4.e perfectly and working with the production copied ald_data and DB.

Then I have installed 4.0.e and tested that it works using empty alf_data and DB.
the only .jar file I need to preserve is for mysql db.
As soon as I owerwrite alf_data (or replace, have tried both) and connect to 3.4.e DB it stops working like described in my first post. Folder name changes dosen't help either.
Worst part is that it just hangs, no error messages or anything.
It always hangs at this spot no matter howw many times I try to restart:

2013-06-19 11:28:00,726  INFO  [admin.patch.PatchExecuter] [main] Checking for patches to apply …
 2013-06-19 11:28:01,705  INFO  [admin.patch.PatchExecuter] [main]      Applying patch 'patch.updateMimetypes4' (Rationalise mimetypes for PhotoShop and AutoCad).
 2013-06-19 11:28:01,736  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Starting 'Authentication' subsystem, ID: [Authentication, managed, ldap1]
 2013-06-19 11:28:01,858  INFO  [management.subsystems.ChildApplicationContextFactory] [main] Startup of 'Authentication' subsystem, ID: [Authentication, managed, ldap1] complete‍‍‍‍

So I'm wondering what the next step would be troubleshooting it, as it breaks somehow when upgrading.

toaijala

Found a solution, it was the new (in 4.0) search engine solr that caused the problem.

I enabled debug (in /opt/alfresco-4.0.e/tomcat/webapps/alfresco/WEB-INF/classes/log4j.properties)
and found that tomcat hanged at same messages as in this thread:
http://forums.alfresco.com/forum/developer-discussions/repository-services/problem-using-search-service-during-alfrsco-startup

I realized the problem was in solr, so I switched back to lucene using these instructions:
http://deepak-keswani.blogspot.fi/2012/12/how-to-disable-solr-enable-lucene-on.html

Now alfresco starts.