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

Closed
Open
Created Mar 08, 2015 by Administrator@rootOwner

Upgrading 7.4 to 7.8 with 502 errors

Created by: kitsos

I was update my gitlab server from 7.4 to 7.8 version. After succesful update. I am getting too much 502 Errors. I have 3GB RAM so I don't think is a resources issue. As far i can assume what the problem is I think there some malfunctionality on unicorn or on sidekiq. I see in my sidekiq shutting down approx. every 3 mins.

My unicorn.stderr.log is like this

`I, [2015-03-08T10:31:50.204069 #17629]  INFO -- : master complete
I, [2015-03-08T10:32:00.021882 #18661]  INFO -- : Refreshing Gem list
I, [2015-03-08T10:32:21.090756 #18661]  INFO -- : listening on addr=/home/git/gitlab/tmp/sockets/gitlab.socket fd=12
I, [2015-03-08T10:32:21.091238 #18661]  INFO -- : listening on addr=127.0.0.1:8080 fd=13
I, [2015-03-08T10:32:21.101911 #18661]  INFO -- : master process ready
I, [2015-03-08T10:32:21.213453 #18661]  INFO -- : reaped #<Process::Status: pid 18797 exit 0> worker=0
I, [2015-03-08T10:32:21.213613 #18661]  INFO -- : reaped #<Process::Status: pid 18799 exit 0> worker=1
I, [2015-03-08T10:32:21.213708 #18661]  INFO -- : master complete
I, [2015-03-08T10:32:25.578338 #18885]  INFO -- : Refreshing Gem list`

My sidekiq.log is like this

`2015-03-08T04:40:30.004Z 26513 TID-osq7tqpvo INFO: Running in ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux]
2015-03-08T04:40:30.004Z 26513 TID-osq7tqpvo INFO: See LICENSE and the LGPL-3.0 for licensing details.
2015-03-08T04:40:30.004Z 26513 TID-osq7tqpvo INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org/pro
2015-03-08T04:41:47.707Z 26513 TID-osq7tqpvo INFO: Shutting down
2015-03-08T04:41:48.039Z 26513 TID-osq96lyzw INFO: Shutting down 25 quiet workers
Sidekiq shut down gracefully.
Pidfile /home/git/gitlab/tmp/pids/sidekiq.pid does not exist
2015-03-08T04:42:36.024Z 27266 TID-otfzkli0s INFO: Booting Sidekiq 3.3.0 with redis options {:url=>"unix:/var/run/redis/redis.sock", :namespace=>"resque:gitlab"}` 

It is not always non-working, but fails every 4-10 clicks on my UI. So it is not usable. Is there any suggestion to fix it or I should rollback my installation?

Regards,

K.

Assignee
Assign to
Time tracking