No new NCP connections possible and existing NCP connections are disconnected.

  • 7001428
  • 24-Sep-2008
  • 27-Apr-2012


Novell Open Enterprise Server 1 (OES 1)
Novell Open Enterprise Server 2 (OES 2)


If Linux User Management (LUM) isn't working correctly on a server, the NCP engine can become unresponsive. If that happens, no new NCP connections are possible and existing NCP connections are disconnected.

In the NDSD log file the following informational errors may be seen:

NCPEngine_VerifyConnectionSocket error
Process NPC error - VerifyConnectionSocket failed for conn: <conn_number>


There are a number of ways to address this problem:

1. Change the preferred-server setting in the nam.conf to another server.

2. Re-configure the Linux User Management (LUM) service (namcd) on the local server to use a base context that exists within a replica currently hosted on the server or alternatively add a replica locally on the server for the currently configured base context as specified in the "/etc/nam.conf" file.

Additional Information

If you choose option #2, do the following.

The current LUM configuration can be obtained by issuing "namconfig get" or to specifically get the configured base context use "namconfig get base-name". To manually change the base context edit the entry in the "/etc/nam.conf" file, once the file is saved namcd needs to be restarted using "rcnamcd restart".