Still similar errors in the logs, or something new?
cheers,
Thomas
On 09/24/2012 10:19 PM, Jacob Blinn wrote:
Alright, I've checked and double-checked the permissions and I am
still receiving the same error when trying to push. Doesn't seem to
matter what system we are pushing from. Client side says:
== Gitorious: ==========================================================
fatal error
========================================================================
fatal: The remote end hung up unexpectedly
On Monday, September 24, 2012 11:39:54 AM UTC-7, Thomas Kjeldahl
Nilsson wrote:
Hi Jacob,
the entire Gitorious repo/file tree should be owned by whatever
user owns your other Gitorious processes, the same user defined in
gitorious_user in config/gitorious.yml (generally 'git'). So do a
'chown -r git:git *' in the Gitorious root directory (same
directory as Gemfile, Rakefile etc) and you should be good to go.
cheers,
Thomas
On 09/24/2012 08:22 PM, Jacob Blinn wrote:
OK, Now that we've completely upgraded to 2.3.0, when we try to
push this is the error we get:
F, [2012-09-24 11:19:27#32728] FATAL -- : SocketError
getaddrinfo: Servname not supported for ai_socktype:
/usr/lib/ruby/1.8/net/http.rb:560:in `initialize'
/usr/lib/ruby/1.8/net/http.rb:560:in `open'
/usr/lib/ruby/1.8/net/http.rb:560:in `connect'
/usr/lib/ruby/1.8/timeout.rb:53:in `timeout'
/usr/lib/ruby/1.8/timeout.rb:101:in `timeout'
/usr/lib/ruby/1.8/net/http.rb:560:in `connect'
/usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
/usr/lib/ruby/1.8/net/http.rb:548:in `start'
/usr/lib/ruby/1.8/net/http.rb:440:in `start'
/var/www/gitorious/script/../lib/gitorious/ssh/client.rb:106:in
`connection'
/var/www/gitorious/script/../lib/gitorious/ssh/client.rb:86:in
`configuration'
/var/www/gitorious/script/../lib/gitorious/ssh/client.rb:60:in
`real_path'
/var/www/gitorious/script/../lib/gitorious/ssh/client.rb:74:in
`to_git_shell_argument'
/var/www/gitorious/script/gitorious:60
What permissions should the files have?
On Saturday, September 22, 2012 7:37:10 AM UTC-7, Ken Dreyer wrote:
On Fri, Sep 21, 2012 at 3:34 PM, Jacob Blinn
<[email protected]> wrote:
> We are getting this error whenever we navigate to the HTTPS
side to login.
> Nothing on the server has actually changed so I can't tell
why suddenly we
> get this error. It seems to only happen in Chrome, but
Firefox will load and
> allow logins fine, it just has a 5-10 second load time. Any
Ideas where to
> go on this?
Do you have a full backtrace in the logs?
- Ken
--
To post to this group, send email to [email protected]
<javascript:>
To unsubscribe from this group, send email to
[email protected] <javascript:>
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
