I am attempting to use the deck.js backend with asciidoctor. I followed the instructions at http://asciidoctor.org/docs/install-and-use-deckjs-backend/. I get the following error:
$ asciidoctor --trace -T asciidoctor-backends/haml deckjs-example.asciidoc
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- asciidoctor/stylesheets (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /home/worldwidewilly/Dropbox/presentations/adoc-deck/asciidoctor-backends/haml/deckjs/helpers.rb:1:in `<top (required)>'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/renderer.rb:121:in `block in initialize'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/renderer.rb:69:in `each'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/renderer.rb:69:in `initialize'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/document.rb:743:in `new'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/document.rb:743:in `renderer'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/document.rb:752:in `render'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor.rb:915:in `render'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/cli/invoker.rb:86:in `block in invoke!'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/cli/invoker.rb:79:in `each'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/lib/asciidoctor/cli/invoker.rb:79:in `invoke!'
from /var/lib/gems/1.9.1/gems/asciidoctor-0.1.4/bin/asciidoctor:13:in `<top (required)>'
from /usr/local/bin/asciidoctor:23:in `load'
from /usr/local/bin/asciidoctor:23:in `<main>'
My document - deckjs-example - looks like:
= Asciidoctor Deckjs Example
Bill Turner
:backend: deckjs
:deckjs_theme: web-2.0
:deckjs_transition: horizontal-slide
:navigation:
:blank:
:goto:
:menu:
:status:
:split:
:toc:
== Title of Slide One
Hello World!
[canvas-image="images/groovy.jpg"]
== Slide Two's Title will not be displayed
[role="canvas-caption", position="center-up"]
This text is displayed on top of the example.jpg image.
My directory contains all the things that I seem to need to have installed:
$ ls
total 32K
22021551 drwxr-xr-x 7 worldwidewilly worldwidewilly 4.0K Apr 27 13:38 asciidoctor-backends
24910534 drwxr-xr-x 8 worldwidewilly worldwidewilly 4.0K Apr 21 20:30 deck.js
527971 -rw-r--r-- 1 worldwidewilly worldwidewilly 394 Apr 27 14:01 deckjs-example.asciidoc
26740079 drwxr-xr-x 2 worldwidewilly worldwidewilly 4.0K Apr 27 14:00 images
I presume a configuration problem. Searching has yet to reveal a solution, though I did find a similar problem on the AsciiDoctor discussion group which, unfortunately, did not seem to provide a solution, at least not one I understood.
I am running on Linux Mint 17. It turns out that the asciidoctor package available in the package manager was hopelessly out of date. Note the version used above: asciidoctor-0.1.4. When I updated to the latest version, 1.5.2, all worked fine.
Related
Can't start Puma for some reason. Getting this error
ArgumentError: couldn't find login name -- expanding `~'
With the below back trace
Feb 03 15:44:21 shopify-shipping-refactor puma[3061]: Done in 1.33s.
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: rake aborted!
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: ArgumentError: couldn't find login name -- expanding `~'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/pry-0.12.2/lib/pry/pry_class.rb:5:in `expand_path'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/pry-0.12.2/lib/pry/pry_class.rb:5:in `<class:Pry>'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/pry-0.12.2/lib/pry/pry_class.rb:1:in `<top (required)>'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/pry-0.12.2/lib/pry.rb:119:in `require'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/pry-0.12.2/lib/pry.rb:119:in `<top (required)>'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/bundler-2.1.4/lib/bundler/runtime.rb:74:in `require'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/bundler-2.1.4/lib/bundler/runtime.rb:74:in `block (2 levels) in require'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/bundler-2.1.4/lib/bundler/runtime.rb:69:in `each'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/bundler-2.1.4/lib/bundler/runtime.rb:69:in `block in require'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/bundler-2.1.4/lib/bundler/runtime.rb:58:in `each'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/bundler-2.1.4/lib/bundler/runtime.rb:58:in `require'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/bundler-2.1.4/lib/bundler.rb:174:in `require'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /opt/shopify_shipping_refactor/config/application.rb:7:in `<top (required)>'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /opt/shopify_shipping_refactor/Rakefile:4:in `require'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /opt/shopify_shipping_refactor/Rakefile:4:in `<top (required)>'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `eval'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: /usr/local/rvm/gems/ruby-2.6.5/bin/ruby_executable_hooks:24:in `<main>'
Feb 03 15:44:25 shopify-shipping-refactor puma[3061]: (See full trace by running task with --trace)
Feb 03 15:44:25 shopify-shipping-refactor systemd[1]: puma.service: Control process exited, code=exited status=1
Feb 03 15:44:25 shopify-shipping-refactor systemd[1]: Failed to start puma.service.
Feb 03 15:44:25 shopify-shipping-refactor systemd[1]: puma.service: Unit entered failed state.
Feb 03 15:44:25 shopify-shipping-refactor systemd[1]: puma.service: Failed with result 'exit-code'.
Analysis: Ruby's expand_path calls into the C-based runtime (obscuring the stack trace), but eventually ends up in rb_default_home_dir to figure out what '~' is. This method relies on the $HOME environment variable to figure this out and falls back to getlogin() (getlogin(3)) and getpwnam() if it's not available.
Cause: The error message you're seeing is from that fallback failing, since (presumably) your process is not registered with a controlling tty and login user.
Solution: Set $HOME when running puma. Use a directory that you want the Puma to use as a home directory when '~' is specified.
I have two ruby code, one is ssh.rb and the other is generate_ip.rb, they are all in the same directory. When I import ssh.rb in generate_ip.rb, I always getting the following error:
Traceback (most recent call last):
5: from generate_ip.rb:1:in `<main>'
4: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
3: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2: from /root/ssh.rb:8:in `<top (required)>'
1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- net/ssh/config (LoadError)
generate_ip.rb↓
require './ssh.rb'
this is my directory structure↓
root#BabyZe:~# ls -l
total 56
drwxr-xr-x 3 root root 4096 Apr 1 20:32 Desktop
drwxr-xr-x 2 root root 4096 Sep 27 2018 Documents
drwxr-xr-x 2 root root 4096 Sep 27 2018 Downloads
-rw-r--r-- 1 root root 32 May 3 07:36 generate_ip.rb
drwxr-xr-x 2 root root 4096 Sep 27 2018 Music
drwxr-xr-x 3 root root 4096 May 3 06:04 Notebooks
drwxr-xr-x 2 root root 4096 Sep 27 2018 Pictures
drwxr-xr-x 2 root root 4096 Sep 27 2018 Public
-rw-r--r-- 1 root root 15595 May 3 06:45 ssh.rb
drwxr-xr-x 2 root root 4096 Sep 27 2018 Templates
drwxr-xr-x 2 root root 4096 Sep 27 2018 Videos
it is a complete code：
root#BabyZe:~# ls -l
total 56
drwxr-xr-x 3 root root 4096 Apr 1 20:32 Desktop
drwxr-xr-x 2 root root 4096 Sep 27 2018 Documents
drwxr-xr-x 2 root root 4096 Sep 27 2018 Downloads
-rw-r--r-- 1 root root 19 May 3 07:48 generate_ip.rb
drwxr-xr-x 2 root root 4096 Sep 27 2018 Music
drwxr-xr-x 3 root root 4096 May 3 06:04 Notebooks
drwxr-xr-x 2 root root 4096 Sep 27 2018 Pictures
drwxr-xr-x 2 root root 4096 Sep 27 2018 Public
-rw-r--r-- 1 root root 15595 May 3 06:45 ssh.rb
drwxr-xr-x 2 root root 4096 Sep 27 2018 Templates
drwxr-xr-x 2 root root 4096 Sep 27 2018 Videos
root#BabyZe:~# cat generate_ip.rb
require './ssh.rb'
root#BabyZe:~# ruby generate_ip.rb
Traceback (most recent call last):
5: from generate_ip.rb:1:in `<main>'
4: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
3: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2: from /root/ssh.rb:8:in `<top (required)>'
1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- net/ssh/config (LoadError)
i try require_relative, it doesn't work -,-
root#BabyZe:~# cat generate_ip.rb
require_relative 'ssh.rb'
root#BabyZe:~# ruby generate_ip.rb
Traceback (most recent call last):
4: from generate_ip.rb:1:in `<main>'
3: from generate_ip.rb:1:in `require_relative'
2: from /root/ssh.rb:8:in `<top (required)>'
1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- net/ssh/config (LoadError)
ssh.rb(same as Net:SSH)↓
# Make sure HOME is set, regardless of OS, so that File.expand_path works
# as expected with tilde characters.
ENV['HOME'] ||= ENV['HOMEPATH'] ? "#{ENV['HOMEDRIVE']}#{ENV['HOMEPATH']}" : Dir.pwd
require 'logger'
require 'etc'
require 'net/ssh/config'
require 'net/ssh/errors'
require 'net/ssh/loggable'
require 'net/ssh/transport/session'
require 'net/ssh/authentication/session'
require 'net/ssh/connection/session'
require 'net/ssh/prompt'
module Net
# Net::SSH is a library for interacting, programmatically, with remote
# processes via the SSH2 protocol. Sessions are always initiated via
# Net::SSH.start. From there, a program interacts with the new SSH session
# via the convenience methods on Net::SSH::Connection::Session, by opening
# and interacting with new channels (Net::SSH::Connection:Session#open_channel
# and Net::SSH::Connection::Channel), or by forwarding local and/or
# remote ports through the connection (Net::SSH::Service::Forward).
...
...
...
No matter what, I am very grateful to all those who can give me advice.
Your problem is not require_relative 'ssh.rb' in generate_ip.rb.
Your problem is in line 8 of ssh.rb
2: from /root/ssh.rb:8:in '<top (required)>'
After the OP edited the question:
As I understand you've used net-ssh gem.
You need to install it
gem install net-ssh
Please, try this:
require './ssh.rb'
Unlike load, require does not have current directory in its load path, so either use require_relative or use the dot to specify current directory
I get the following error in apache log on puppet master:
Any ideas what could be wrong here:
[ E 2018-03-11 07:50:58.9057 10913/T8 age/Cor/Con/CheckoutSession.cpp:285 ]: [Client 1-1] Cannot checkout session because a spawning error occurred. The identifier of the error is cd3585fe. Please see earlier logs for details about the error.
App 10950 stdout:
App 10950 stdout:
[ E 2018-03-11 07:51:03.0922 10913/Te age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /usr/share/puppet/rack/puppetmasterd: An error occurred while starting up the preloader.
Error ID: 01cd04d1
Error details saved to: /tmp/passenger-error-sAcbhg.html
Message from application: cannot load such file -- puppet/util/command_line (LoadError)
/usr/local/rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
config.ru:32:in `block in <main>'
/usr/local/rvm/gems/ruby-2.4.1/gems/rack-2.0.4/lib/rack/builder.rb:55:in `instance_eval'
/usr/local/rvm/gems/ruby-2.4.1/gems/rack-2.0.4/lib/rack/builder.rb:55:in `initialize'
config.ru:1:in `new'
config.ru:1:in `<main>'
/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:110:in `eval'
/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:110:in `preload_app'
/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:156:in `<module:App>'
/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>'
/usr/local/rvm/gems/ruby-2.4.1/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:29:in `<main>'
My config:
Centos 6.5,
Puppet 3.8.7,
Apache/2.2.15,
Phusion Passenger 5.2.1
I have configured gitlab.rb with LDAP, and after failing to sign in, I wanted to test LDAP with:
sudo /opt/gitlab/embedded/bin/bundle exec /opt/gitlab/embedded/bin/rake gitlab:ldap:check RAILS_ENV=production
When I run this I get the following error:
rake aborted!
Errno::ENOENT: No such file or directory - No file specified as Settingslogic source
/opt/gitlab/embedded/service/gitlab-rails/config/initializers/1_settings.rb:173:in `new'
/opt/gitlab/embedded/service/gitlab-rails/config/initializers/1_settings.rb:173:in `block in <top (required)>'
/opt/gitlab/embedded/service/gitlab-rails/config/initializers/1_settings.rb:172:in `each'
/opt/gitlab/embedded/service/gitlab-rails/config/initializers/1_settings.rb:172:in `<top (required)>'
/opt/gitlab/embedded/service/gitlab-rails/config/environment.rb:5:in `<top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
Tasks: TOP => gitlab:check => gitlab:gitlab_shell:check => environment
(See full trace by running task with --trace)
I am new to Gitlab and rake, I tried to search for the problem, but found myself at a dead end.
I don't know what the problem is and am afraid that when I experiment I will break anything else.
Does anyone recognise this problem, can anyone help me find point towards the problem and hopefully a solution?
Much appreciated.
Install directory:
[root#centos7template ~]# ll /var/opt/gitlab
total 8
drwx------ 2 git root 6 Nov 1 08:45 backups
-rw------- 1 root root 38 Nov 1 08:47 bootstrapped
drwx------ 2 git root 24 Nov 3 12:28 gitaly
drwx------ 3 git root 25 Nov 1 08:45 git-data
drwxr-xr-x 3 git root 19 Nov 1 08:45 gitlab-ci
drwxr-xr-x 2 git root 31 Nov 3 10:39 gitlab-monitor
drwxr-xr-x 9 git root 150 Nov 3 10:39 gitlab-rails
drwx------ 2 git root 23 Nov 3 10:39 gitlab-shell
drwxr-x--- 2 git gitlab-www 51 Nov 3 12:29 gitlab-workhorse
drwx------ 3 root root 68 Nov 3 13:39 logrotate
drwxr-x--- 9 root gitlab-www 154 Nov 3 12:29 nginx
drwxr-xr-x 3 root root 31 Nov 1 08:47 node-exporter
drwx------ 2 gitlab-psql root 25 Nov 3 10:39 postgres-exporter
drwxr-xr-x 3 gitlab-psql root 77 Nov 3 12:29 postgresql
drwxr-x--- 3 gitlab-prometheus root 38 Nov 3 10:39 prometheus
drwxr-x--- 2 gitlab-redis git 57 Nov 3 12:29 redis
-rw-r--r-- 1 root root 40 Nov 1 08:45 trusted-certs-directory-hash
Installed versions:
gitaly v0.43.0
gitlab-config-template 10.1.0
gitlab-cookbooks 10.1.0
gitlab-ctl 10.1.0
gitlab-ctl-ee 10.1.0
gitlab-elasticsearch-indexer v0.2.1
gitlab-monitor v1.9.0
gitlab-pages v0.6.0
gitlab-rails v10.1.0-ee
gitlab-scripts 10.1.0
gitlab-selinux 10.1.0
gitlab-shell v5.9.3
gitlab-workhorse v3.2.0
Created new LDAP configuration in gitlab.rb, reconfigured with gitlab-ctl, tried various authentication method, and with simple_tls it worked.
Thanks for all the effort to post comments with questions! Appreciated.
Update I tried catching this exception in my application controller, but to no avail. I've also updated Passenger to 3.0.7 and submitted an issue to their tracker.
I have a Rails 3.0.4 application running on FreeBSD 8.2 with Apache 2.2.17, Passenger 3.0.2 and Ruby 1.9.2-p180 that's been dying every other day. Here's the backtrace from the error log:
[ pid=85853 thr=17189069660 file=utils.rb:176 time=2011-05-04 12:08:13.022 ]:
*** Exception ActionController::UnknownHttpMethod in application
(U<F9>i<CA>,fs<C8>6<F6><C0>b<F2><C5>hVj<BE><D9>#<F5><80><99><EA>=n,
accepted HTTP methods are OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT,
PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, UNLOCK, VERSION-CONTROL, REPORT, CHECKOUT,
CHECKIN, UNCHECKOUT, MKWORKSPACE, UPDATE, LABEL, MERGE, BASELINE-CONTROL, MKACTIVITY,
ORDERPATCH, ACL, SEARCH, and PATCH) (process 85853, thread #<Thread:0x0000080118c6b8>):
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/actionpack-3.0.4/lib/action_dispatch/http/request.rb:76:in `request_method'
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/railties-3.0.4/lib/rails/rack/logger.rb:24:in `before_dispatch'
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/railties-3.0.4/lib/rails/rack/logger.rb:12:in `call'
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/rack-1.2.1/lib/rack/runtime.rb:17:in `call'
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/rack-1.2.1/lib/rack/lock.rb:11:in `block in call'
from <internal:prelude>:10:in `synchronize'
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/rack-1.2.1/lib/rack/lock.rb:11:in `call'
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/railties-3.0.4/lib/rails/application.rb:168:in `call'
from /usr/local/docs/arc/shared/bundle/ruby/1.9.1/gems/railties-3.0.4/lib/rails/application.rb:77:in `method_missing'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/rack/request_handler.rb:96:in `process_request'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_request_handler.rb:513:in `accept_and_process_next_request'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/rack/application_spawner.rb:205:in `start_request_handler'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/rack/application_spawner.rb:170:in `block in handle_spawn_application'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/utils.rb:479:in `safe_fork'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/rack/application_spawner.rb:165:in `handle_spawn_application'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server.rb:180:in `start'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/rack/application_spawner.rb:128:in `start'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/spawn_manager.rb:253:in `block (2 levels) in spawn_rack_application'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/spawn_manager.rb:246:in `block in spawn_rack_application'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server_collection.rb:82:in `block in synchronize'
from <internal:prelude>:10:in `synchronize'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/spawn_manager.rb:244:in `spawn_rack_application'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/spawn_manager.rb:137:in `spawn_application'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/spawn_manager.rb:275:in `handle_spawn_application'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously'
from /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.2/helper-scripts/passenger-spawn-server:99:in `<main>'
[Wed May 04 12:08:13 2011] [notice] child pid 1567 exit signal Bus error (10)
[Wed May 04 12:08:16 2011] [notice] child pid 1195 exit signal Bus error (10)
[Wed May 04 12:08:20 2011] [notice] child pid 1600 exit signal Bus error (10)
[Wed May 04 12:08:20 2011] [notice] child pid 1590 exit signal Bus error (10)
[Wed May 04 12:08:21 2011] [notice] child pid 1199 exit signal Bus error (10)
[Wed May 04 12:08:21 2011] [notice] child pid 726 exit signal Bus error (10)...etc...
Once this happens, the application goes down. Apache still serves up static files in the public directory, but no application. Of course the gobbledygook where the http verb should be concerns me (and makes it impossible to track down via google), but will rescuing this exception in the application_controller actually prevent passenger from dying? Anyone seen this before?
To be perfectly honest, it looks like your application server (fastcgi or apache moduel?) is dieing quite ungracefully when an illegal HTTP verb is received.
I fully expect that you can filter this in the apache config for the site (be it /etc/apache2/site-available/... or .htaccess in your virtual folder (mod_access)
However, I think it is sane to just report the trace to the Passenger devs as a bug. The info is right there in the trace
U<F9>i<CA>,fs<C8>6<F6><C0>b<F2><C5>hVj<BE><D9>#<F5><80><99><EA>=n
is not a valid verb. It could be trivial to reproduce using netcat on port 80 of your webserver (remember the Host header)