when i try to create conjure account using the command( I am following conjur quickstart tutorial)
docker-compose exec conjur conjurctl account create myConjurAccount > admin_data
i am getting Cipher error in admin_data file,
when i cat admin_data file
rake aborted!
OpenSSL::Cipher::CipherError:
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/symmetric.rb:37:in`final'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/symmetric.rb:37:in `decrypt'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/attr_encrypted.rb:60:in `decrypt'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/attr_encrypted.rb:40:in `block (3 levels) in attr_encrypted'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/adapters/sequel_adapter.rb:32:in `get_key'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/keystore.rb:18:in `get'
/var/lib/gems/2.5.0/gems/slosilo-2.1.1/lib/slosilo/keystore.rb:47:in `[]'
/opt/conjur-server/app/models/account.rb:6:in `find_or_create_accounts_resource'
/opt/conjur-server/lib/tasks/account.rake:15:in `block (2 levels) in <top (required)>'
/var/lib/gems/2.5.0/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'
Tasks: TOP => account:create
(See full trace by running task with --trace)
But sometimes its creating i am not understanding what makes it working in the background. Any help will be appreciated.
and also docker-compose ps showing
bot_app tail -F anything Up
conjur_client sleep infinity Up
conjur_server conjurctl server Up 80/tcp
nginx_proxy nginx -g daemon off; Up 0.0.0.0:8443->443/tcp, 80/tcp
postgres_database docker-entrypoint.sh postgres Up 5432/tcp
openssl openssl req -newkey rsa:20 ... Exit 0
Everytime openssl exiting with 0
I have fixed this issue by removing all stopped containers before running the conjure docker container using docker container prune.
Related
In my docker container, running asciidoctor -r asciidoctor-plantuml my_doc.adoc gets me asciidoctor: FAILED: 'asciidoctor-plantuml' could not be loaded.
To reproduce the issue:
$ docker run -it -v $WHERE_ADOCS:/documents/ asciidoctor/docker-asciidoctor
77687352778d:/documents# asciidoctor -r asciidoctor-plantuml --trace my_doc.adoc
from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:281:in `block in parse!'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:279:in `each'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:279:in `parse!'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/options.rb:34:in `parse!'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/lib/asciidoctor/cli/invoker.rb:24:in `initialize'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/bin/asciidoctor:13:in `new'
from /usr/lib/ruby/gems/3.1.0/gems/asciidoctor-2.0.18/bin/asciidoctor:13:in `<top (required)>'
from /usr/bin/asciidoctor:25:in `load'
from /usr/bin/asciidoctor:25:in `<main>'```
with the result like above. I've been following this README of plantuml extention for asciidoctor.
Do I need to start the plantuml-server for generating the .html?
11:34 $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
plantuml/plantuml-server jetty 92b40d953f4e 3 weeks ago 410MB
asciidoctor/docker-asciidoctor latest dc8b75bfd089 4 weeks ago 685MB
so both images exists in my local. Is there anything I miss?
Any hint is appreciated....
Instead of using asciidoctor-plantuml, asciidoctor-diagram works flawless:
77687352778d:/documents# asciidoctor -r asciidoctor-diagram my_doc.adoc
with the expected my_doc.html with the embedded plantuml being generated.
<returncode>FAILED</returncode>
<messageKey>unsupportedRequest</messageKey>
<message>This request is not supported.</message>
</response>```
This is the response from the scalelite server when i enter the URL on browser.
I am getting this message when i try to run
```docker exec -i scalelite-api bundle exec rake db:setup```
ActiveRecord::ProtectedEnvironmentError: You are attempting to run a destructive action against your 'production' database.
If you are sure you want to continue, run the same command with the environment variable:
DISABLE_DATABASE_ENVIRONMENT_CHECK=1
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.6/lib/active_record/tasks/database_tasks.rb:63:in `check_protected_environments!'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.6/lib/active_record/railties/databases.rake:15:in `block (2 levels) in <main>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.6/lib/active_record/railties/databases.rake:404:in `block (3 levels) in <main>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.3/exe/rake:27:in `<top (required)>'
/usr/bin/bundle:23:in `load'
/usr/bin/bundle:23:in `<main>'
Tasks: TOP => db:schema:load => db:check_protected_environments
(See full trace by running task with --trace)
This is what i get when i enter the command
docker exec -i scalelite-api bundle exec rake status
domain.com enabled online 0 0 0 0
domain.com enabled online 0 0 0 0
Experts please help me with this. I am new to this
I am trying the balance the load between 2 servers.
That's OK. You should check it with https://your.scalelite.com/bigbluebutton/api/ not https://your.scalelite.com.
Starting the Ruby thin client works fine in command line:
RAILS_ENV=production bundle exec thin --ssl-disable-verify -C services/private_pub/private_pub_thin.yml start
But starting it as deamon returns a Bad File Descriptor:
user#app:~/app$ RAILS_ENV=production bundle exec thin -d --ssl-disable-verify -C services/private_pub/private_pub_thin.yml start
user#app:~/app$ /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:149:in ``': Bad file descriptor (Errno::EBADF)
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:149:in `block in git'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/shared_helpers.rb:72:in `call'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/shared_helpers.rb:72:in `with_clean_git_env'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:149:in `git'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/source/git/git_proxy.rb:83:in `version'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/env.rb:78:in `git_version'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/env.rb:22:in `report'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:74:in `request_issue_report_for'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:40:in `log_error'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:100:in `rescue in with_friendly_errors'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
from /opt/rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
from /opt/rbenv/versions/2.2.1/bin/bundle:23:in `load'
from /opt/rbenv/versions/2.2.1/bin/bundle:23:in `<main>'
Any idea? This happened without any code change. There is also nothing already running.
I am trying to run a Ruby on Rails app with nginx and unicorn. After setting up the unicorn configuration file 'unicorn.rb' when I try and execute this command
bundle exec unicorn -c config/unicorn.rb -D
It throws the following error:
/home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/lib/unicorn/configurator.rb:537:in `working_directory': config_file=config/unicorn.rb would not be accessible in working_directory=/home/vagrant/home (ArgumentError)
from config/unicorn.rb:3:in `reload'
from /home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/lib/unicorn/configurator.rb:72:in `instance_eval'
from /home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/lib/unicorn/configurator.rb:72:in `reload'
from /home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/lib/unicorn/configurator.rb:65:in `initialize'
from /home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/lib/unicorn/http_server.rb:76:in `new'
from /home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/lib/unicorn/http_server.rb:76:in `initialize'
from /home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/bin/unicorn:126:in `new'
from /home/vagrant/.rvm/gems/ruby-2.2.1/gems/unicorn-5.0.0/bin/unicorn:126:in `<top (required)>'
from /home/vagrant/.rvm/gems/ruby-2.2.1/bin/unicorn:23:in `load'
from /home/vagrant/.rvm/gems/ruby-2.2.1/bin/unicorn:23:in `<main>'
from /home/vagrant/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
from /home/vagrant/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'
master failed to start, check stderr log for details
I am running inside an ubuntu-vagrant setup and my app is in the following directory:
/home/vagrant/home/my-app
And the configuration file(unicorn.rb) is in the following directory:
/home/vagrant/home/my-app/config
And the file(unicorn.rb) contains the following configurations:
working_directory "/home/vagrant/home/"
pid "/home/vagrant/home/temp/pids/unicorn.pid"
stderr_path "/home/vagrant/home/log/unicorn.log"
stdout_path "/home/vagrant/home/log/unicorn.log"
listen "/tmp/unicorn.expertiza.sock"
worker_processes 2
timeout 30
I dont understand where I am going wrong. Even the error statement doesnt make much sense. Can someone provide some assistance.
I am attempting to deploy my Rails 4 app to Heroku, and when I enter:
git push heroku master
I get the following error:
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
rake aborted!
could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
From the Rails Asset Pipeline on Heroku Cedar:
This means that your app is attempting to connect to the database as part of rake assets:precompile. Because the config vars are not present in the environment and this is the mechanism the Heroku uses to configure your database connection, the command is failing.
The page suggests that I run
env -i GEM_PATH=$GEM_PATH \
PATH=$PATH \
DATABASE_URL=postgres://user:pass#127.0.0.1/dbname \
/bin/sh -c 'bundle exec rake --trace assets:precompile'
When I do, I get the following error:
rake aborted!
couldn't find HOME environment -- expanding ~'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/guardfile/generator.rb:20:inexpand_path'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/guardfile/generator.rb:20:in <class:Generator>'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/guardfile/generator.rb:9:in'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/guardfile/generator.rb:2:in <module:Guard>'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/guardfile/generator.rb:1:in'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/guardfile.rb:2:in require'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/guardfile.rb:2:in'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/dsl.rb:1:in require'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard/dsl.rb:1:in'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard.rb:6:in require'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-2.2.4/lib/guard.rb:6:in'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-rspec-4.2.0/lib/guard/rspec.rb:1:in require'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/guard-rspec-4.2.0/lib/guard/rspec.rb:1:in'
/usr/local/rvm/gems/ruby-2.0.0-p247#global/gems/bundler-1.3.5/lib/bundler/runtime.rb:81:in require'
/usr/local/rvm/gems/ruby-2.0.0-p247#global/gems/bundler-1.3.5/lib/bundler/runtime.rb:81:inrescue in block in require'
/usr/local/rvm/gems/ruby-2.0.0-p247#global/gems/bundler-1.3.5/lib/bundler/runtime.rb:66:in block in require'
/usr/local/rvm/gems/ruby-2.0.0-p247#global/gems/bundler-1.3.5/lib/bundler/runtime.rb:59:ineach'
/usr/local/rvm/gems/ruby-2.0.0-p247#global/gems/bundler-1.3.5/lib/bundler/runtime.rb:59:in require'
/usr/local/rvm/gems/ruby-2.0.0-p247#global/gems/bundler-1.3.5/lib/bundler.rb:132:inrequire'
/Users/dmanaster1/flatiron_school/SourceQ-An/config/application.rb:5:in <top (required)>'
/Users/dmanaster1/flatiron_school/SourceQ-An/Rakefile:5:inrequire'
/Users/dmanaster1/flatiron_school/SourceQ-An/Rakefile:5:in <top (required)>'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/rake_module.rb:25:inload'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/rake_module.rb:25:in load_rakefile'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:637:inraw_load_rakefile'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:94:in block in load_rakefile'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:165:instandard_exception_handling'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:93:in load_rakefile'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:77:inblock in run'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:165:in standard_exception_handling'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/lib/rake/application.rb:75:inrun'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/gems/rake-10.1.0/bin/rake:33:in <top (required)>'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/bin/rake:23:inload'
/Users/dmanaster1/flatiron_school/SourceQ-An/vendor/cache/ruby/2.0.0/bin/rake:23:in `'
What is generating this error? How can I fix it?
I am unfamiliar with user-env-compile, but just set the Devise key as described here:
heroku config:set DEVISE_SECRET_KEY=whatever_the_key_is
Make sure your initializer then uses the key like this:
config.secret_key = ENV['DEVISE_SECRET_KEY']
Then disable user-env-compile like so:
heroku labs:disable user-env-compile -a myapp
And then try to deploy.