Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2197

Closed
Open
Created Dec 06, 2012 by Administrator@rootOwner

almost all reque jobs fail with PostgreSQL error

Created by: ikari-pl

I got a fresh gitlab installation, created some repos, imported some more. My redis stats say:

  • processed: 85
  • failed: 72

almost everything fails, but probably after restarting gitlab and restarting failed tasks, some pass. On the other hand, some seem to pass multiple times (so I have the same "ikari has pushed" notification repeated 3 times, with different timestmps).

There are only two kinds of failures in the log:

  • Class: PostReceive Exception: ActiveRecord::StatementInvalid Error: PG::Error: ERROR: prepared statement "a1" already exists : INSERT INTO "events" ("action", "author_id", "created_at", "data", "project_id", "target_id", "target_type", "title", "updated_at") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9) RETURNING "id"
  • Class: Notify Arguments: "project_access_granted_email" Exception: ActiveRecord::StatementInvalid Error: PG::Error: ERROR: prepared statement "a1" already exists : SELECT "users_projects".* FROM "users_projects" WHERE "users_projects"."id" = $1 LIMIT 1

I have no idea what I'm doing (and what I'm doing wrong), I have no experience with ruby, unfortunately. Switching between 1, 2 and 3 workers was the only modification I tried, doesn't change much (as it seemed to work for @rbrtmlnr under similar, but solved, #1015)

Assignee
Assign to
Time tracking