topic Re: Bug? in Alfresco Archive

Bug?

markthompson23 — Fri, 30 Dec 2005 22:21:35 GMT

I have manually set up this installation twice.Once I'm done, I get this error when attempting to apply categories (I get it when I click on the link to select the category)——————————–javax.faces.FacesException: org.alfresco.repo.search.SearcherException: More than one root node? 0caused byrg.apac

Re: Bug?

lgr — Mon, 02 Jan 2006 16:58:23 GMT

Hi,

See this article, it deals with the same problem.

http://www.alfresco.org/forums/viewtopic.php?t=365&highlight=one+root+node

Anyway, the same error has occured on my repository, and i've never succedded in making any export work, so the only solution i've found is to reinstall all content from scratch after having reset the database.

If you've got any working solution, please tell me.

Laurent.

Re: Bug?

markthompson23 — Tue, 03 Jan 2006 01:09:46 GMT

Are you starting Tomcat as a Windows service?

I've found that if I start the application using the alf_start.bat file, I don't get the error. If it's running as a Windows service, I do get the error. (Going back to the bat solves the error without having to reload anything.)

Re: Bug?

lgr — Tue, 03 Jan 2006 09:37:12 GMT

Well, I'm using Alfresco under linux.
It is launched with the same user and rights as a service or manually.
So i've got the error every time. Anyway, this information should interest the devs…

Laurent.

Re: Bug?

davidc — Tue, 03 Jan 2006 10:24:39 GMT

This issue is often caused by the database and index being out of sync. The index directory location is a relative path defined in repository.properties, so the location where you start Alfresco is important. Starting via alf_start and a service may result in different working directories.

To be sure that you're picking up the correct index directory you can provide an absolute path in repository.properties for dir.root.

Re: Bug?

lgr — Tue, 03 Jan 2006 10:51:56 GMT

ok, this is a great info, that explains why i've so many alf-data folders around my partitions. So, i've got a solution to make it work in the future.

Anyway, is there a way to repair my lucene indexes without having to reinstall all from scratch ? I can't export and import with success yet (i've got another post on this issue).

Laurent.

Re: Bug?

steve — Tue, 03 Jan 2006 13:32:52 GMT

Hello,

You can repair your indexes…

First, stop your app server and back up your existing indexes (just in case!)
The indexes are found in: alf_data\lucene-indexes

Then, edit 'index-recovery-context.xml' and change the following line:

<property name="executeFullRecovery">
<value>false</value> <!– enable this to start the full index recovery –>
</property>

Change the value to true.

Restart the app server and the indexes should be rebuilt.

Steve

Re: Bug?

lgr — Tue, 03 Jan 2006 15:08:22 GMT

ok, but i've got many alf_data folders, containing each a contentstore and a lucene-indexes folders. Some of the content is in my new official contentstore (referenced by the absolute path in repository.properties)

Do i have to copy all files included in "contentstore" into my new "official" contentstore folder (the one with the absolute path), and start the recovery process ?

