Hi Pawel,
Install worked a charm, and I am all up and running. I have done a few basic
operations such as push and pull and have created a few projects to test out
correct functionality. Unfortunately I have hit a few snags though :-(.
- When I try to delete a project from the web UI it returns a 500 error page.
- When I try to delete project from console it returns the following:
[root@git-stream10 ~]# /var/www/gitorious/app/bin/console
WARNING! No value set for exception_recipients in gitorious.yml.
Will not be able to send email regarding unhandled exceptions
/var/www/gitorious/app/app/validators/user_validator.rb:31: warning: toplevel
constant MIN_LENGTH referenced by PasswordValidator::MIN_LENGTH
Both MergeRequest and its :status machine have defined a different default for
"status". Use only one or the other for defining defaults to avoid unexpected
behaviors.
irb(main):001:0> project = Project.find_by_slug("robertputt-test")
=> #<Project id: 2, title: "RobertPutt Test", description: "Personal project
for performing GIT functionality t...", user_id: 1, created_at: "2013-12-16
16:01:04", updated_at: "2013-12-16 16:01:04", slug: "robertputt-test", license:
"Academic Free License v3.0", home_url: nil, mailinglist_url: nil,
bugtracker_url: nil, owner_id: 1, owner_type: "User", wiki_enabled: true,
site_id: nil, merge_requests_need_signoff: false, oauth_signoff_key: nil,
oauth_signoff_secret: nil, oauth_signoff_site: nil, oauth_path_prefix: nil,
merge_request_custom_states: [], suspended_at: nil>
irb(main):002:0> project.destroy
ThinkingSphinx::SphinxError: unknown index 'project_core' in update request
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/connection.rb:78:in
`rescue in execute'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/connection.rb:74:in
`execute'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/deletion.rb:27:in
`block in execute'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/connection.rb:38:in
`block in take'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/innertube-1.1.0/lib/innertube.rb:138:in
`take'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/connection.rb:36:in
`take'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/deletion.rb:26:in
`execute'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/deletion.rb:41:in
`perform'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/deletion.rb:8:in
`perform'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/active_record/callbacks/delete_callbacks.rb:7:in
`block in after_destroy'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/active_record/callbacks/delete_callbacks.rb:7:in
`each'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/active_record/callbacks/delete_callbacks.rb:7:in
`after_destroy'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/thinking-sphinx-3.0.6/lib/thinking_sphinx/callbacks.rb:7:in
`block (2 levels) in callbacks'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:310:in
`_callback_after_39'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:493:in
`_run__501851049709665248__destroy__2411722913464129458__callbacks'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:405:in
`__run_callback'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:385:in
`_run_destroy_callbacks'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.14/lib/active_support/callbacks.rb:81:in
`run_callbacks'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.14/lib/active_record/callbacks.rb:254:in
`destroy'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.14/lib/active_record/transactions.rb:254:in
`block in destroy'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.14/lib/active_record/transactions.rb:313:in
`block in with_transaction_returning_status'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.14/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in
`transaction'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.14/lib/active_record/transactions.rb:208:in
`transaction'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.14/lib/active_record/transactions.rb:311:in
`with_transaction_returning_status'
from
/var/www/gitorious/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.14/lib/active_record/transactions.rb:254:in
`destroy'
from (irb):2
from /var/www/gitorious/app/bin/console:6:in `block in <main>'
from /var/www/gitorious/app/bin/setup.rb:33:in
`run_with_gitorious_environment'
from /var/www/gitorious/app/bin/console:3:in `<main>'irb(main):003:0>
Now, I admit I am a bit of a noob when it comes to Ruby, unfortunately I am a
Java, Perl and Python man. I am guessing "run_with_gitorious_environment" may
suggest I am not running it the right ENV settings setup prior to running the
console script. Hopefully you can enlighten me.
- Final problem on my list, I have created a snapshot fine using the following
command...
cd /var/www/gitorious/app/ && script/snapshot
/tmp/gitorioussnapshot-16-12-13.tar
Works great, although when I try todo a test restore for this snapshot I find
that script/restore does not exist. Is this a known issue, or is the installer
some how broken and does not pull this script as it should?
Sorry to give you a lot of work, hopefully these are all things which can be
used to help other users also.
Best Regards,
Rob
On Monday, 16 December 2013 15:36:26 UTC, Robert Putt wrote:
> On Monday, 16 December 2013 10:29:56 UTC, Paweł Pierzchała wrote:
>
> > Hi Robert,
>
> > I've removed all the git:// urls from the app, now gems and submodules use
> > https protocol. Ce-installer still installs 3.0.0, we are going to release
> > another version and update the ce-installer in couple of days, but if you
> > don't want to wait, you could try installing Gitorious version with the fix
> > by setting '30d878caa18278d2af85211977e9a8ad91b3e5f5' as gitorious::version
> > in ce-installer/manifests/nodes.pp
>
> >
>
> >
>
> >
>
> >
>
> > Cheers,
>
> > Pawel
>
> >
>
> >
>
> >
>
> > On Fri, Dec 13, 2013 at 11:04 PM, Robert Putt <[email protected]> wrote:
>
> >
>
> >
>
> >
>
> > On Friday, 13 December 2013 19:22:08 UTC, Robert Putt wrote:
>
> >
>
> > > Hi All,
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Following the previous post regarding installation issues with CentOS 6.4
> > > and 6.5 and the SSL issue being resolved with Ruby I am still running
> > > into issues with the de-installer script. Hopefully you can help.
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Just to clarify, I am installing this on a newly installed CentOS 6.4
> > > host with a minimal install with no previous installation of puppet or
> > > ruby.
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > So far I have installed git from yum, cloned the installer as per the
> > > docs at getgitorious and ran the install script... All appears good until
> > > the puppet recipe starts installing and I see a lot of the following
> > > outputs.
>
> >
>
> >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Error:
> > > /Stage[main]/Gitorious::Core/Exec[init_gitorious_submodules]/returns:
> > > change from notrun to 0 failed: env GIT_SSL_NO_VERIFY=true git submodule
> > > update --init --recursive returned 1 instead of one of [0]
>
> >
>
> > >
>
> >
>
> > > Error: sh -c 'export GIT_SSL_NO_VERIFY=true && cd /var/www/gitorious/app
> > > && bundle install --deployment --without development test && env
> > > GIT_SSL_NO_VERIFY=true git submodule update --init --recursive && chown
> > > -R git:git db vendor && bin/rake db:migrate && touch
> > > /tmp/post_version_upgrade_done' returned 1 instead of one of [0]
>
> >
>
> >
>
> >
>
> > >
>
> >
>
> > > Error:
> > > /Stage[main]//Node[gitorious-ce]/Gitorious::Version[942b6ef1b16efcb10745cf75a0c377e13ee77875]/Exec[post_version_upgrade]/returns:
> > > change from notrun to 0 failed: sh -c 'export GIT_SSL_NO_VERIFY=true &&
> > > cd /var/www/gitorious/app && bundle install --deployment --without
> > > development test && env GIT_SSL_NO_VERIFY=true git submodule update
> > > --init --recursive && chown -R git:git db vendor && bin/rake db:migrate
> > > && touch /tmp/post_version_upgrade_done' returned 1 instead of one of [0]
>
> >
>
> >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > After 15 attempts it gives up. If you would like some detail from the
> > > puppet log let me know.
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > I am confused as to why this isn't working. Please can you guys offer an
> > > insight into what I am doing wrong.
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Best Regards,
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Rob
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Hi,
>
> >
>
> >
>
> >
>
> > I have worked out the problem here, during the puppet recipe it tries to
> > clone from github for eve using git://. Unfortunately within our labs port
> > 9418 is blocked to the outside world, leaving us with just the ability to
> > http or ssh clone.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > This poses a bit of a problem because it means I cannot install gitorious,
> > and they will not agree to open this port.
>
> >
>
> >
>
> >
>
> > I have tried a recursive grep on the installation scripts in ce-installer
> > to try and see where this is referenced to do a cheeky swap to http
> > cloning. Although I cannot find it, I can only assume this script is pulled
> > dynamically as part of the recipe.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Please can you advise on how I can install gitorious without access to the
> > outside world via port 9418?
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Best Regards,
>
> >
>
> >
>
> >
>
> > Rob
>
> >
>
> >
>
> >
>
> > --
>
> >
>
> > --
>
> >
>
> > 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.
>
>
>
> Hi Pawel,
>
>
>
> Thanks for the quick update and thanks for your help. I'll give it a go now.
> I am sure this is a feature which will be attractive to other users also as I
> can imagine a lot of users having strict firewall rules which are enforced
> which are out of their control. It took me long enough to convince our
> college to open up SSH to the lab so we could login from other locations. :-(.
>
>
>
> Regards,
>
>
>
> Rob
--
--
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.
