Defect #11841

git log error: git exited with non-zero status: 128

Added by Paulo Castro over 10 years ago. Updated about 10 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution: Affected version:


I keep on seing this message in the logs whenever I hit the Repository tab in my project.

I'm quite sure this is the line generating the noise.

200:          cmd_args = %w|log --no-color --encoding=UTF-8 --raw --date=iso --pretty=fuller --parents --stdin|

SVN Version 10390

About your application's environment
Ruby version              1.8.7 (x86_64-linux)
RubyGems version          1.8.11
Rack version              1.4
Rails version             3.2.8
Active Record version     3.2.8
Action Pack version       3.2.8
Active Resource version   3.2.8
Action Mailer version     3.2.8
Active Support version    3.2.8
Middleware                Rack::Cache, ActionDispatch::Static, Rack::Lock, #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x7f9dda7aa588>, Rack::Runtime, Rack::MethodOverride, ActionDispatch::RequestId, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::DebugExceptions, ActionDispatch::RemoteIp, ActionDispatch::Callbacks, ActiveRecord::ConnectionAdapters::ConnectionManagement, ActiveRecord::QueryCache, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, ActionDispatch::Head, Rack::ConditionalGet, Rack::ETag, ActionDispatch::BestStandardsSupport, OpenIdAuthentication
Application root          /srv/redmine/redmine
Environment               production
Database adapter          mysql
Database schema version   20120731164049

Related issues

Related to Redmine - Defect #11842: Referencing issue in commit message not working. Closed
Related to Redmine - Defect #12505: Git: fetch_changesets returns a fatal error Closed


#1 Updated by Raphael Kallensee over 10 years ago

I have the same problem (with Redmine 2.0.3). But maybe this is depending on the git version. I have the error on one machine running Git (Debian Lenny), but on a machine with Git (Ubuntu Lucid) there are no problems - with the same repository (I pushed to both).

#2 Updated by Jan Kundrát about 10 years ago

#12505 (with a patch) looks like a duplicate of this one. If my assumption is correct, the problem is not realted to the version of git but to the frequency in which git gc is run.

Also available in: Atom PDF