Do i have to do anything with the lucene-indexes included in my old alf_data folders ? erase or copy (copy ? well i don't think so …) ?

Laurent.

Re: Bug?

lgr — Tue, 03 Jan 2006 15:16:30 GMT

And another question : is it possible to clear all content, but leave all spaces structure and users intact ?

I've all content available, but i've defined many users, and some spaces with detailed permissions on it. It does not bother that i loose the content, but redefining all spaces, users and permission should be a pain.

Do you think that erasing all contentstore files, perhaps erasing all lucene indexes, but not erasing the database content should do it ?

Laurent.

Re: Bug?

lgr — Tue, 03 Jan 2006 16:23:12 GMT

Then, edit 'index-recovery-context.xml' and change the following line:

<property name="executeFullRecovery">
<value>false</value> <!– enable this to start the full index recovery –>
</property>

I haven't found this key in the file.
I've added it.

But i've got an error :
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'IndexRecoveryJobDetail' defined in cla
ss path resource [alfresco/scheduled-jobs-context.xml]: Can't resolve reference to bean 'indexRecoveryComponent' while setting
property 'jobDataAsMap[indexRecoveryComponent]'; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'indexRecoveryComponent' defined in class path resource [alfresco/index-recovery-context.xml]:
Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'e
xecuteFullRecovery' of bean class [org.alfresco.repo.node.index.FtsIndexRecoveryComponent]: Bean property 'executeFullRecovery
' is not writable or has an invalid setter method: Does the parameter type of the setter match the return type of the getter?
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'indexRecoveryComponent' defined in cla
ss path resource [alfresco/index-recovery-context.xml]: Error setting property values; nested exception is org.springframework
.beans.NotWritablePropertyException: Invalid property 'executeFullRecovery' of bean class [org.alfresco.repo.node.index.FtsInd
exRecoveryComponent]: Bean property 'executeFullRecovery' is not writable or has an invalid setter method: Does the parameter
type of the setter match the return type of the getter?
org.springframework.beans.NotWritablePropertyException: Invalid property 'executeFullRecovery' of bean class [org.alfresco.rep
o.node.index.FtsIndexRecoveryComponent]: Bean property 'executeFullRecovery' is not writable or has an invalid setter method:
Does the parameter type of the setter match the return type of the getter?

I use Alfresco v1.1.2. Did i miss something ?

Laurent.

Re: Bug?

lgr — Tue, 03 Jan 2006 20:55:20 GMT

Hmm, i did not find it in the nightly build as well…

So, i'll appreciate some further help .

Laurent.

Re: Bug?

derek — Wed, 04 Jan 2006 11:11:16 GMT

Hi, Laurent

Non-enterprise solutions should employ a backup and recovery procedure, especially before performing upgrades and other major changes to configurations: http://www.alfresco.org/mediawiki/index.php/Backup_and_Restore.

There is no recovery for content which has gone permanently missing. But you can merge file-based content stores (the default) at will just by copying them over each other. All files are GUID-based and you will never get a clash.

For Professional and Enterprise customers, a tool exists that can fully recovery broken or missing Lucene indexes: http://www.alfrescosoftware.com/products/professional. It is also used to keep indexes up to date on backup servers.

Regards

Re: Bug?

derek — Wed, 04 Jan 2006 13:02:58 GMT

In reply to markthompson23:

javax.faces.FacesException: org.alfresco.repo.search.SearcherException: More than one root node? 0
caused by:
org.apache.jasper.JasperException: org.alfresco.repo.search.SearcherException: More than one root node? 0
caused by:
java.lang.RuntimeException: org.alfresco.repo.search.SearcherException: More than one root node? 0

This error message is a little misleading and I have just fixed the error text. It should have said: Index has no root node. Check that the correct index locations are being used.

There are not multiple root nodes, but rather no root nodes. When a root node is created for a store in the database (e.g. the categories store), a root node is created in the Lucene index within the same transaction. It is not possible to create two root nodes for a store, and a second root node should never be made in an index.

However, if you point your server to a new index location, then it assumes that the indexes have root nodes. When you attempt to update the categories, no root node is found and it blows up. This is the theory. Remember that the index and content locations are relative to where you start Tomcat from unless you make it a fixed location. (http://www.alfresco.org/forums/viewtopic.php?p=2504#2504).

You can recover the indexes if you have the Enterprise code. Otherwise try to find the original indexes and put them in the correct location - or try again… :cry:

Regards

Re: Bug?

lgr — Wed, 04 Jan 2006 13:27:23 GMT

ok.

Perhaps, do you have an easy way to delete all content, leaving spaces structure and users intact ? That should save me a couple of hours. I was thinking of deleting "contentstore" folder content and "lucene-indexes", and doing some minimalist trick in the mysql database.

Or I'll reinstall all and implement true backup procedures properly. Yes, i'll try again, but game is not over.

Laurent.

Re: Bug?

markthompson23 — Wed, 04 Jan 2006 13:35:57 GMT

In reply to derek

In case it is relevant, the number at the end of error message kept incrementing. It got as high as 10 (ie 'More than one root node? 10'). I wasn't able to determine what sequence of steps caused it to increment.

I have since restored the system and have set the dir.root value to a fixed location so that has solved the problem. I thought the fact that the number was incrementing might indicate that the error message was accurate. Anyway, I just wanted to pass it on just in case.

Re: Bug?

derek — Wed, 04 Jan 2006 14:59:41 GMT

Mark:

Sorry. I didn't know that the number was incrementing. The problem is probably that the database is cleaned repeatedly but the indexes are not - or something like that.

Laurent:

The Lucene indexes contain search structures for absolutely everthing in the repository and not just the full text search. So not having the indexes is basically terminal. I'm afraid that there is no magic bullet here without rebuilding or having a backup.

Regards

Re: Bug?

lgr — Mon, 09 Jan 2006 04:52:53 GMT

Hello,

I'm rather astonished. I've reinstalled all the Alfresco software from scratch. I've done some modifications on configuration files, including fixing a full path for alf_data folder in repositories.properties, renaming the root space, also define users, create some spaces, etc …

Then, i try to modify catagories, and a common error "more than one root node" occurs. I've understood why. I've put a comment at the end of the line dir.root in repository.properties, and i though that it should be allowed. When i saw my folder named "alf_data #very important", i understood that it should not be allowed.

Can you confirm that not allowing comments at the end of a line is a feature and not a bug ?

Laurent.

Re: Bug?

derek — Mon, 09 Jan 2006 09:29:15 GMT

Hi,

It is unfortunate, but the handling of Java Properties does not allow comments at the end of lines. On the other hand, if you wanted a propery value with a # in it, then there would have to be some magic escape sequence that would be equally obscure.

Regards