Problems after ISCSI conectivity lost

[guigsilva]

Hello everybody!

We have some problems between  our VMWare server and ISCSI storage... The Alfresco VM have some disk problems we run e2fsck and correct some inodes...

The machine starts but we can´t write on... On logs we have this :

Caused by: org.alfresco.error.AlfrescoRuntimeException: 021324442 Failed to write property deltas:
  Node:          1299041
  Old:           {}
  New:           {{http://www.alfresco.org/model/content/1.0}content=contentUrl=store://2017/3/13/17/49/d6f08806-8370-4766-9a49-b4c91bec18b7.bin|mimetype=application/octet-stream|size=0|encoding=UTF-8|locale=pt_BR_}
  Diff:          {{http://www.alfresco.org/model/content/1.0}content=RIGHT_ONLY}
  Delete Tried:  []
  Add Tried:     {{http://www.alfresco.org/model/content/1.0}content=contentUrl=store://2017/3/13/17/49/d6f08806-8370-4766-9a49-b4c91bec18b7.bin|mimetype=application/octet-stream|size=0|encoding=UTF-8|locale=pt_BR_|id=1032506}

and this :

### Error updating database.  Cause: org.postgresql.util.PSQLException: ERROR: right sibling's left-link doesn't match: block 11 links to 17868 instead of expected 17636 in index "idx_alf_nprop_l"
### The error may involve alfresco.node.parameter_NodeProperty
### The error occurred while setting parameters
### Cause: org.postgresql.util.PSQLException: ERROR: right sibling's left-link doesn't match: block 11 links to 17868 instead of expected 17636 in index "idx_alf_nprop_l"
; uncategorized SQLException for SQL []; SQL state [XX000]; error code [0]; ERROR: right sibling's left-link doesn't match: block 11 links to 17868 instead of expected 17636 in index "idx_alf_nprop_l"; nested exception is org.postgresql.util.PSQLException: ERROR: right sibling's left-link doesn't match: block 11 links to 17868 instead of expected 17636 in index "idx_alf_nprop_l"

I think the problem is that postgreSQL index is corrupted ...

Any ideias?

Thanks in advance

Guilherme

Afresco 4.2f on ubuntu 12.04

[mehe]

You are on the right track, looks like you have a corrupt index on the db. Rebuild the db index should fix it. Search in postgresql Doku (postgresql .org) for REINDEX. You should stop the whole system, make a backup of the db and start the db only (no Alfresco app), then REINDEX

[guigsilva · Accepted solution]

Hello!

Just for update

We rebuid the index (activate the PostgreSQL remote access because we cant´s find a way to do this local) and all came back to normal...

Just in case we blow the solr index to and rebuild it

Thanks a Lot

Guilherme Gaspar