No such file or directory - passenger-5.0.0.beta1/buildout/support-binaries/PassengerAgent #1304

Closed
jcoglan opened this Issue Nov 25, 2014 · 7 comments

Comments

Projects
None yet
3 participants
@jcoglan

jcoglan commented Nov 25, 2014

I'm running the server and client from faye-websocket:

$ git clone git://github.com/faye/faye-websocket-ruby.git
$ cd faye-websocket-ruby
$ vim faye-websocket-ruby.gemspec # set passenger dependency to 5.0.0.beta1
$ bundle install
$ cd examples
$ bundle exec passenger start -p 9001

Then run the client:

$ ruby autobahn_client.rb

The server prints this error:

$ bundle exec passenger start -p 9001
...
App 13918 stderr: /home/jcoglan/projects/.faye/websocket/ruby/.bundle/ruby/2.0.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/system_metrics_command.rb:32:in `exec': No such file or directory - /home/jcoglan/projects/.faye/websocket/ruby/.bundle/ruby/2.0.0/gems/passenger-5.0.0.beta1/buildout/support-binaries/PassengerAgent (Errno::ENOENT)
App 13918 stderr:   from /home/jcoglan/projects/.faye/websocket/ruby/.bundle/ruby/2.0.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/system_metrics_command.rb:32:in `run'
App 13918 stderr:   from /home/jcoglan/projects/.faye/websocket/ruby/.bundle/ruby/2.0.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/main.rb:75:in `run!'
App 13918 stderr:   from /home/jcoglan/projects/.faye/websocket/ruby/.bundle/ruby/2.0.0/gems/passenger-5.0.0.beta1/bin/passenger-config:37:in `<main>'

This routine works correctly when using Passenger 4.

@FooBarWidget

This comment has been minimized.

Show comment
Hide comment
@FooBarWidget

FooBarWidget Nov 25, 2014

Member

But does the server still work correctly? Did Passenger exit after printing this error? Are there any other errors?

Member

FooBarWidget commented Nov 25, 2014

But does the server still work correctly? Did Passenger exit after printing this error? Are there any other errors?

@jcoglan

This comment has been minimized.

Show comment
Hide comment
@jcoglan

jcoglan Nov 25, 2014

No, the WebSocket connection fails.

jcoglan commented Nov 25, 2014

No, the WebSocket connection fails.

@FooBarWidget

This comment has been minimized.

Show comment
Hide comment
@FooBarWidget

FooBarWidget Nov 25, 2014

Member

No, I mean, do normal HTTP requests work? What happens if you run curl on the front page?

Member

FooBarWidget commented Nov 25, 2014

No, I mean, do normal HTTP requests work? What happens if you run curl on the front page?

@matthooks

This comment has been minimized.

Show comment
Hide comment
@matthooks

matthooks Nov 25, 2014

I'm also seeing this error on Heroku on the first request to (some) freshly started dynos. Requests are definitely going through, though.

2014-11-25T23:03:07.502800+00:00 app[web.1]: App 92 stderr: /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/system_metrics_command.rb:32:in `exec'
2014-11-25T23:03:07.502863+00:00 app[web.1]: App 92 stderr: : 
2014-11-25T23:03:07.502943+00:00 app[web.1]: App 92 stderr: No such file or directory - /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/buildout/support-binaries/PassengerAgent
2014-11-25T23:03:07.503016+00:00 app[web.1]: App 92 stderr:  (
2014-11-25T23:03:07.503090+00:00 app[web.1]: App 92 stderr: Errno::ENOENT
2014-11-25T23:03:07.503159+00:00 app[web.1]: App 92 stderr: )
2014-11-25T23:03:07.503238+00:00 app[web.1]: App 92 stderr:     from /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/system_metrics_command.rb:32:in `run'
2014-11-25T23:03:07.503342+00:00 app[web.1]: App 92 stderr:     from /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/main.rb:75:in `run!'
2014-11-25T23:03:07.503417+00:00 app[web.1]: App 92 stderr:     from /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/bin/passenger-config:37:in `<main>'

I'm also seeing this error on Heroku on the first request to (some) freshly started dynos. Requests are definitely going through, though.

2014-11-25T23:03:07.502800+00:00 app[web.1]: App 92 stderr: /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/system_metrics_command.rb:32:in `exec'
2014-11-25T23:03:07.502863+00:00 app[web.1]: App 92 stderr: : 
2014-11-25T23:03:07.502943+00:00 app[web.1]: App 92 stderr: No such file or directory - /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/buildout/support-binaries/PassengerAgent
2014-11-25T23:03:07.503016+00:00 app[web.1]: App 92 stderr:  (
2014-11-25T23:03:07.503090+00:00 app[web.1]: App 92 stderr: Errno::ENOENT
2014-11-25T23:03:07.503159+00:00 app[web.1]: App 92 stderr: )
2014-11-25T23:03:07.503238+00:00 app[web.1]: App 92 stderr:     from /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/system_metrics_command.rb:32:in `run'
2014-11-25T23:03:07.503342+00:00 app[web.1]: App 92 stderr:     from /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/lib/phusion_passenger/config/main.rb:75:in `run!'
2014-11-25T23:03:07.503417+00:00 app[web.1]: App 92 stderr:     from /app/vendor/bundle/ruby/2.1.0/gems/passenger-5.0.0.beta1/bin/passenger-config:37:in `<main>'

@jcoglan

This comment has been minimized.

Show comment
Hide comment
@jcoglan

jcoglan Nov 26, 2014

Oh, I see. Yes, the app seems to be handling requests, despite that error. It turns out that WebSocket is not working because Passenger is not passing the HTTP_CONNECTION header to the application.

jcoglan commented Nov 26, 2014

Oh, I see. Yes, the app seems to be handling requests, despite that error. It turns out that WebSocket is not working because Passenger is not passing the HTTP_CONNECTION header to the application.

@FooBarWidget

This comment has been minimized.

Show comment
Hide comment
@FooBarWidget

FooBarWidget Nov 26, 2014

Member

There are two separate issues here. The "No such file or directory" error is a non-fatal cosmetic bug, and it is a totally different bug from the WebSocket one. I'll have a look at both.

Member

FooBarWidget commented Nov 26, 2014

There are two separate issues here. The "No such file or directory" error is a non-fatal cosmetic bug, and it is a totally different bug from the WebSocket one. I'll have a look at both.

@FooBarWidget

This comment has been minimized.

Show comment
Hide comment
@FooBarWidget

FooBarWidget Nov 26, 2014

Member

I've split the WebSocket issue into #1306.

Member

FooBarWidget commented Nov 26, 2014

I've split the WebSocket issue into #1306.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment