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

Closed
Open
Created Sep 03, 2013 by Administrator@rootOwner

MySQL ActiveRecord::StatementInvalid error when creating big merge requests

Created by: aiurm

Hi,

when I am creating merge requests with many differences (commits and/or files) an internal server error (500) occurs.

I seems that the MySQL update statement is too long. The corresponding line in production.log has more than 2000000 characters! Smaller merge requests are handled without any error.

Error from production.log:

ActiveRecord::StatementInvalid (Mysql2::Error: MySQL server has gone away: 
UPDATE `merge_requests` SET `st_commits` = '...many many changes...', 
`updated_at` = '2013-09-03 09:16:30', `st_diffs` = '--- \n...\n' 
 WHERE `merge_requests`.`id` = 65):

Output of checks:

Checking Environment ...

Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.7.0 ? ... OK (1.7.0)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ...
PIET / P7525_EASS ... ok
PIEE / P6003_Test_DM ... repository is empty
...other repos (all ok or empty)...
Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have satellites? ...
PIET / P7525_EASS ... yes
PIEE / P6003_Test_DM ... yes
...other repos (all ok)...
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.11)

Checking GitLab ... Finished

Versioninfo

  • Gitlab 6.0.0 6c1c2842
  • Gitlab-Shell 1.7.0
  • Git 1.7.11
  • Ruby 1.9.3p194
  • Gem 2.0.3
  • Bundler 1.3.5
  • Rake 10.1.0
Assignee
Assign to
Time tracking