Common NSS server initialization problems

Table 1. Common NSS server initialization problems
Problem Symptom Cause/response
The NSS load module is not APF-authorized. The NSS load module abends. The following message will be logged to the console: 
IEF450I NSSD STEP1 - ABEND=S000
U4087 REASON=00000000
The NSS load module must be APF-authorized.
The NSS socket directory does not exist or else it cannot be created by the NSS server. When NSS server syslog level 2 is set (NSS_SYSLOG_LEVEL_VERBOSE), debug message DBG0040I is generated. For example: 
DBG0040I NSS_VERBOSE Cannot
create socket directory
/var/sock - rc -1 errno 135
EDC5135I Not a directory.
The NSS server will
immediately shutdown.
  1. The /var directory must already exist.
  2. The /var/sock subdirectory must already exist, or else the userid that the NSS server is running under must have authority to create the /var/sock subdirectory.
The NSS server is configured in FIPS 140 mode and ICSF is not active. Message EZD1390I is issued, and the NSS server stops. If the NSS server is configured in FIPS 140 mode, ICSF must be active when the NSS server is started. To correct this problem, start ICSF and then start the NSS server. ICSF must be configured in one of several FIPS operational modes when started.