Based on error (ndsdwrapper[3460]: /opt/novell/eDirectory/sbin/ndsdwrapper: line 12: NDSHOME/opt/novell/eDirectory/sbin/ndsd: No such file or directory)

It does not look for /opt/novell/eDirectory/sbin/ndsd but NDSHOME/opt/novell/eDirectory/sbin/ndsd

Check ndsdwrapper script how eDirectory is run, but there could be something wrong with setting some environment variable (probably in ndsdwrapper script you should see hov env variables are loaded)

You are using a custom environment. Probably you have a wrong setting in your environment. Your environment has to be such, that $sbindir points to /opt/novell/eDirectory/sbin . In your case $sbindir points to NDSHOME/opt/novell/eDirectory/sbin, which of course does not exist. And as NDSHOME is interpreted as a real path and not a variable, it is probably net set up as a variable.

This occur after a OES upgrade ...

I do not believe that the environment has changed into a custom env. during the upgrade.

I removed this server from the ring and recreate it.

As you wrote in your initial post you created an env_custom file. Probably you did not copy the contents of the env file to your env_custom file before adding the entry "NDSD_IGNORE_RFL=Y"  to this file. If you fail to do this most of the environment is not set or not set correctly, so that ndsd is for sure unable to start.