Hi again!
New project this time around, I've been asked to look into updating our
Gitorious install at work, which hasn't been updated in quite some time. So
what I basically did, is clone the VM on which it is running, install a
parallel Gitorious Install manually (the same way it was originally
installed, with the newer versions and updated packages this time around),
dump the original database and create a new database on our database server
using the previously done dump. LDAP authentication works, so does the web
interface, I can browse the projects, etc.
Now I got pretty much everything thing to work, except for a couple of
hiccups. To test it out, I created a new project and tried to push a local
repository to it. The push seems to work (I can see the files I pushed and
the comment I wrote when I pushed it), but whenever I push, I get 2 e-mails:
An exception occured in #<PushProcessor:0x701bb78
@repository=
#<Repository id: 229, name: "test3", project_id: 38, user_id: 22,
created_at: "2013-03-21 17:30:42", updated_at: "2013-03-21 17:30:42",
parent_id: nil, ready: true, kind: 0, owner_type: "User", owner_id: 22,
hashed_path: "test3/test3", description: "", last_pushed_at: nil,
wiki_permissions: 0, deny_force_pushing: false,
notify_committers_on_new_merge_request: true, last_gc_at: nil,
merge_requests_enabled: true, disk_usage: nil, push_count_since_gc: nil>,
@spec=
#<PushSpecParser:0x7017578
@from_sha=
#<PushSpecParser::Sha:0x7017528
@sha="070312dc01970a7880e9a88d874febd032b9ff82">,
@ref=#<PushSpecParser::Ref:0x70174d8 @name="master", @type="heads">,
@to_sha=
#<PushSpecParser::Sha:0x7017500
@sha="41ffda943b6c89e75d6c2407f3753fcf10efa2aa">>,
@user=nil>
!
RuntimeError: Username was nil
/home/git/gitorious2/app/processors/push_processor.rb:84:in `ensure_user'
/home/git/gitorious2/app/processors/push_processor.rb:51:in
`process_push'
/home/git/gitorious2/app/processors/push_processor.rb:41:in
`on_message'
/home/git/gitorious2/lib/gitorious/messaging.rb:82:in `consume'
/home/git/gitorious2/lib/gitorious/messaging/stomp_adapter.rb:96:in
`on_message'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/processor.rb:32:in
`process!'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:232:in
`_dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:151:in
`execute_filter_chain'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:231:in
`_dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:222:in
`each'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:222:in
`_dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:207:in
`dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:204:in
`synchronize'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:204:in
`dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:45:in
`start'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:32
As well as this one:
An exception occured in #<PushProcessor:0x701bb78
@repository=
#<Repository id: 229, name: "test3", project_id: 38, user_id: 22,
created_at: "2013-03-21 17:30:42", updated_at: "2013-03-21 17:30:42",
parent_id: nil, ready: true, kind: 0, owner_type: "User", owner_id: 22,
hashed_path: "test3/test3", description: "", last_pushed_at: nil,
wiki_permissions: 0, deny_force_pushing: false,
notify_committers_on_new_merge_request: true, last_gc_at: nil,
merge_requests_enabled: true, disk_usage: nil, push_count_since_gc: nil>,
@spec=
#<PushSpecParser:0x7017578
@from_sha=
#<PushSpecParser::Sha:0x7017528
@sha="070312dc01970a7880e9a88d874febd032b9ff82">,
@ref=#<PushSpecParser::Ref:0x70174d8 @name="master", @type="heads">,
@to_sha=
#<PushSpecParser::Sha:0x7017500
@sha="41ffda943b6c89e75d6c2407f3753fcf10efa2aa">>,
@user=nil>
!
ActiveMessaging::AbortMessageException:
ActiveMessaging::AbortMessageException
/home/git/gitorious2/lib/gitorious/messaging/stomp_adapter.rb:106:in
`on_error'
/home/git/gitorious2/lib/gitorious/messaging/stomp_adapter.rb:98:in
`on_message'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/processor.rb:32:in
`process!'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:232:in
`_dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:151:in
`execute_filter_chain'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:231:in
`_dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:222:in
`each'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:222:in
`_dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:207:in
`dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:204:in
`synchronize'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:204:in
`dispatch'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:45:in
`start'
/opt/ruby-enterprise-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activemessaging-0.7.1/lib/activemessaging/gateway.rb:32
I noticed I don't an updated on my Activities panel when I do something
(like in this case, push something new). I'm still pretty new at Git
overall and slowly getting the hang of things, but this just confuses me.
Does it have something to do with the fact it's not the original
database/host pairing since I'm running on a new Database that's a dump of
the live one on a newly created virtual machine for testing purposes?
I say this, because whenever a programmer tried to push on one of the
original projects on the test machine, it would simply give him a Fatal
Error message (without any further explanation) so this had me thinking.
Any help would be greatly appreciated! Thanks!
--
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
---
You received this message because you are subscribed to the Google Groups
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
