HTTP 500 when editing a file

Created by: almereyda

hi ppl,

when commiting changes to any file with the UI, gitlab (4.0.0) throws a HTTP 500 error.

log does say

Completed 500 Internal Server Error in 277ms

RuntimeError (Satellite doesn't exist):
lib/gitlab/satellite/satellite.rb:38:in `lock'
lib/gitlab/satellite/action.rb:21:in `block in in_locked_and_timed_satellite'
lib/gitlab/satellite/action.rb:20:in `in_locked_and_timed_satellite'
lib/gitlab/satellite/edit_file_action.rb:22:in `commit!'
app/controllers/tree_controller.rb:30:in `update'

i'm running gitlab on http://uberspace.de, some kind of shared hosting.

Created by: Razer6

Have you created the satellites? What does sudo -u gitlab -H bundle exec rake gitlab:check RAILS_ENV=production say?

By Administrator on 2013-01-27T21:47:03 (imported from GitLab project)

By Administrator on 2013-01-27T21:47:03 (imported from GitLab)

Created by: almereyda

hmm, it seems there are no satellites, you're right. but i'm also using non-standard installation on a hosted service, where I have no root access. ( uberspace.de )

let's see how far we can bring this with the 4.2 update.

By Administrator on 2013-02-28T00:41:01 (imported from GitLab project)

By Administrator on 2013-02-28T00:41:01 (imported from GitLab)

Created by: yuribf

I got a similar issue. I got the following error when trying to create satellites: cannot load such file -- rb-inotify

Adding RAILS_ENV=production to the command solved it

By Administrator on 2013-08-27T08:24:12 (imported from GitLab project)

By Administrator on 2013-08-27T08:24:12 (imported from GitLab)

Created by: Razer6

@yuribf RAILS_ENV=production is necessary because otherwise it tries to load some debug-gems!

By Administrator on 2013-08-27T08:27:06 (imported from GitLab project)

By Administrator on 2013-08-27T08:27:06 (imported from GitLab)