Now I know that "Alfresco started" string is ok. It's ambiguity confused me, like the others. 
In the meantime we almost completed our migration from 2.1 to 3.2. There is one problem though in the form of (as I can see) well known "patch.authorityMigration" bug:
http://issues.alfresco.com/jira/browse/ALF-2029
Now, what can be done? Questions:
1) Is there a patch for 3.2 Community version which will enable correct patching with patch.authorityMigration?
2) If not, is there a way to do this manually, either by hand, either with some program?
3) If not, how can I turn off this patch so that his long error stack strace is not visible in the server log?
4) Is this bug serious? Is Alfresco going to work if users are added manually without successful patch?
In the meantime we almost completed our migration from 2.1 to 3.2. There is one problem though in the form of (as I can see) well known "patch.authorityMigration" bug:
http://issues.alfresco.com/jira/browse/ALF-2029
2011-05-18 10:45:30,406 INFO [STDOUT] 10:45:30,406 User:System INFO [admin.patch.PatchExecuter] Applying patch 'patch.authorityMigration' (Copies any old authorities from the user store to the spaces store.).
2011-05-18 10:45:43,324 INFO [STDOUT] 10:45:43,324 User:System ERROR [admin.patch.PatchExecuter] 04180001 org.alfresco.service.cmr.repository.DuplicateChildNodeNameException: Duplicate child name not allowed: name_of_the_file.txt
at org.alfresco.repo.node.db.hibernate.HibernateNodeDaoServiceImpl$12.doInHibernate(HibernateNodeDaoServiceImpl.java:2000)
at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:372)
at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:338)
at org.alfresco.repo.node.db.hibernate.HibernateNodeDaoServiceImpl.newChildAssoc(HibernateNodeDaoServiceImpl.java:1961)
at sun.reflect.GeneratedMethodAccessor474.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at org.alfresco.repo.transaction.TransactionalDaoInterceptor.invoke(TransactionalDaoInterceptor.java:68)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.alfresco.repo.domain.hibernate.DirtySessionMethodInterceptor.invoke(DirtySessionMethodInterceptor.java:381)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy63.newChildAssoc(Unknown Source)
…Now, what can be done? Questions:
1) Is there a patch for 3.2 Community version which will enable correct patching with patch.authorityMigration?
2) If not, is there a way to do this manually, either by hand, either with some program?
3) If not, how can I turn off this patch so that his long error stack strace is not visible in the server log?
4) Is this bug serious? Is Alfresco going to work if users are added manually without successful patch?
I've found a solution for the problem above. Two users/persons were referencing the same TXT file in their properties, hence the error. One of the references was removed with JavaScript script and the remaining patches were applied correctly.
Migration to 3.2 version is finished (on test server with real content & DB). We started with idea to migrate to 3.3, but bugs were too complicated. 3.2 was buggy too, but mildly in comparison. Al least now we can say we're using a "modern" version.
Migration to 3.2 version is finished (on test server with real content & DB). We started with idea to migrate to 3.3, but bugs were too complicated. 3.2 was buggy too, but mildly in comparison. Al least now we can say we're using a "modern" version.
