Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Occasional errors when using livereload flag #6899

Closed
bdielman opened this issue Apr 4, 2018 · 7 comments

Comments

@bdielman
Copy link

commented Apr 4, 2018

  • I believe this to be a bug, not a question about using Jekyll.
  • I updated to the latest Jekyll (or) if on GitHub Pages to the latest github-pages
  • I ran jekyll doctor to check my configuration
  • I am on (or have tested on) macOS 10+
  • I was trying to build.

My Reproduction Steps

  • Upgrade to Jekyll 3.7.3
  • Make necessary changes to _config.yml
  • Run bundle exec jekyll serve --livereload

Note: Using rbenv to manage Ruby versions, this repo is on 2.4.1

The Output I Wanted

Expecting to see this when I make changes to the source files:

Regenerating: 1 file(s) changed at 2018-04-03 21:56:36

The Output I'm Seeing

I do see the above, but regularly get the following errors upon saving files:

ERROR Errno::EPROTOTYPE: Protocol wrong type for socket
ERROR Errno::ECONNRESET: Connection reset by peer @ io_fillbuf - fd:18

@ashmaroli

This comment has been minimized.

Copy link
Member

commented Apr 4, 2018

@bdielman Hi can you run the server with the --trace switch and post the resulting output so that we can get some insight into where the exception could be originating from..?
Thanks.

@bdielman

This comment has been minimized.

Copy link
Author

commented Apr 4, 2018

Only seeing this in the output:

ERROR Errno::ECONNRESET: Connection reset by peer @ io_fillbuf - fd:17 
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpserver.rb:82:in `eof?'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpserver.rb:82:in `run'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/server.rb:290:in `block in start_thread'
@bdielman

This comment has been minimized.

Copy link
Author

commented Apr 4, 2018

For the other error:

ERROR Errno::EPROTOTYPE: Protocol wrong type for socket
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpresponse.rb:465:in `write'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpresponse.rb:465:in `<<'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpresponse.rb:465:in `_write_data'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpresponse.rb:458:in `_send_file'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpresponse.rb:413:in `send_body_io'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpresponse.rb:305:in `send_body'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpresponse.rb:209:in `send_response'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/httpserver.rb:112:in `run'
	/.rbenv/versions/2.4.1/lib/ruby/2.4.0/webrick/server.rb:290:in `block in start_thread'
@ashmaroli

This comment has been minimized.

Copy link
Member

commented Apr 4, 2018

I've not encountered these exceptions at my end (yet) and your backtrace doesn't seem to lead to any of the classes / files in Jekyll.., so not sure what and how to fix..

/cc @awood Would be great if you could throw some light on this.. Thanks.

@awood

This comment has been minimized.

Copy link
Contributor

commented Apr 4, 2018

Whoa. I don't know what's going on here.
@bdielman:

  • does everything work normally without --livereload? I'm guessing yes, but I just want to verify.
  • does Jekyll actually work at all with --livereload? From your description it sounds like it does work but prints out those error messages over and over.

I think the issue might be a WEBrick bug since it looks like rails hit the same issue. That being said, a little bit of searching hasn't yielded many other mentions of either the "connection reset" or the "wrong type for socket" issues, so maybe it's an error in how WEBrick is being used.

@bdielman

This comment has been minimized.

Copy link
Author

commented Apr 5, 2018

@ashmaroli @awood - Thanks for looking into this!

@bdielman

This comment has been minimized.

Copy link
Author

commented Apr 20, 2018

Upgrading Ruby to 2.5.1 seems to have fixed the problem so I'm closing the issue.

@bdielman bdielman closed this Apr 20, 2018
@jekyll jekyll locked and limited conversation to collaborators Jul 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants
You can’t perform that action at this time.