Import ldif failed with error due to je.log.fileCacheSize

This topic has 1 reply, 2 voices, and was last updated 4 years, 8 months ago by Michelle Reagin.

  • Author
    Posts
  • #19605
     ShitalPatil
    Participant

    While import ldif file, we are seeing below error. All the nodes are imported but import job fails with below error.

    We have no where specified value for “je.log.fileCacheSize” but I suppose it is read from “ds-cfg-db-log-filecache-size: 100”. But then why 100 is being compared with “null”.

    Its OpenDJ 2.6

    [15/Nov/2017:20:24:26.459 +0900] severity=”SEVERE_ERROR” msgCount=17 msgID=3408518 message=”org.opends.server.admin.server.ConfigChangeListenerAdaptor.applyConfigurationChange failed for entry ds-cfg-backend-id=userRoot,cn=Backends,cn=config: result code=Other, admin action required=false, messages=”An error occurred while trying to initialize a backend loaded from class org.opends.server.backends.jeb.BackendImpl with the information in configuration entry ds-cfg-backend-id=userRoot,cn=Backends,cn=config: je.log.fileCacheSize is set to 100 in the config parameter which is incompatible with the value of null in the underlying environment (EnvironmentMutableConfig.java:669 DbInternal.java:251 EnvironmentImpl.java:2270 DbEnvPool.java:153 Environment.java:246 Environment.java:227 Environment.java:170 RootContainer.java:218 BackendImpl.java:1746 BackendImpl.java:319 BackendConfigManager.java:1298 BackendConfigManager.java:751 BackendConfigManager.java:69 ServerManagedObjectChangeListenerAdaptor.java:74 ConfigChangeListenerAdaptor.java:342 ConfigFileHandler.java:1759 LocalBackendModifyOperation.java:607 LocalBackendWorkflowElement.java:551 WorkflowImpl.java:197 WorkflowTopologyNode.java:100 ModifyOperationBasis.java:520 …). This backend will be disabled””
    [15/Nov/2017:20:24:26.459 +0900] severity=”INFORMATION” msgCount=18 msgID=9437595 message=”Local DB backend userRoot does not specify the number of lock tables: defaulting to 97″
    [15/Nov/2017:20:24:26.459 +0900] severity=”SEVERE_WARNING” msgCount=19 msgID=3277447 message=”org.opends.server.admin.server.ConfigChangeListenerAdaptor.applyConfigurationChange indicated that administrative action is required for entry ds-cfg-backend-id=userRoot,cn=Backends,cn=config: messages=”The change to the je.log.iteratorReadSize attribute will not take effect until the backend is restarted The change to the ds-cfg-db-num-lock-tables attribute will not take effect until the backend is restarted The change to the je.lock.timeout attribute will not take effect until the backend is restarted The change to the je.env.isTransactional attribute will not take effect until the backend is restarted The change to the je.log.faultReadSize attribute will not take effect until the backend is restarted The change to the je.txn.timeout attribute will not take effect until the backend is restarted The change to the ds-cfg-db-checkpointer-wakeup-interval attribute will not take effect until the backend is restarted””
    [15/Nov/2017:20:24:26.459 +0900] severity=”SEVERE_ERROR” msgCount=20 msgID=11796481 message=”The task could not enable a backend: ds-cfg-backend-id=userRoot,cn=Backends,cn=config

    #19609
     Michelle Reagin
    Participant

    I haven’t seen this error before, but the first thing I would check is your JVM settings for OpenDJ since the error complains about the underlying environment. You will find them in the file installation_directory/config/java.properties, specifically, the line beginning with start-ds.java-args. If options -Xms, -Xmx, and -Xmn are not defined on that line, I recommend defining them according to the amount of free memory available on your OS and the amount of memory you want to allocate to OpenDJ. You can read more about these options here: https://backstage.forgerock.com/docs/opendj/2.6/admin-guide/#perf-tweaking

    The second thing I would check, since file cache size relates to the amount of open/cached files for the underlying DB, are the maximum available file descriptors on your OS as well as validate the OpenDJ OS user has the appropriate hard and soft limits for file descriptors as described here: https://backstage.forgerock.com/docs/opendj/2.6/release-notes/#prerequisites-file-descriptors

    If those steps don’t resolve the issue, I would upgrade to 2.6.4 and apply the patches for that version to see if that resolves the issue.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?