Gitlab stuck on: "Checking for ability to automatically merge" for Merge Request

[sabhiram]

Hey Sameer - this is an awesome project and we use it for our development env daily. Things have been going smoothly so far, except today when I tried to merge a request - I got stuck on "Checking for ability to automatically merge...".

I tried the few things mentioned here: https://github.com/gitlabhq/gitlabhq/issues/1104 to no avail.

Would appreciate a pointer when you get to it. Also seems like when I try to run the container from inside the w/ docker exec, I am unable to kick off the rake job to enable automerges etc.

Any help would be appreciated! thanks!

[sameersbn]

@sabhiram I don't know what the issue could be or how to fix it. You should report it to the upstream gitlab project.

What database server are you using? If its mysql then it is probably the cause of your issue.

[sameersbn]

@sabhiram If you do use mysql then you can take a look at #125

[sabhiram]

Oh doh - it is mysql... I will attempt to bump the packet size right now and report back. Wish I knew about this sooner lol. Thanks for the pointer @sameersbn

[sabhiram]

The strange thing is - the instance also fails to allow me to fetch any of the downloads via the download buttons. Regardless of if it is a zip or a diff or a release. To make matters more awesome - we run a SELinux host, and use an NFS file mount :)

Worst case ill scratch it on a dedicated VM :)

[sameersbn]

@sabhiram that is one of the reason why there is a Recommended against Postgresql in the readme 😄

[sabhiram]

@sameersbn - I guess what is strange to me is the fact that even plain text diffs do not download, nor do archives of git projects. I can try and whip up a postgres db and see where it lands - do you know if the other (download) issues occur (potentially) due to the sql container?

[sameersbn]

@sabhiram no idea. I am only aware of merge issues so far.

[johnjelinek]

This is happening to me too, and I'm using postgres 9.4.

[sabhiram]

Yep, I still use sameer's awesome other dockerfiles, but something as vital as gitlab should not be down for small organizations. We moved to a dedicated smartOS vm for gitlab that is snapshotted every hour or so.

[sameersbn]

@johnjelinek what version of gitlab are you using. Do you notice anything in the logs? Try looking up the logs in the /var/log/gitlab directory.

[sameersbn]

@johnjelinek @sabhiram can you please take a look at https://github.com/gitlabhq/gitlabhq/issues/1104

[sameersbn]

Also take a look at https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide

You might also want to try starting the container with app:sanitize argument to make sure that all files and directories have the right ownership and permissions as it is listed as a probable cause of the issue.

If that does not help, the please try launching the raketask to create the satellites directories https://github.com/gitlabhq/gitlabhq/blob/master/doc/raketasks/maintenance.md#re-create-satellite-repositories. Refer to the README on how to launch raketasks.

[sameersbn]

@johnjelinek let me know if any of the above suggestions fixes the issue.

[johnjelinek]

I'm using 7.11.4 and I grepped the logs and didn't find anything.

On Wed, Jun 24, 2015 at 12:03 PM, Sameer Naik notifications@github.com
wrote:

Also take a look at
https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide

You might also want to try starting the container with app:sanitize
argument to make sure that all files and directories have the right
ownership and permissions as it is listed as a probable cause of the issue.

If that does not help, the please try launching the raketask to create the
satellites directories
https://github.com/gitlabhq/gitlabhq/blob/master/doc/raketasks/maintenance.md#re-create-satellite-repositories.
Refer to the README on how to launch raketasks.

—
Reply to this email directly or view it on GitHub
#313 (comment)
.

[sameersbn]

@johnjelinek please do try the other suggestions and let me know. Thank you.

[simkin]

I am having the same issue. upping the max_allowed_packet value in my.cn did not fix it for me. Log files contain no obvious errors.

GitLab 7.12.1 f6fb946 on Centos

[sameersbn]

@simkin can you please try the suggestions in #313 (comment)

[simkin]

I upgrade to the latest version 7.13.2 that resolved the issue, thanks for your suggestion though!

[sameersbn]

@simkin great!