Thomas,

My Ruby version is:
# ./ruby --version
ruby 1.8.7 (2012-02-08 MBARI 8/0x6770 on patchlevel 358) [x86_64-linux], 
MBARI 0x6770, Ruby Enterprise Edition 2012.02

/proc info for the processes seems to confirm that version 1.8.7 is in fact 
being used (/opt/ruby is a symlink to my Ruby Enterprise directory).

# ps aux | grep ruby
git       4582  0.0  1.5  94620 15600 ?        S    Aug09   0:27 
/opt/ruby/bin/ruby /usr/bin/stompserver -w /var/www/gitorious/tmp/stomp -q 
file -s queue
git       4614  0.0 13.9 269068 142244 ?       S    Aug09   0:00 ruby 
/var/www/gitorious/script/git-daemon -d
# ls -la /proc/4614/exe
lrwxrwxrwx. 1 git apache 0 Aug 10 03:05 /proc/4614/exe -> 
/opt/ruby-enterprise-1.8.7-2012.02/bin/ruby

Although, if I'm not mistaken Passenger should be using a Ruby interpreter 
as well. I'm unsure how to figure out which one it's using.

Thanks!


On Friday, August 10, 2012 2:55:28 AM UTC-4, Thomas Kjeldahl Nilsson wrote:
>
>  
> Taking a look at this later today, haven't seen this on our end. BTW which 
> specific Ruby version are you running the processes on?
>
> cheers,
> Thomas
>
>
> On 08/09/2012 07:58 PM, esc201 wrote:
>  
> Hi Thomas,
>
>  Thanks for the reply!
>
>  I pulled your changes and rebooted my server, and while the "gitdir" 
> error is now gone, it seems to have been replaced with another error.
>
>  NoMethodError: undefined method `wiki?' for nil:NilClass
>
>  The other error still persists as well.
>
> ActiveMessaging::AbortMessageException: ActiveMessaging::AbortMessageException
>
>  
>  
>  Backtraces: 
> http://pastebin.com/13g5A7Jy
> http://pastebin.com/cZgwiVh4
>
>  The config I'm using is:
>
>  production:
>   cookie_secret: ******
>   repository_base_path: "/home/git/repos"
>   site_name: ******
>   use_ssl: true
>   gitorious_client_port: 80
>   gitorious_client_host: localhost
>   gitorious_host: *****
>   gitorious_user: git
>   exception_notification_emails: *****
>   gitorious_support_email: *****
>   mangle_email_addresses: false
>   public_mode: false
>   locale: en
>   archive_cache_dir: "/home/git/tarballs"
>   archive_work_dir: "/home/git/tarball-work"
>   only_site_admins_can_create_projects: false
>   hide_http_clone_urls: false
>   is_gitorious_dot_org: false
>
>  I'm still new to Gitorious, but I think everything in there is at least 
> relatively normal.
>
>  Would it make any difference if I'm using Ruby Enterprise?
>
>  Thanks again!
>
>
> On Thursday, August 9, 2012 4:03:46 AM UTC-4, Thomas Kjeldahl Nilsson 
> wrote: 
>>
>>  Hi there,
>>
>> this appears to be a bug that was introduced way back in February, but 
>> for some reason hasn't show up anywhere else so far (that we know of!). 
>> Perhaps something specific to your config?
>>
>> Anyway, I've pushed a fix to mainline now. Pull and let us know if it 
>> resolves your errors. 
>>
>> cheers,
>> Thomas
>>
>>
>> On 08/09/2012 09:53 AM, esc201 wrote:
>>  
>> Hi all, 
>>
>>  I just installed Gitorious (cloned from master branch on mainline) and 
>> am getting two errors emailed to me whenever I push to any repo. If it 
>> matters, in a failed attempt to solve this problem, I re-cloned Gitorious 
>> just a few hours ago, but left the database and repos directory intact.
>>
>>  In short, the errors are:
>>
>>  NoMethodError: undefined method `gitdir' for nil:NilClass
>>
>> and
>>
>> ActiveMessaging::AbortMessageException: 
>> ActiveMessaging::AbortMessageException
>>
>> Full backtraces are here:
>>
>> http://pastebin.com/xmRCmUhm
>>
>> http://pastebin.com/cZgwiVh4
>>
>>  Strangely enough, pushing still seems to work fine. That is, the pushed 
>> code still shows up in a browser properly and git reports no errors client 
>> side.
>>
>>  Any ideas?
>>
>>  Thank you!
>>
>>  -- 
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>>
>>
>>
>> -- 
>> best regards,
>> Thomas Kjeldahl Nilssonhttp://gitorious.com
>>
>>   
>
> -- 
> best regards,
> Thomas Kjeldahl Nilssonhttp://gitorious.com
>
>  

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to