プロジェクト

全般

プロフィール

Vote #73611

完了

Can't access SCM when log/production.scm.stderr.log is not writable

Admin Redmine さんが3年以上前に追加. 3年以上前に更新.

ステータス:
Closed
優先度:
高め
担当者:
-
カテゴリ:
SCM_3
対象バージョン:
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
3
version_id:
71
issue_org_id:
13541
author_id:
37941
assigned_to_id:
1
comments:
3
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
60
ステータス-->[Closed]

説明

Our git repository viewer has stopped working since we have upgraded to redmine 2.3.0 (and rails 3.2.13).

The message is "404 The entry or revision was not found in the repository." and the accompanying log message is:

Started GET "/projects/knot-dns/repository" for 109.81.193.205 at 2013-03-20 19:25:24 +0100
Processing by RepositoriesController#show as HTML
  Parameters: {"id"=>"knot-dns"}
  Current user: oerdnj (id=3)
  Rendered common/error.html.erb within layouts/base (0.2ms)
Completed 404 Not Found in 208ms (Views: 151.5ms | ActiveRecord: 11.6ms)

Our current environment is:

Ruby version              1.9.3 (x86_64-linux)
RubyGems version          1.8.11
Rack version              1.4
Rails version             3.2.13
Active Record version     3.2.13
Action Pack version       3.2.13
Active Resource version   3.2.13
Action Mailer version     3.2.13
Active Support version    3.2.13
Middleware                Rack::Cache, ActionDispatch::Static, Rack::Lock, #, 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          /usr/share/redmine
Environment               production
Database adapter          postgresql
Database schema version   20130217094251

journals

Ok, I have nailed it down to 30801ca9, which makes to shellout fail when log file is not writeable.

The shellout command dies without an explicit notice/traceback, which makes it very hard to debug.

I am not sure while the stderr is logged in any environment (not just development), but when you do, you should probably create the file from Ruby to ensure correct permissions, etc. and then write to it from shell, so error like this can be caught before the shell is run.
--------------------------------------------------------------------------------
stderr is now logged only when log level is set to debug (r11680). Thanks for pointing this out.
--------------------------------------------------------------------------------
Merged.
--------------------------------------------------------------------------------

Admin Redmine さんが3年以上前に更新

  • カテゴリSCM_3 にセット
  • 対象バージョン2.3.1_71 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0