i'm trying to install the gitlab-vagrant-vm from these repository: https://github.com/gitlabhq/gitlab-vagrant-vm
if i'm running
bundle exec rake gitlab:test it runs the test with all it's cases and checks.
but the summary gives me following lines of error.
Error summary:
Errors (1)
Project Issue Tracker :: I set the issue tracker to "Redmine" :: And change the issue tracker to "Redmine"
Steps Summary: (1379) Successful, (0) Undefined, (0) Pending, (0) Failed, (1) Error
Coverage report generated for RSpec to /vagrant/gitlabhq/coverage. 4937 / 7059 LOC (69.94%) covered.
rake aborted!
Command failed with status (1): [/opt/rbenv/versions/2.0.0-p247/bin/ruby -S...]
Tasks: TOP => spinach
(See full trace by running task with --trace)
rake aborted!
rake spinach failed!
/vagrant/gitlabhq/lib/tasks/gitlab/test.rake:15:in `block (3 levels) in '
/vagrant/gitlabhq/lib/tasks/gitlab/test.rake:12:in `each'
/vagrant/gitlabhq/lib/tasks/gitlab/test.rake:12:in `block (2 levels) in '
Tasks: TOP => gitlab:test
(See full trace by running task with --trace)
vagrant#precise32:/vagrant/gitlabhq$
what's this error about, and how to fix it? i really want to work with gitlab, and trying for several days now...
i am using:
osx 10.9 with server 3
vagrant 1.3.5
virtualbox 4.3
in the vagrant vm i ran "apt-get update / upgrade" to get the latest ubuntu
greetz!
Related
I am using the Bitnami Redmine Stack 3.3.1-0 on Ubuntu 16.04.2 LTS.
I recently installed a plugin (Issue Templates - http://www.redmine.org/plugins/redmine_issue_templates).
In the process, I updated the gems using bundle install and bundle update.
After performing this update, the Redmine website no longer works. I get the error:
"We're sorry, but something went wrong. We've been notified about this issue and we'll take a look at it shortly."
Upon analyzing the apache error log, I find the error:
"Could not find rake-12.3.0 in any of the sources (Bundler::GemNotFound)"
However, I have checked /opt/bitnami/apps/redmine/htdocs/vendor/ and /opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems and rake-12.3.0 is included in both locations. I am not sure why this issue is occuring.
I uninstalled the plugin and removed the files, but I still have the issue. I tried bundle install, bundle update, gem install rake -v '12.3.0', bundle exec rake rails:update:bin in the /opt/bitnami/apps/redmine/htdocs/ folder, and I also tried ./gem update in the /opt/bitnami/ruby/bin folder, but I still have the issue.
Please advise me what to do.
[ 2018-03-15 15:35:23.8349 28957/7f4ce96ec700 age/Hel/Req/CheckoutSession.cpp:252 ]: [Client 4-1] Cannot checkout session because a spawning error occurred. The identifier of the error is 35671c4a. Please see earlier logs for details about the error.
App 4445 stdout:
App 4445 stderr: /opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/lib/phusion_passenger/config/system_metrics_command.rb:34: warning: Insecure world writable dir /opt/bitnami/ruby/bin in PATH, mode 040757
App 4445 stdout:
[ 2018-03-15 15:35:29.9175 28957/7f4ce86a9700 App/Implementation.cpp:287 ]: Could not spawn process for application /opt/bitnami/apps/redmine/htdocs/: An error occured while starting up the preloader.
Error ID: 16a39427
Error details saved to: /tmp/passenger-error.3ZEVOb
Message from application: <p>It looks like Bundler could not find a gem. Maybe you didn't install all the gems that this application needs. To install your gems, please run:</p>
<pre class="commands">bundle install</pre>
<p>If that didn't work, then the problem is probably caused by your application being run under a different environment than it's supposed to. Please check the following:</p>
<ol>
<li>Is this app supposed to be run as the <code>daemon</code> user?</li>
<li>Is this app being run on the correct Ruby interpreter? Below you will
see which Ruby interpreter Phusion Passenger attempted to use.</li>
</ol>
<p>-------- The exception is as follows: -------</p>
Could not find rake-12.3.0 in any of the sources (Bundler::GemNotFound)
<pre> /opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `map!'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in definition_method'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `<top (required)>'
/opt/bitnami/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `require'
/opt/bitnami/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
/opt/bitnami/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/lib/phusion_passenger/loader_shared_helpers.rb:278:in `block in run_load_path_setup_code'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/lib/phusion_passenger/loader_shared_helpers.rb:381:in `running_bundler'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/lib/phusion_passenger/loader_shared_helpers.rb:276:in `run_load_path_setup_code'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/helper-scripts/rack-preloader.rb:99:in `preload_app'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/helper-scripts/rack-preloader.rb:157:in `<module:App>'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/helper-scripts/rack-preloader.rb:29:in `<module:PhusionPassenger>'
/opt/bitnami/ruby/lib/ruby/gems/2.1.0/gems/passenger-5.0.6/helper-scripts/rack-preloader.rb:28:in `<main>'</pre>
[ 2018-03-15 15:35:29.9342 28957/7f4ceaeef700 age/Hel/Req/CheckoutSession.cpp:252 ]: [Client 1-2] Cannot checkout session because a spawning error occurred. The identifier of the error is 16a39427. Please see earlier logs for details about the error.
Did you load the Bitnami environment before running the "bundle" commands? There's a script at /opt/bitnami/ called "use_redmine". Please run it before running the commands.
For instance:
/opt/bitnami/use_redmine
cd /opt/bitnami/apps/redmine/htdocs/
bundle ...
Note: if you installed the Redmine Stack as superuser "root" on your Ubuntu, you need to load the environment using sudo /opt/bitnami/use_redmine
i took a cookbook from github and am running chef-client. it gives me the error recipe not found but if i run other recipes from that cookbook its runs fine
root#vagrant-ubuntu-trusty-64:~# chef-client
Starting Chef Client, version 12.16.42
resolving cookbooks for run list: ["task_postgis::postgre_extension"]
Synchronizing Cookbooks:
- task_postgis (0.1.0)
- database (6.1.1)
- postgresql (5.1.0)
- apt (5.0.0)
- compat_resource (12.16.2)
- build-essential (7.0.2)
- seven_zip (2.0.2)
- windows (2.1.1)
- ohai (4.2.2)
- mingw (1.2.4)
- openssl (6.0.0)
Installing Cookbook Gems:
Compiling Cookbooks...
[2016-12-05T10:04:51+00:00] WARN: Chef::Provider::AptRepository already exists! Cannot create deprecation class for LWRP provider apt_repository from cookbook apt
[2016-12-05T10:04:52+00:00] WARN: AptRepository already exists! Deprecation class overwrites Custom resource apt_repository from cookbook apt
================================================================================
Recipe Compile Error
Chef::Exceptions::RecipeNotFound
could not find recipe setup_extensions for cookbook postgresql
Cookbook Trace:
/var/chef/cache/cookbooks/task_postgis/recipes/postgre_extension.rb:1:in `from_file'
Relevant File Content:
/var/chef/cache/cookbooks/task_postgis/recipes/postgre_extension.rb:
1>> include_recipe 'postgresql::setup_extensions'
2: # install extensions to database
3: postgresql_extension "postgis" do
4: database "mydb"
5: end
6:
7: #postgresql_language "plpgsql" do
8: # database "mydb"
9: #end
10:
Platform:
x86_64-linux
Running handlers:
[2016-12-05T10:04:52+00:00] ERROR: Running exception handlers
Running handlers complete
[2016-12-05T10:04:52+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 14 seconds
[2016-12-05T10:04:53+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-12-05T10:04:53+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-12-05T10:04:53+00:00] ERROR: could not find recipe setup_extensions for cookbook postgresql
[2016-12-05T10:04:53+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
There is no setup_extensions recipe in community postgresql cookbook. I'm not sure if there ever was such recipe. Where did you get this snippet?
Upgrading to capistrano 3, the following no longer seems to work:
namespace :project do
desc "Prevents executing by creating lockfile"
task :disable do
on roles(:app) do
execute "touch /tmp/proj_lockfile"
end
on_rollback do
execute "rm /tmp/proj_lockfile"
end
end
end
...
NoMethodError: undefined method `on_rollback' for main:Object
config/deploy.rb:34:in `block (2 levels) in <top (required)>'
Tasks: TOP => deploy:starting => transformer:disable
(See full trace by running task with --trace)
Is there a new task etc to do this?
There is no Capistrano 3 equivalent of on_rollback.
In Capistrano 3, if any command fails, the deployment stops, and the release that was being deployed is left in place (possibly working and deployed, possibly not working and deployed, or not deployed - Capistrano no longer attempts to clean up at all).
Note that this also means that :on_error => :continue is unsupported with no replacement; you have to begin/rescue any exceptions yourself.
The rollbacks section of the documentation is completely empty.
Take a look at the "Rollback flow" documentation: http://capistranorb.com/documentation/getting-started/flow/
deploy:starting
deploy:started
deploy:reverting - revert server(s) to previous release
deploy:reverted - reverted hook
deploy:publishing
deploy:published
deploy:finishing_rollback - finish the rollback, clean up everything
deploy:finished
I'm having issues installing mongodb version 2.4.6 on an Amazon EC2 Linux with chef.
I'm using the popular mongodb chef cookbook
I've taken measures to ensure that my runlist specifies recipe[mongodb::10gen_repo] before recipe[mongodb::default].
I am getting the following error though:
Recipe: mongodb::10gen_repo
* yum_repository[10gen] action addRecipe: <Dynamically Defined Resource>
* template[/etc/yum.repos.d/10gen.repo] action create (up to date)
* execute[yum-makecache-10gen] action nothing (skipped due to action :nothing)
* ruby_block[yum-cache-reload-10gen] action nothing (skipped due to action :nothing)
(up to date)
Recipe: mongodb::default
* package[mongo-10gen-server] action install
================================================================================
Error executing action `install` on resource 'package[mongo-10gen-server]'
================================================================================
Chef::Exceptions::Exec
----------------------
returned 1, expected 0
Resource Declaration:
---------------------
# In /var/chef/cache/cookbooks/mongodb/recipes/default.rb
22: package node[:mongodb][:package_name] do
23: action :install
24: version node[:mongodb][:package_version]
25: end
26:
Compiled Resource:
------------------
# Declared in /var/chef/cache/cookbooks/mongodb/recipes/default.rb:22:in `from_file'
package("mongo-10gen-server") do
action [:install]
retries 0
retry_delay 2
package_name "mongo-10gen-server"
version "2.4.6-mongodb_1"
cookbook_name "mongodb"
recipe_name "default"
end
[2013-12-26T09:22:05+00:00] ERROR: Running exception handlers
[2013-12-26T09:22:05+00:00] ERROR: Exception handlers complete
[2013-12-26T09:22:05+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
Chef Client failed. 5 resources updated
[2013-12-26T09:22:05+00:00] ERROR: package[mongo-10gen-server] (mongodb::default line 22) had an error: Chef::Exceptions::Exec: returned 1, expected 0
[2013-12-26T09:22:05+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Where have you defined node[:mongodb][:package_name]?
In order to use that cookbook, I believe you need to set that attribute.
Using the Android 2.2, API-8, SDK-r7 along with CTS-2.2_r4 suite.
Updated the SDK_ROOT environment variable with SDK_r7 tools in “android-cts/tools/startcts” script and the “SDK_ROOT/tools” also included in PATH environment variable.
Ran the “android” and created a new virtual device and started the same. This invokes the emulator named as “emulator-5554”.
Now, started the cts using the below command:
bash android-cts/tools/startcts.
start –plan android
Above command failed with:
Test package: android.app
install met failure [install_failed_insufficient_storage]
CTS_ERROR >>> Failed to execute shell command am instrument -w -r -e package android com.android.cts.app/android.test.InstrumentationCtsTestRunner on device emulator-5554
com.android.ddmlib.ShellCommandUnresponsiveException.
A few more issues are:
CTS_ERROR >>> Got exception while processing command
CTS_ERROR >>> Installing met timeout due to Unknown reason
CTS_ERROR >>> Timeout: ReferenceAppTest
CTS_ERROR >>> Timeout: getDeviceInfo
Any hint to avoid the above timeout issues? Thank you very much for anticipating a quick response from you.
I did not got this error on the CTS 2.1 r5. But I am not running the SDK test that Android but my own tests instead. There for I will use the CTS 2.1 for a while.