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

Closed
Open
Created May 11, 2015 by Administrator@rootOwner

Enabling gitlab ci causes nginx error

Created by: DazWorrall

On an omnibus install, I enabled gitlabci in gitlab.rb according to the docs (setting ci_external_url), ran gitlab-ctl reconfigure without error but I couldn't reach the CI server. Checking the logs, nginx failed to reload with the following error:

2015-05-11_08:38:52.94967 2015/05/11 09:38:52 [emerg] 937#0: could not build the server_names_hash, you should increase server_names_hash_bucket_size: 32

I put server_names_hash_bucket_size 64; into /var/opt/gitlab/nginx/conf/nginx.conf and manually sent a HUP and that solved it. 2 issues then:

  1. The default bucket size is too small
  2. The failure to reload nginx didnt raise an error when I ran gitlab-ctl reconfigure
Assignee
Assign to
Time tracking