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
  • #3389

Closed
Open
Created Mar 26, 2013 by Administrator@rootOwner

gitlab 5.0 redis issue with separate redis server.

Created by: leopku

I am using app&db splitting model. So my mysql & redis servers are all running in other machines alone with rails app.

Resque.yml was set with correct IP. But when starting gitlab, It seems gitlab still try connecting 127.0.0.1:6379. The error log was: cache error: Error connecting to Redis on 127.0.0.1:6379 (ECONNREFUSED)

Currently, I installed a redis-server in rails apps machine for a temporary solution.

Assignee
Assign to
Time tracking