Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bliss bliss
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 544
    • Issues 544
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 147
    • Merge requests 147
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • BlissBliss
  • blissbliss
  • Issues
  • #2762
Closed
Open
Issue created May 17, 2021 by Cyril Guilloud@cyril.guilloudOwner

RPC : missing conection identification in case of Connection reset

When server is closed un-properly, "Connection reset by peer" error is printed client-side (in BLISS session) But hard to know which connection is closed:

SESSION_SXM [1]:
!!! === ConnectionResetError: [Errno 104] Connection reset by peer === !!!
SESSION_SXM [1]:
Edited May 17, 2021 by Cyril Guilloud
Assignee
Assign to
Time tracking