LDAP Listener remains in incorrect status Active (Shutting Down)
LDAP Monitor shows the LDAP Listener with the incorrect status Active (Shutting Down)
This problem can occur after an abnormal termination of the LDAP Listener process or after a ServiceNow upgrade.
- Restarting the LDAP Listener does not change the status.
- In some cases the LDAP Listener is still functional.
- Entries appear in the sys_status table such as ''glide.ldap.listener-790e96360a0a3c7000794f76ff93305a.shutdown_pending''
The table sys_status contains additional entries that have not been cleaned up.
To resolve this issue:
Navigate to each LDAP Server and click Stop Listener.
Delete the *glide.ldap.listener entries in the sys_status table.
Enter sys_status.list in the filter.
Search for the name *glide.ldap.listener.
Delete the entries.
- Navigate to each LDAP Server and click Start Listener.
Note: This process does not cause any down time or negative performance for the ServiceNow application. It is completely transparent to any users logged in and working.