Edge Encryption Proxy Network Outage or Degraded Proxy Performance or HTTP-502 Errors When Edge Proxy Runs on Linux Due to an Insufficent Number of Operating System File Descriptors - Error: java.io.IOException: Too many open filesIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Following the standard investigation for a "Edge Encryption proxy network outage" case the Edge Encryption logfiles in <proxy_installation>/logs/* should be checked during the time of the proxy outage. When checking the jetty.log the following is seen for a proxy running on Linux: 2019-07-10 13:26:10,778 [qtp837525639-78-acceptor-0@af778ec-ServerConnector@43087c2{SSL,[ssl, http/1.1]}{0.0.0.0:443}] WARN org.eclipse.jetty.server.AbstractConnector - java.io.IOException: Too many open files at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422) at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250) at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:373) at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) at java.lang.Thread.run(Thread.java:748) This may also be seen in cases where the customer is reporting degraded performance on the proxy, e.g. slowness loading pages for users, etc. Users may also see HTTP-502 responses at their browsers. Release Applies to any release. Environment Any instance that has Edge Encryption proxies that run on a Linux operating system. This is not applicable to proxies running on Windows. Cause The Edge Encryption proxy's host Linux operating system has run out of file descriptors also known as file handles, which leads to Edge Encryption proxy failures in handling connections and resources. Resolution (1) Contact your Linux administrator to check the number of allowed file descriptors in the operating system. (2) The Linux administrator should set the file descriptor limits as they see fit. ServiceNow does not provide specific guidelines for these settings, but a hard limit of 1024 is more than likely not enough. Additional Information How to set the file descriptor limits can vary by Linux version. This is why this should be done by the Linux administrator. Two examples of how to set these limits are provided here: https://www.linuxtechi.com/set-ulimit-file-descriptors-limit-linux-servers/ https://www.redhat.com/archives/redhat-sysadmin-list/2006-October/msg00007.html