Upgrade 3.0 => 3.3g works just one time!

[tomedward]

Hello Forum,

I upgraded our Alfresco 3.0 Community to the current Alfresco 3.3g Community.

Copied alf_data, imported DB. Started Alfresco 3.3, upgrade scripts are running just smooth, Alfresco is up, Server is available, Users, Groups, data everything fine(!), yes?
Well just run alf_stop and alf_start and be suprised to find out that it cant find the root dir anymore! What is going on?  :!:  :?:

Here is the log:
20:46:05,784 INFO  [org.alfresco.config.JndiPropertyPlaceholderConfigurer] Loading properties file from class path resource [alfresco/alfresco-shared.properties]
20:46:07,300 INFO  [org.alfresco.repo.management.subsystems.ChildApplicationContextFactory] Startup of 'OOoDirect' subsystem, ID: [OOoDirect, default] complete
20:46:09,409 INFO  [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco root data directory ('dir.root') is: D:\Alfresco\alf_data
20:46:09,597 ERROR [org.alfresco.repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: System content not found in content store.
20:46:09,597 ERROR [org.alfresco.repo.admin.ConfigurationChecker] Ensure that the 'dir.root' property is pointing to the correct data location.

Just to be clear it worked all fine and perfect on the first start. It only happened after alf_stop+alf_start. I didnt change anything in the config after the upgrade and of course is alf_data still in the path and the DB is available too.

Thanks for the help. Tom

[loftux]

There is a patch that seem to delete content, I ran into this to.
I resolved it by having an old alf_data/contentstore available, i.e
-Make a copy  of alf_data/contentstore to alf_data/contentstore2
-run the upgrade, stop alfresco
-copy all content in alf_data/contentstore into alf_data/contentstore2 and then delete alf_data/contentstore
-rename alf_data/contentstore2 to alf_data/contentstore
-Restart, and it should work.

Is this safe? I'm not sure, but since an upgrade should not alter any of the content files, and alfresco file store never overwrites files you should be fine. What could happen is that you get some more orphaned files (files with no link in db), but they should be deleted by the orphan store cleaner.
But please, do test carefully before going live.

[tomedward]

Thanks Loftux! The hint helped. Indeed, as the error says, content from contentstore ist missing! I compared with the former contentstore and something like 10% of the files were gone! Why, how, dont know! I just copied the former contentstore once again into alf_data and now it works. I can start and stop the server without losing my contents. However, there are quite alot of warnings when running and tons(!) of errors when stopping, but cant see what they say. Tom

[loftux]

Try to do a full reindex, and see if that helps. Else you would have to post your errors if you need more help.

[tomedward]

Hello Loftux, did index.recovery.mode=FULL, renamed the lucene-index folder before, so it was completly fresh.
But the Warnings when running and the tons of errors when stopping did not disappear. 😞
These are the errors displayed when stopping.

ERROR [org.alfresco.repo.management.subsystems.ChildApplicationContextFactory$ChildApplicationContext] Exception thrown from ApplicationListener handling ContextClosedEvent
org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'shutdownBackstop': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)

Also I ran in the "share port situation", means if you run your alfresco e.g. on port 80, one cant login into the share anymore.

Thanks for the help, Tom

[mrogers]

You can safely ignore that error.     Just make sure that Alfresco has actually shut down before restarting.