Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • U ucollect
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Turris
  • ucollect
  • Issues
  • #54
Closed
Open
Created Feb 10, 2017 by Ghost User@ghostContributor

Key error when a message from unknown plugin arrives

When the collect master receives a message from unknown plugin, it raises a key error and terminates the connection. This, while not generally happening, should be handled more gracefully.

How to reproduce: enable the plugin in the client, in the database (in known plugins ‒ in the debug setup all are enabled by default) and do not enable it in the master's configuration. Choose a plugin that does send a message during startup to get the error right away (eg. flow).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking