topic Re: RM Installation causes failed start and 404 error in Alfresco Archive

RM Installation causes failed start and 404 error

ofrxnz — Tue, 17 Nov 2009 21:33:30 GMT

So, i am was testing the upgrade path from 3.0 to 3.2r and after I applied this fix https://issues.alfresco.com/jira/browse/ALFCOM-3611 I was successfully able to migrate/upgrade to 3.2r with 100% the functionality. I went to install the Records Management amps to give them a test drive and was car

Re: RM Installation causes failed start and 404 error

kbonnet — Wed, 18 Nov 2009 07:37:39 GMT

Thanks for posting this and pointing me to it from my own post /en/viewtopic.php?f=51&t=23237&p=76180. i have the same problem, but i never named CompanyHome different from the default.

Any Alfrescians on the rescue?

Koen

Re: RM Installation causes failed start and 404 error

ofrxnz — Wed, 18 Nov 2009 21:27:59 GMT

May or may not be related but, this seems to go deeper into the boot strap process now.

The new IMAP related files did not and do not appear in Data Dictionary as well….

When i tested 3.2 (not 3.2r) a while back, IMAP worked great but, in 3.2r it seems to be half working……

Ill keep digging and post what i find

Re: RM Installation causes failed start and 404 error

ofrxnz — Wed, 02 Dec 2009 20:46:11 GMT

Well, it looks like there is a version 3.2r2 emphasis on the second 2. i found it on sourceforge now and it seems to be giving me better behavior. will post more when i have put it through its paces

The version that was giving me the issues IDs as v3.2.0 (r 2384)

This version which holds promise is v3.2.0 (r2 2440)

Should the front page of the Wiki be updated to reflect this is an update?

Re: RM Installation causes failed start and 404 error

kbonnet — Fri, 11 Dec 2009 19:11:23 GMT

Yes, i agree, R2 is a rather important improvement. There are also improvements on the external authentication subsystem

Re: RM Installation causes failed start and 404 error

ofrxnz — Tue, 15 Dec 2009 14:38:24 GMT

So, in 3.2r2 if i delete every user, disable external authentication, and wait about 24 hours, i have about a 60% success rate at installing RM.

Could the authentication component be taking too long to start and causing the RM install to explode?

Does that make any sense?

Re: RM Installation causes failed start and 404 error

bnordgren — Fri, 18 Dec 2009 17:08:41 GMT

I suspect it's not the authentication component causing the fail. I have a brand new 3.2r2 system on ArchLinux with no data and no authentication configured (meaning admin/admin is in the local store; no other users, no other user stores). My failure is somewhat different: installing RM appears to have reset the "dir.root" property. I can't figure out how, since my alfresco-global.properties is intact.

Note I am not using the installer. My process was : 1] stop tomcat; 2] install RM amp in alfresco war; 3] install RM-share amp in share war; 4] remove the alfresco and share directories from /srv/tomcat/webapps; 5] restart tomcat; 6] notice failure. I did install the MS Sharepoint support at the same time, so that could be it.

In the following, note the line which declares that: "The Alfresco 'dir.root' property is set to a relative path './alf_data'. 'dir.root' should be overridden to point to a specific folder." My alfresco-global.properties file still has dir.root as "/mnt/infomaster/alfresco". But since dir.root is being ignored, it's being set to a directory which doesn't exist, which puts it out of sync with the database (which it can still contact).

Should we enter this into Jira, or is it already there?


INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
09:23:27,593  INFO  [alfresco.config.JBossEnabledWebApplicationContext] Refreshi
ng org.alfresco.config.JBossEnabledWebApplicationContext@3eb68e0e: display name
[Root WebApplicationContext]; startup date [Fri Dec 18 09:23:27 GMT 2009]; root
of context hierarchy
09:23:27,773  INFO  [alfresco.config.JBossEnabledWebApplicationContext] Bean fac
tory for application context [org.alfresco.config.JBossEnabledWebApplicationCont
ext@3eb68e0e]: org.springframework.beans.factory.support.DefaultListableBeanFact
ory@709a1411
09:23:28,444  INFO  [web.scripts.DeclarativeRegistry] Registered 22 Web Scripts
(+0 failed), 24 URLs
09:23:28,456  INFO  [web.scripts.AbstractRuntimeContainer] Initialised Presentat
ion Web Script Container (in 143.1033ms)
09:23:28,661  INFO  [web.scripts.DeclarativeRegistry] Registered 40 Web Scripts
(+0 failed), 42 URLs
09:23:28,673  INFO  [web.scripts.AbstractRuntimeContainer] Initialised WebFramew
ork Web Script Container (in 214.60793ms)
Dec 18, 2009 9:23:29 AM org.apache.catalina.core.StandardContext addApplicationL
istener
INFO: The listener "org.apache.myfaces.webapp.StartupServletContextListener" is
already configured for this context. The duplicate definition has been ignored.
09:23:31,849  INFO  [alfresco.config.JndiPropertiesFactoryBean] Loading properti
es file from class path resource [alfresco/repository.properties]
09:23:31,851  INFO  [alfresco.config.JndiPropertiesFactoryBean] Loading properti
es file from class path resource [alfresco/domain/transaction.properties]
09:23:31,851  INFO  [alfresco.config.JndiPropertiesFactoryBean] Loading properti
es file from file [/srv/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/module/
org_alfresco_module_dod5015/alfresco-global.properties]
09:23:31,918  INFO  [alfresco.config.JndiPropertyPlaceholderConfigurer] Loading
properties file from class path resource [alfresco/alfresco-shared.properties]
09:23:47,818  INFO  [domain.schema.SchemaBootstrap] Schema managed by database d
ialect org.hibernate.dialect.MySQLInnoDBDialect.
09:23:48,387  INFO  [domain.schema.SchemaBootstrap] No changes were made to the
schema.
09:23:48,635  INFO  [management.subsystems.ChildApplicationContextFactory] Start
ing 'sysAdmin' subsystem, ID: [sysAdmin, default]
09:23:48,646  INFO  [alfresco.config.JndiPropertyPlaceholderConfigurer] Loading
properties file from class path resource [alfresco/alfresco-shared.properties]
09:23:48,650  INFO  [management.subsystems.ChildApplicationContextFactory] Start
up of 'sysAdmin' subsystem, ID: [sysAdmin, default] complete
09:23:49,715  WARN  [node.index.FullIndexRecoveryComponent] The indexes are not
synchronized with the database.
09:23:49,815  WARN  [node.index.AVMFullIndexRecoveryComponent]     Index for avm
 store sitestore is out of date
09:23:50,645  WARN  [repo.admin.ConfigurationChecker] The Alfresco 'dir.root' pr
operty is set to a relative path './alf_data'.  'dir.root' should be overridden
to point to a specific folder.
09:23:50,645  INFO  [repo.admin.ConfigurationChecker] The Alfresco root data dir
ectory ('dir.root') is: ./alf_data
09:23:50,681  ERROR [repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: I
ndexes not found for 7 stores.
09:23:50,681  INFO  [repo.admin.ConfigurationChecker] You may set 'index.recover
y.mode=FULL' if you need to rebuild the indexes.
09:23:50,681  ERROR [repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: S
ystem content not found in content store.
09:23:50,681  ERROR [repo.admin.ConfigurationChecker] Ensure that the 'dir.root'
 property is pointing to the correct data location.
09:23:50,683  ERROR [web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: 11180000 Ensure that the 'dir.root'
 property is pointing to the correct data location.
        at org.alfresco.repo.admin.ConfigurationChecker.check(ConfigurationCheck
er.java:338)
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: RM Installation causes failed start and 404 error

bnordgren — Fri, 18 Dec 2009 19:07:58 GMT

Ok, while all the above observations are "true", subsequent investigation renders unlikely the conclusion to which I jumped.

At some point in time yesterday, prior to alfresco booting at all, it stopped reading my alfresco-global.properties file. Hence, the "./alf_data" directory was the one in use prior to adding any AMPs to the warfile. So I withdraw any assertion that installing the RM AMP affected my dir.root.

…but adding the AMPs yesterday did cause the indices to get out of sync, which caused the configuration checker to abort all attempts to start.

…and yet starting from scratch (removing ./alf_data; dropping the alfresco database and re-creating it) and adding AMPs one by one, restarting the server in between each addition, everything seems to work as expected. No out-of-sync indices. No errors on startup.

The conclusion to which I now jump is that Alfresco is like DOS, or windows 95: If you install something, you better reboot. If you're installing lots of somethings, you do it one at a time and reboot in between each one. If you fail to do this, it "might" work, but if you want to be sure, it's reboot city.

Now to find out why tomcat suddenly stopped locating my alfresco-global.properties file…

Re: RM Installation causes failed start and 404 error

bnordgren — Tue, 22 Dec 2009 21:10:35 GMT

Just a quick follow-up…after all my jumping to conclusions, it turns out that my problem is that my installation of Tomcat 6.0.20 does not respect the shared.loader directive in the configuration file. Once I moved the shared directory path to the common.loader directive in the same file I stopped seeing these weird problems. My issues were mostly due to starting Tomcat in whatever random directory I happened to be at, causing a new filestore to be created which was no longer in sync with the database. I wasn't debugging what I thought I was. Sorry.