You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by jy l <lj...@gmail.com> on 2021/06/02 05:38:28 UTC

ERR_544 CRITICAL: file header magic not OK 0 (2.0.0.AM26)

Hi:
My ApacheDS can't be accessed after running for some time. I checked the
log and threw the following exception:
java.lang.Error: ERR_544 CRITICAL: file header magic not OK 0
        at jdbm.recman.FileHeader.<init>(FileHeader.java:91)
        at jdbm.recman.PageManager.commit(PageManager.java:293)
        at jdbm.recman.BaseRecordManager.commit(BaseRecordManager.java:419)
        at
jdbm.recman.CacheRecordManager.commit(CacheRecordManager.java:350)
        at
org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartitionWriteTxn.commit(JdbmPartitionWriteTxn.java:62)
        at
org.apache.directory.server.core.authn.AuthenticationInterceptor.internalModify(AuthenticationInterceptor.java:493)
        at
org.apache.directory.server.core.authn.AuthenticationInterceptor.bind(AuthenticationInterceptor.java:725)
        at
org.apache.directory.server.core.DefaultOperationManager.bind(DefaultOperationManager.java:515)
        at
org.apache.directory.server.ldap.handlers.request.BindRequestHandler.handleSimpleAuth(BindRequestHandler.java:207)
        at
org.apache.directory.server.ldap.handlers.request.BindRequestHandler.handle(BindRequestHandler.java:661)
        at
org.apache.directory.server.ldap.handlers.request.BindRequestHandler.handle(BindRequestHandler.java:64)
        at
org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:195)
        at
org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:57)
        at
org.apache.mina.handler.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:243)
        at
org.apache.directory.server.ldap.LdapProtocolHandler.messageReceived(LdapProtocolHandler.java:224)
        at
org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:1015)
        at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:650)
        at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1300(DefaultIoFilterChain.java:49)


I don't know what happened to cause this anomaly, and I can't reproduce it
immediately.
My version of apacheds is 2.0.0.AM26. It runs in the environment of
centos7, jdk8.

Looking forward to an effective solution.


Good luck!

Re: ERR_544 CRITICAL: file header magic not OK 0 (2.0.0.AM26)

Posted by Emmanuel Lécharny <el...@gmail.com>.
Hi,

yes, this is a known problem, see 
http://directory.apache.org/apacheds/production-readiness.html

You can try the repairr command : apacheds.sh repair




On 02/06/2021 07:38, jy l wrote:
> Hi:
> My ApacheDS can't be accessed after running for some time. I checked the
> log and threw the following exception:
> java.lang.Error: ERR_544 CRITICAL: file header magic not OK 0
>          at jdbm.recman.FileHeader.<init>(FileHeader.java:91)
>          at jdbm.recman.PageManager.commit(PageManager.java:293)
>          at jdbm.recman.BaseRecordManager.commit(BaseRecordManager.java:419)
>          at
> jdbm.recman.CacheRecordManager.commit(CacheRecordManager.java:350)
>          at
> org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartitionWriteTxn.commit(JdbmPartitionWriteTxn.java:62)
>          at
> org.apache.directory.server.core.authn.AuthenticationInterceptor.internalModify(AuthenticationInterceptor.java:493)
>          at
> org.apache.directory.server.core.authn.AuthenticationInterceptor.bind(AuthenticationInterceptor.java:725)
>          at
> org.apache.directory.server.core.DefaultOperationManager.bind(DefaultOperationManager.java:515)
>          at
> org.apache.directory.server.ldap.handlers.request.BindRequestHandler.handleSimpleAuth(BindRequestHandler.java:207)
>          at
> org.apache.directory.server.ldap.handlers.request.BindRequestHandler.handle(BindRequestHandler.java:661)
>          at
> org.apache.directory.server.ldap.handlers.request.BindRequestHandler.handle(BindRequestHandler.java:64)
>          at
> org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:195)
>          at
> org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:57)
>          at
> org.apache.mina.handler.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:243)
>          at
> org.apache.directory.server.ldap.LdapProtocolHandler.messageReceived(LdapProtocolHandler.java:224)
>          at
> org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:1015)
>          at
> org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:650)
>          at
> org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1300(DefaultIoFilterChain.java:49)
> 
> 
> I don't know what happened to cause this anomaly, and I can't reproduce it
> immediately.
> My version of apacheds is 2.0.0.AM26. It runs in the environment of
> centos7, jdk8.
> 
> Looking forward to an effective solution.
> 
> 
> Good luck!
> 

-- 
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecharny@busit.com https://www.busit.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
For additional commands, e-mail: users-help@directory.apache.org