Article - CS170232
Windchill Directory Server (WindchillDS) shuts down with error "Too many open files" in Windchill
Modified: 01-May-2017
Applies To
- Windchill PDMLink 10.0
Description
- WindchillDS shuts down / fails / exits with error Too many open files
- WindchillDS error log:
category=PROTOCOL severity=FATAL_ERROR msgID=2425016 msg=The LDAP connection handler defined in configuration entry cn=LDAP Connection Handler,cn=Connection Handlers,cn=config has experienced consecutive failures while trying to accept client connections: Too many open files (ServerSocketChannelImpl.java:-2 ServerSocketChannelImpl.java:152 LDAPConnectionHandler.java:970). This connection handler will be disabled
category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.protocols.ldap.LDAPConnectionHandler (alert type org.opends.server.LDAPHandlerDisabledByConsecutiveFailures, alert ID 2425016): The LDAP connection handler defined in configuration entry cn=LDAP Connection Handler,cn=Connection Handlers,cn=config has experienced consecutive failures while trying to accept client connections: Too many open files (ServerSocketChannelImpl.java:-2 ServerSocketChannelImpl.java:152 LDAPConnectionHandler.java:970). This connection handler will be disabled
category=PROTOCOL severity=NOTICE msgID=2556181 msg=Stopped listening for new connections on LDAP Connection Handler 0.0.0.0 port 390
category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerShutdown, alert ID 458893): The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class org.opends.server.core.DirectoryServerShutdownHook and the reason provided for the shutdown was The Directory Server shutdown hook detected that the JVM is shutting down. This generally indicates that JVM received an external request to stop (e.g., through a kill signal)
category=SYNC severity=NOTICE msgID=15138879 msg=Replication server stopped -1 has properly disconnected for cn=admin data in local server id 22723. Trying to reconnect to a suitable replication server
category=CORE severity=SEVERE_WARNING msgID=131185 msg=Worker Thread 6 was interrupted while waiting for new work: java.lang.InterruptedException. This should not happen, but the thread will resume waiting for new work so there should be no adverse effects
- WindchillDS access log:
UNBIND REQ conn=1113263 op=2 msgID=3
DISCONNECT conn=1113263 reason="Client Unbind"
UNBIND REQ conn=1116523 op=2 msgID=3
DISCONNECT conn=1116523 reason="Client Unbind"
UNBIND REQ conn=1113611 op=2 msgID=3
This is a printer-friendly version of Article 170232 and may be out of date. For the latest version click CS170232