Environment
NetIQ eDirectory 8.8 SP8
Situation
eDirectory is running on Red Hat 7.3. With the +NMAS flag on, ndstrace is constantly reporting -663 errors during a NMAS policy refresh.
Messages are seen that indicate the database is locked. Further, the server's nds.conf file cannot be updated.
[2017/03/25 12:22:38.221] DS Local Agent is not open in GetAgentStateAndSlashTreeName
[2017/03/25 12:22:38.221] GetAgentStateAndSlashTreeName failed in ReadConfigFromDS, err = ds locked (-663)
[2017/03/25 12:22:38.221] Could not update server configuration, err = ds locked (-663)
[2017/03/25 12:00:01.966] NMAS policy refresh background thread attempting policy refresh [2017/03/25 12:00:01.966] ERROR: -663 Failed to access the login policy object [2017/03/25 12:00:01.966] ERROR: -663 NMAS Login Policy Refresh Check Failed [2017/03/25 12:00:01.966] ERROR: -663 NMAS policy refresh background thread failed policy refresh [2017/03/25 12:00:01.966] NMAS policy refresh background thread refresh rate: 1
Messages are seen that indicate the database is locked. Further, the server's nds.conf file cannot be updated.
[2017/03/25 12:22:38.221] DS Local Agent is not open in GetAgentStateAndSlashTreeName
[2017/03/25 12:22:38.221] GetAgentStateAndSlashTreeName failed in ReadConfigFromDS, err = ds locked (-663)
[2017/03/25 12:22:38.221] Could not update server configuration, err = ds locked (-663)
Resolution
The server only had 2GB of RAM. Increased it to 4GB and the server restarted fine.
4GB is the minimum amount of memory required to run eDirectory. Most environments will require substantially more. This is especially true if other applications, such as iManager or IDM, also reside on the server.
4GB is the minimum amount of memory required to run eDirectory. Most environments will require substantially more. This is especially true if other applications, such as iManager or IDM, also reside on the server.