Hello, I have to upgrade Alfresco 3.2r to Alfresco 3.4d for a customer company. They have their Alfresco 3.2r running into a virtual machine with windows server 2008 (using 2GB RAM). First of all, I asked them a test enviornemnt (so a snapshot of production environment), and I started to work. After fighting one day, I did the upgrade in the test envoirment following the general upgrade process, but it only worked doing the next:
1)shut down alfresco 3.2r
2)install new alfresco 3.4d
3)make changes to alfresco 3.4d, and check that it works
4)copy the alf_data from 3.2r to 3.4d
5)recover the database from 3.2r to 3.4d (mysqldump)
6)first, in repository.properties —-> index.recovery=AUTO (without deletinc lucene-indexes)
7)start the new alfresco and check that it doesn't work proprely, so shut down again
8)delete lucene-indexes, and in repository.properties —-> index.recovery=FULL
9)startup —> perfect
10)after that, in repository.properties —>index.recovery=VALIDATE
This was the process that worked properly, and perfect. I still don't why I should do the step #6, instead of step #8 directly, but with this sequence it worked (I checked many times). Ok, perfect.
The problem is that yesterday, thinking I was ready to make the upgrade in production environment, it didn't work. The same sequence throw me an error of
The only difference between test and production environment is:
TEST: disk space —-> used: 18,1GB, free: 11,8GB
PRODUCTION: disc space —-> used: 38,8GB, free: 1,15GB (in this unit I have my new (defective) alfresco 3.4, and my old alfresco 3.2r)
Could the disc space be the cause of the problem?? Any ideas??? it's urgent
1)shut down alfresco 3.2r
2)install new alfresco 3.4d
3)make changes to alfresco 3.4d, and check that it works
4)copy the alf_data from 3.2r to 3.4d
5)recover the database from 3.2r to 3.4d (mysqldump)
6)first, in repository.properties —-> index.recovery=AUTO (without deletinc lucene-indexes)
7)start the new alfresco and check that it doesn't work proprely, so shut down again
8)delete lucene-indexes, and in repository.properties —-> index.recovery=FULL
9)startup —> perfect
10)after that, in repository.properties —>index.recovery=VALIDATE
This was the process that worked properly, and perfect. I still don't why I should do the step #6, instead of step #8 directly, but with this sequence it worked (I checked many times). Ok, perfect.
The problem is that yesterday, thinking I was ready to make the upgrade in production environment, it didn't work. The same sequence throw me an error of
20:25:42,604 ERROR [admin.patch.PatchExecuter] 04250015 org.alfresco.error.AlfrescoRuntimeException: 04250014 Bootstrap failedThe only difference between test and production environment is:
TEST: disk space —-> used: 18,1GB, free: 11,8GB
PRODUCTION: disc space —-> used: 38,8GB, free: 1,15GB (in this unit I have my new (defective) alfresco 3.4, and my old alfresco 3.2r)
Could the disc space be the cause of the problem?? Any ideas??? it's urgent
