Error: "Protocol not available"

[Kixunil]

When trying to run the server:

let core = tokio_core::reactor::Core::new().unwrap();

// I tried both "127.0.0.1:8331", "0.0.0.0:8331" and even "[::1]:8331", also other ports
let addr = std::net::SocketAddr::new(config.bind_address, config.bind_port);
// ProxyHandle implements Service
let service = ProxyHandle(Rc::new(Proxy { config, client: HttpClient::new(&core.handle()), }));

let server = hyper::server::Http::new().bind(&addr, move || Ok(service.clone())).unwrap();
server.run().unwrap();

It panics with OS error "Protocol not available"

nc -l works, so I guess the problem is somewhere in hyper or its dependency.

[seanmonstar]

Oh noes! What version of hyper are you using?

And when you say it panics, where? At one of the unwraps you have, or inside hyper?

[Kixunil]

The last one - 0.11.26

It panics on my unwrap - the one at the end of line: let server = hyper::server::Http::new().bind(&addr, move || Ok(service.clone())).unwrap();

[Kixunil]

FYI, I just rewrote the code to use tokio_core::net::TcpListener::bind(&addr, &handle).unwrap(); and hyper::server::Http::new().serve_incoming(listener.incoming().map(|(socket, _addr)| socket), move || Ok(service.clone())); and it works.

[sfackler]

I've seen the "protocol unavailable" message once before myself but I can't remember what the context was unfortunately.

[seanmonstar]

What OS is this happening on?

[Kixunil]

Linux Mint

[seanmonstar]

Do you what version of the Linux kernel it is? 0.11.26 tries to set SO_REUSEPORT and SO_REUSEADDR, so that the newer run_threads can work. Looks like SO_REUSEPORT is only in Linux >=3.9?

[asonix]

mint should definitely be at least 3.9, unless that's a really old install.

I was on 3.12 in 2013 on elementary OS (another ubuntu derivative)

[Kixunil]

3.2.0-48-generic

(Yes, it is old install.)

[seanmonstar]

So, I think 2c48101 will fix this, if you want to try it out before I just publish a new version assuming it fixes it :)

[Kixunil]

I plan to try it. Thank you for quick response!

[seanmonstar]

I've published v0.11.27 with the fix mentioned here!