Almost every action creates a broken pipe error in the server logs

Description

{}Update 9/5/2021{}: Almost every action performed by any user ends up with a "broken pipe" error, even if the user waits until the page is loaded before clicking on something else in the navigation, submitting, etc.

Almost any action performed as an admin causes a broken pipe error to display in the server logs on 22x. I compared with 21x and wasn't seeing this behavior there. Not sure if I have the components correct, but it affects almost everything.

22x - examples of actions resulting in a broken pipe error in the logs: 

  • Logging in as admin

  • Clicking on Worksite Setup

  • Clicking on Administration Workspace

  • Clicking on External Tools

  • Clicking Home > MOTD

  • Clicking Resources

Activity

Show:

Miguel Pellicer September 14, 2021 at 4:09 AM

This could be related to network issues in both client and server side, nothing to do in the source side.

Won't Fix

Details

Priority

Affects versions

Components

Assignee

Reporter

Environment

22x: https://trunk-mysql.nightly.sakaiproject.org/, build: 80bd741e
Created August 15, 2021 at 11:24 AM
Updated September 14, 2021 at 4:09 AM
Resolved September 14, 2021 at 4:08 AM