Environment
eDirectory 9
Situation
The server's volume on which the database resides is getting full. The last repair aborted.
Ndsrepair returns: Error: -153
The database was originally setup on a BTRFS volume which is not supported. Now the database needs to be moved to an XFS volume.
Resolution
In this example a new drive with more capacity and formatted as XFS has been added and mounted as /var/opt/edirfiles. The eDirectory data directory, in the default location, will be moved here.
1. Stop NDSD
ndsmanage stopall
2.Copy the data directory to the new location.
cp -rp /var/opt/novell/eDirectory/data//* /var/opt/edirfiles//
3. Update the nds.conf file with the new path.
- vi /etc/opt/novell/eDirectory/conf/nds.conf
n4u.nds.dibdir=/var/opt/edirfiles/dib
n4u.server.vardir=/var/opt/edirfiles
http.server.module-base=/var/opt/edirfiles/nds-http/
cp -rp /var/opt/novell/eDirectory/data//* /var/opt/edirfiles//
3. Update the nds.conf file with the new path.
- vi /etc/opt/novell/eDirectory/conf/nds.conf
n4u.nds.dibdir=/var/opt/edirfiles/dib
n4u.server.vardir=/var/opt/edirfiles
http.server.module-base=/var/opt/edirfiles/nds-http/
4. Modify the PIDFile path in the unit file.
vi /usr/lib/systemd/system/ndsdtmpl-etc-opt-novell-eDirectory-conf-nds.conf@.service
PIDFile=/var/opt/edirfiles/ndsd.pid
The run, 'systemctl daemon-reload'
PIDFile=/var/opt/edirfiles/ndsd.pid
The run, 'systemctl daemon-reload'
5. Start NDSD
ndsmanage startall
ndsmanage startall
Note: There may be errors the first time it starts. If so stop NDSD and start once more. After a couple of starts there should be no more errors.