Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 485
    • Issues 485
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 23
    • Merge Requests 23
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #1668

Closed
Open
Opened Nov 21, 2011 by Oliver Vogel@vogelor

key error with monitor-data

Sometimes there is a duplicateed key error when the monitor tries to save its data.

To avoid this, we can

  1. delete the key (not so good, because then we have no key for the table ;-)
  2. use update into instead of insert into. this statement executes the record if there is another one with the same key
  3. if 2) will not help, we can maybe change the index from unique to index only
Assignee
Assign to
3.0.5
Milestone
3.0.5
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#1668