FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    Broken pipe error in logs

    Scheduled Pinned Locked Moved Solved
    Q&A
    2
    2
    1.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      twilkinson
      last edited by

      I'm seeing the same issue described in this old post, which unfortunately offers no further explanation or solution:

      Re: Performance issues after upgrade

      I'm running FusionAuth™ version 1.47.1 in a docker container.
      The system seems to be behaving properly, but from time to time this error shows up in the logs:

      Oct 31 14:17:06 auth2 fusionauth 2023-10-31 06:17:06.672 PM ERROR io.fusionauth.http.server.HTTPServerThread - An exception was thrown during processing
      Oct 31 14:17:06 auth2 fusionauth java.io.IOException: Broken pipe
      Oct 31 14:17:06 auth2 fusionauth at java.base/sun.nio.ch.FileDispatcherImpl.writev0(Native Method)
      Oct 31 14:17:06 auth2 fusionauth at java.base/sun.nio.ch.SocketDispatcher.writev(SocketDispatcher.java:66)
      Oct 31 14:17:06 auth2 fusionauth at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:217)
      Oct 31 14:17:06 auth2 fusionauth at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:153)
      Oct 31 14:17:06 auth2 fusionauth at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:563)
      Oct 31 14:17:06 auth2 fusionauth at java.base/java.nio.channels.SocketChannel.write(SocketChannel.java:642)
      Oct 31 14:17:06 auth2 fusionauth at io.fusionauth.http.server.HTTPServerThread.write(HTTPServerThread.java:323)
      Oct 31 14:17:06 auth2 fusionauth at io.fusionauth.http.server.HTTPServerThread.run(HTTPServerThread.java:171)

      Has there been a resolution for this?

      A 1 Reply Last reply Reply Quote 0
      • A
        Alex Patterson @twilkinson
        last edited by

        @twilkinson That message is logged when an HTTP client closes a connection before FusionAuth can fully send a response. This could be as innocuous as a user closing their browser before a page has completed loading.

        Some thoughts:

        • Do you see other exceptions in the log?
        • Possibly related to database connections? What does the load look like on the DB?
        • Do you see any issues on Elastic if you are using it?
        1 Reply Last reply Reply Quote 0
        • T twilkinson has marked this topic as solved on
        • First post
          Last post