corrupt node - what to do now

[rainer]

hi list,

i am fighting with a corrupted node since yesterday - it made my publish repository unusable, i couldn't even delete any node anymore.

i got the following error:

ERROR AUTHOR[main]org.apache.jackrabbit.core.query.OnWorkspaceInconsistency: Node /site1/en/explore (a471dc88-2d47-4186-9c7c-4bfc6459a34d) has missing child 'events-overview' (ab203e01-f2a8-45f4-859a-d02f96f6977b)
...
ERROR AUTHOR[main]org.apache.jackrabbit.core.RepositoryImpl: Unable to initialize workspace 'website'
javax.jcr.RepositoryException: Error indexing workspace: Error indexing workspace: Error indexing workspace
...
ERROR AUTHOR[main]info.magnolia.cms.beans.config.ContentRepository: Failed to initialize hierarchy manager for JCR magnolia
javax.jcr.NoSuchWorkspaceException: website


The strange thing is - i can work with the instance as usual... but at startup the error is thrown.

(i do also remember the day, when the "events-overview" page was not deletable.)


any help is appreciated ;)

regards
rainer

[Jan Haderka-2]

Try to use magnolia-tools [1] to delete the corrupted node and then
re-index the workspace.

[1] http://documentation.magnolia-cms.com/cookbook/tools.html

HTH,
Jan


On Tue, 2009-11-03 at 00:04 -0800, rainer wrote:

>
> hi list,
>
> i am fighting with a corrupted node since yesterday - it made my publish
> repository unusable, i couldn't even delete any node anymore.
>
> i got the following error:
>
> ERROR AUTHOR[main]org.apache.jackrabbit.core.query.OnWorkspaceInconsistency:
> Node /site1/en/explore (a471dc88-2d47-4186-9c7c-4bfc6459a34d) has missing
> child 'events-overview' (ab203e01-f2a8-45f4-859a-d02f96f6977b)
> ...
> ERROR AUTHOR[main]org.apache.jackrabbit.core.RepositoryImpl: Unable to
> initialize workspace 'website'
> javax.jcr.RepositoryException: Error indexing workspace: Error indexing
> workspace: Error indexing workspace
> ...
> ERROR AUTHOR[main]info.magnolia.cms.beans.config.ContentRepository: Failed
> to initialize hierarchy manager for JCR magnolia
> javax.jcr.NoSuchWorkspaceException: website
>
>
> The strange thing is - i can work with the instance as usual... but at
> startup the error is thrown.
>
> (i do also remember the day, when the "events-overview" page was not
> deletable.)
>
>
> any help is appreciated ;)
>
> regards
> rainer

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[rainer]

I could repair the repository using this groovy script:

http://lab.openmindonline.it/wiki/display/OPENUTILS/Repair+jcr+nodes+with+broken+item+states+with+openutils-mgnlgroovy

But i wonder where the corrupted pages come from (using 4.1.1 EE) - i found 3 errors in my repository.
Unfortunately i cannot reproduce the behaviour...

regards
rainer

rainer wrote:

hi list,

i am fighting with a corrupted node since yesterday - it made my publish repository unusable, i couldn't even delete any node anymore.

i got the following error:

ERROR AUTHOR[main]org.apache.jackrabbit.core.query.OnWorkspaceInconsistency: Node /site1/en/explore (a471dc88-2d47-4186-9c7c-4bfc6459a34d) has missing child 'events-overview' (ab203e01-f2a8-45f4-859a-d02f96f6977b)
...
ERROR AUTHOR[main]org.apache.jackrabbit.core.RepositoryImpl: Unable to initialize workspace 'website'
javax.jcr.RepositoryException: Error indexing workspace: Error indexing workspace: Error indexing workspace
...
ERROR AUTHOR[main]info.magnolia.cms.beans.config.ContentRepository: Failed to initialize hierarchy manager for JCR magnolia
javax.jcr.NoSuchWorkspaceException: website


The strange thing is - i can work with the instance as usual... but at startup the error is thrown.

(i do also remember the day, when the "events-overview" page was not deletable.)


any help is appreciated ;)

regards
rainer

[Jan Haderka-2]

On Tue, 2009-11-03 at 05:14 -0800, rainer wrote:
>
> I could repair the repository using this groovy script:

cool. glad to hear that.

> But i wonder where the corrupted pages come from (using 4.1.1 EE) - i found
> 3 errors in my repository.
> Unfortunately i cannot reproduce the behaviour...

Check your log files. Usually it is one of the 3 reasons - broken
connections to the backend store, incorrect shutdown or OOME.
... and all of those together with the embedded or not-transactional
backend store. e.g. Derby + OOME or kill -9 of the server in middle of
transaction => unfinished transaction => corrupted node ...
similar result with the MySQL and OOME or kill or lost connection in
middle of transaction while using MyISAM instead of InnoDB => lack of XA
support means no rollback in such situation => corrupted node

HTH,
Jan


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------