Integrity Error after Alfresco Upgrade

[texano]

Hi,

I've upgrade my Alfresco installation with 20GB repository content from 4.2.C to the newest 5.0.D.
Now we are having errors related to "Mandatory property not set" and "node.integrity.IntegrityException" when creating new sites, viewing tasks, etc. This errors are show in Alfresco Share page and in catalina.out logs.
Please check the attached files.


2015-04-25 19:57:54,094  ERROR [extensions.webscripts.AbstractRuntime] [http-apr-8080-exec-8] Exception from executeScript - redirecting to status template error: 03250167 Found 1 integrity violations:
Mandatory property not set:
   Node: workspace://SpacesStore/32fddf43-103a-4f48-b001-b48552dff3ad
   Name: 32fddf43-103a-4f48-b001-b48552dff3ad
   Type: {http://www.alfresco.org/model/content/1.0}person
   Property: {http://www.alfresco.org/model/content/1.0}sizeCurrent
org.alfresco.repo.node.integrity.IntegrityException: 03250167 Found 1 integrity violations:
Mandatory property not set:
   Node: workspace://SpacesStore/32fddf43-103a-4f48-b001-b48552dff3ad
   Name: 32fddf43-103a-4f48-b001-b48552dff3ad
   Type: {http://www.alfresco.org/model/content/1.0}person
   Property: {http://www.alfresco.org/model/content/1.0}sizeCurrent
        at org.alfresco.repo.node.integrity.IntegrityChecker.checkIntegrity(IntegrityChecker.java:664)
        at org.alfresco.repo.node.integrity.IntegrityChecker.beforeCommit(IntegrityChecker.java:766)




Can you guys help me with this?

Thank you.

[s00pa]

I have exactly the same problem running 5.0.d and I've tried removing all solr indexes and reindexing and it makes no difference. A few days ago I was experimenting with 5.0.c and I can't remember seeing this problem back then. I'm trying to figure out now whether to go back to 5.0.c because it looks like 5.0.d has more problems. And to the person suggesting that we need to set index.recovery.mode=FULL, as far as I know, this has been deprecated since Solr took over from Lucene for indexing alfresco.

EDIT: removing and re-adding the users fixes the problem

–
Sean

[texano]

Hey,

The reindex did not work for me
Still have the same error

Mandatory property not set:
   Node: workspace://SpacesStore/1ad6e30b-7b4d-4886-9d79-80ad6707ecca
   Name: 1ad6e30b-7b4d-4886-9d79-80ad6707ecca
   Type: {http://www.alfresco.org/model/content/1.0}person
   Property: {http://www.alfresco.org/model/content/1.0}sizeCurrent

[ceeliro]

Perform same procedure than before and also set index.recovery.mode=FULL in the alfresco-global.properties

[texano]

Hi,

Tried index.recovery.mode=FULL in the alfresco-global.properties but the problem keeps.. We are in production with this errors..

Anyone know the solution?


Thank you.

[rjohnson]

I doubt this is anything to do with SOLR. Alfresco seems to be complaining about the storage used value not being set and being mandatory on the users account (note the description Type: Person, Property: sizeCurrent). This will be held in the database somewhere, not SOLR. You can set quota's for peoples account and it looks as if the value for "storage used" is not set and for whatever reason Alfresco requiring it to be set. This could be a difference in defaults or settings during the upgrade.

Fixing this is likely to be tricky because I suspect you will have to update something in the database directly which is always a risk.

I do not know if you are using quotas on user accounts or not, but you might try switching it off in alfresco-global.properties and on each user account and see if that helps.

[texano]

I don't think the problem is related with SOLR too but DB problems. When I delete a user and create it again the problem solves. I guess that the pre-upgrade users don't have sizeCurrent defined or something… and then we create a new user in version 5.0.D the sizeCurrent correct works. sizeCurrent is the size used in user space. Any idea how i can update all users in database with a value for sizeCurrent? We don't use quotas.

Thank you.

[andrewlove]

This is an issue in 5.0.d only.

I upgraded directly from 4.2 to 5.0.d and experienced this error both in the SHARE UI and when performing a search. Critically the error causes search to return an empty result set to the user when the error is thrown server-side.

I then performed a migration from 4.2 to 5.0.c and the error was not present. Search worked flawlessly.

For now I am running on 5.0.c.

I cannot use the delete/re-create user workaround suggested here as I use passthru authentication and ldap replication using AD.

[texano]

Any solution besides not upgrading to 5.0.D? I cannot downgrade now.. and I cannot lose all the work done in current 5.0.D version..
Anyone know when 5.0.E will be release with a fix for this? Or just a patch

[mrogers]

5.0.E is unlikely to be released.  The 5.0 code line is finished and 5.1 is in progress.   Next community release will probably be 5.1.A.  

[mrogers]

The issue seems to be a missing mandatory property, so re-indexing is irrelevant.  One fix would be to slap a value of zero on the failing person nodes.