Non-stop "Loading commit data" in 5.2
Closed
Non-stop "Loading commit data" in 5.2
Created by: drakeguan
I believe there is something specific to my setup. I have run through all possible check mentioned in https://github.com/gitlabhq/gitlabhq/blob/master/doc/raketasks/maintenance.md and nearly every checks passed except bundle exec rake gitlab:app:check RAILS_ENV=production
Redis version >= 2.0.0? ... yes
rake aborted!
undefined method `match' for nil:NilClass
/home/git/gitlab/lib/gitlab/version_info.rb:8:in `parse'
/home/git/gitlab/lib/tasks/gitlab/check.rake:671:in `check_git_version'
/home/git/gitlab/lib/tasks/gitlab/check.rake:27:in `block (3 levels) in <top (required)>'
I then go checking production log in admin/log and found out the following stuff:
ActionView::Template::Error (undefined method `committed_date' for nil:NilClass):
4:
5: :plain
6: var row = $("table.table_#{@hex_path} tr.file_#{hexdigest(file_name)}");
7: row.find("td.tree_time_ago").html('#{escape_javascript time_ago_in_words(commit.committed_date)} ago');
8: row.find("td.tree_commit").html('#{escape_javascript render("tree/tree_commit_column", commit: commit)}');
app/views/refs/logs_tree.js.haml:7:in `block in _app_views_refs_logs_tree_js_haml__1324518347852395915_51408880'
app/views/refs/logs_tree.js.haml:1:in `each'
app/views/refs/logs_tree.js.haml:1:in `_app_views_refs_logs_tree_js_haml__1324518347852395915_51408880'
Wondering if there is something data migration issue or mistakes I have done. Looking forward any hints or help for this.
Created by: KosmicTask
Ubuntu 12 2GB VM GitLab 5.2 Apache + Passenger
I am seeing something similar, though not exactly the same. In this case the process does conclude after 679 secs.
My production log says:
Rendered notes/_diff_note_link.html.haml (1.0ms) Rendered notes/_diff_note_link.html.haml (0.9ms) Rendered notes/_diff_note_link.html.haml (1.0ms) Rendered notes/_diff_note_link.html.haml (1.0ms) Rendered notes/_diff_note_link.html.haml (1.0ms) Rendered commits/_text_file.html.haml (530.2ms) Rendered commits/_diffs.html.haml (669202.8ms) Rendered commit/show.html.haml within layouts/project_resource (679327.8ms) Encoding::CompatibilityError (incompatible character encodings: UTF-8 and ASCII-8BIT): app/views/commits/_diffs.html.haml:45:in `block in _app_views_commits__diffs_html_haml___839163854986264234_70159369438840' app/views/commits/_diffs.html.haml:17:in `each' app/views/commits/_diffs.html.haml:17:in `each_with_index' app/views/commits/_diffs.html.haml:17:in `_app_views_commits__diffs_html_haml___839163854986264234_70159369438840' app/views/commit/show.html.haml:10:in `_app_views_commit_show_html_haml__475218855358637448_62145880' Rendered errors/encoding.html.haml within layouts/errors (2.8ms) Rendered layouts/_head.html.haml (5.6ms) Rendered layouts/_search.html.haml (89.4ms) Rendered layouts/_head_panel.html.haml (103.7ms) Rendered layouts/_flash.html.haml (0.7ms) Completed 500 Internal Server Error in 690921ms (Views: 136.2ms | ActiveRecord: 19.6ms)
On some occasions, perhaps on page reload, I do receive
Diff is too large to display
However, this problem is a real killer.
I pushed the same project that caused this issue onto Github. The stats are
Showing 45 changed files with 202,268 additions and 190 deletions.
The generated commit page was 3MB and rendered in a few seconds.
By Administrator on 2013-06-05T15:29:55 (imported from GitLab project)
Created by: drakeguan
My issue is just got solved after I spot that the path to git is different in my site. The default path for git is /usr/bin/git while mine is /usr/local/bin/git. I just change the path in gitlab.yml and restart the sever, then it works.
By Administrator on 2013-06-05T15:59:48 (imported from GitLab project)
Created by: shibz
I had this issue with a non-stop "Loading commit data" on my CentOS 6 GitLab server because the RHEL 6 default version of Git is too old (I had 1.7.1, but it needs to be at least 1.7.10). I was able to solve it by removing the default version and installing the RpmForge version.
By Administrator on 2013-08-14T17:10:43 (imported from GitLab project)
Created by: KosmicTask
I upgraded my Git installation to post 1.7.10 without effect. The amount of logging activity to production.log continues to fairly prodigious. This alone may be causing a problem on what is a VPS installation. IO in such situations is always contended.
Is there anyway to limit the writes to production.log?
By Administrator on 2013-08-15T14:32:13 (imported from GitLab project)