Xray not working on OpenBSD 7.5, syscalls show errno 35 Resource Temporary Unavailable about xray-core HOT 11 CLOSED

Even if no connection is established, xray will at least output log to prompt that xray has been started. Are you sure you have correctly get the log

from xray-core.

Ouch, I was hugely mistaken. I had a bunch of config files and I thought the one being used by the init script had log verbosity set to debug.

I fixed that by setting it to debug. And I can connect to the server from the client, the server is also accepting the incoming connections which could be seen in the logs. However, the sites are not properly loading on the client side, instead stuck on an infinite loading screen.

And the resource not found syscalls.

However, one thing to mention is I am running xray from a chrooted environment. I copied all the dependencies, and also through the system calls figured out it needs /etc/resolv.conf and /etc/hosts files to function which I also copied, and that setup worked properly on OpenBSD 7.4. (I also ran xray without chroot and same behavior)

Note; I am using nekoray on the client side. I used both of what they call "Xray" and "sing-box" "bases".

from xray-core.

The issues template has requested to provid client config, do not say "I am using xxxx gui client"....
And there is sitll no log

from xray-core.

I apologize for the inconvenience.

Xray client and server configs: https://pastebin.com/hEwyUxbb
Xray access logs: https://pastebin.com/DNRYsMEL
Xray error logs: https://pastebin.com/nJyVAAdG

Note: I have replaced the username, server and client IP addresses, credentials and the SNI. I hope that wouldn't be any issue. And for the error and access logs, I did head -n 100 since the logs files were much bigger in size.

from xray-core.

Please raise it with golang x/sys
https://cs.opensource.google/go/x/sys

from xray-core.

Go 大佬秒回了 golang/go#36435 感谢报告这个问题
Closing as known limitation

from xray-core.

@yuhan6665 the issue referenced above relates to the migration from direct syscalls to libc-based syscalls. That was multiple years ago and is not the issue here.

@repliqa if it worked on OpenBSD 7.4 but not on OpenBSD 7.5, the most likely cause is code that is calling syscall.Syscall* - either directly in this code base, in a dependency or an out-of-date dependency. Running under egdb with a breakpoint on the syscall.Syscall* functions should identify the source of the call.

from xray-core.

And as suspected:

from xray-core.

hmm interesting. It may work if you turn off readv (via env var xray.buf.readv) and sockopt. Thanks for your info!

from xray-core.

Will the source code be updated so Xray works on OpenBSD 7.5 or future versions? OpenBSD 7.6 will soon be out and 7.4 would being discontinued. And also, I think the issue needs to be reopened. @yuhan6665 @Fangliding

from xray-core.

@repliqa Please try turn off readv (via env var xray.buf.readv) and sockopt. If it still happens, please try to get logs as mentioned in #3291 (comment)

from xray-core.