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
DNS network syscalls failing when falling back to secondary nameservers #73
Comments
Could you show me output of
Do you any "Invalid argument" errors if you connect to a non-wss websocket?
FWIW it works fine for me locally
I notice luarocks will do that if a 'http' module already exists (e.g. if you've installed via apt/dpkg). @hisham ping? |
Here, keep in mind that's right after renaming its folder to http (in order to get round the naming issue already stated). Plus, naming being an issue proves it being the copy in use. When connecting to
It works fine for me locally too, perhaps it's an isolated issue having to do with that Debian VM? |
That's good to know: the issue isn't in TLS negotiation. Could you run it again with the environmental variable SOCKET_DEBUG=1 set?
Perhaps, I'm wondering if maybe something weird going on with dns there? |
Getting the following, before
|
interesting.... Can you run under |
Added it to the same gist. Reading through, looks like some files aren't found. |
The error is coming from here.
Looking up higher, I see that the same fd was previously used for another request:
I wonder if your OS doesn't like @wahern ping |
|
Oh, I just noticed the
Which is an instance of wahern/cqueues#167. |
as far as I can tell, this a bug in cqueue's behaviour (or infact, dns.c) and should be followed up there. I think this is due to your /etc/resolv.conf containing a local resolver (e.g. 127.0.0.1) followed by another (working) server, and that your local dns resolver is not running. |
Closing as bug has been reported to cqueues/dns.c |
After a fresh Lua and luarocks installation this error occurs. Probably has to do with cqueues but posting here just in case.
EDIT: Seems to work fine on Ubuntu, this error is proven to fire on Debian.
Also, after installing using luarocks, the module is eventually named after http_0_1_0-http and not http as expected.
The text was updated successfully, but these errors were encountered: