A "bad ioctl syscall 21537" error occurred

system · October 6, 2017, 1:25am


	Attention	Topic was automatically imported from the old Question2Answer platform.
	Asked By	ferhand
	Old Version	Published before Godot 3 was released.

I have an export project in html5 which try to connect to a web site via http post and get…but from the start this error shows…

bad ioctl syscall 21537

abort(“bad ioctl syscall 21537”) at jsStackTrace@file:///D:/godot/Proyectos/HTML5/internetLeadboard/LeadBoardTest.js:1:17999

¿What in the world is going on?

system · October 7, 2017, 3:13am


	Reply From:	Grass H0PEr

“export project in html5”
“connect to a web site via http post”

It seeeeems like Godot’s HTTPClient isn’t implemented for exporting a game project to a Web format. If I’m understanding this correctly.

Here’s a link to the github page about this error titled

Listening to socket fails when exporting to HTML5 :

github.com/godotengine/godot

Listening to socket fails when exporting to HTML5

opened 04:06PM - 24 May 17 UTC

closed 10:04PM - 24 May 17 UTC

JonasPf

archived platform:web

**Operating system or device - Godot version:** Ubuntu 16.04 with Godot 2.1.3….stable.official **Issue description:** My godot project listens to a socket using this code: ``` var port = 4545 var server = TCP_Server.new() func _ready(): if server.listen(port) == 0: print("Server running on port " + str(port)) set_process(true) else: print("Cannot listen on port " + str(port)) get_tree().quit() ``` I export it to HTML5 and run it locally using the python internal webserver: `sudo python -m SimpleHTTPServer`. When I open the webpage, it starts loading and fails with the following message: ``` **WARNING**: At: ./drivers/unix/socket_helpers.h:87:_socket_create() - Unable to set/unset IPv4 address mapping over IPv6 bad ioctl syscall 21537 abort("bad ioctl syscall 21537") at Error at jsStackTrace (http://127.0.0.1:8000/index.js:1:17538) at stackTrace (http://127.0.0.1:8000/index.js:1:17709) at abort (http://127.0.0.1:8000/index.js:3:12282) at ___syscall54 (http://127.0.0.1:8000/index.js:1:174652) at qoj (http://127.0.0.1:8000/index.asm.js:27:104858) at Array.CRa (http://127.0.0.1:8000/index.asm.js:18:126238) at Array.cRi (http://127.0.0.1:8000/index.asm.js:14:809595) at Array.MHh (http://127.0.0.1:8000/index.asm.js:16:643720) at p4i (http://127.0.0.1:8000/index.asm.js:14:1161263) at UA (http://127.0.0.1:8000/index.asm.js:23:909097) If this abort() is unexpected, build with -s ASSERTIONS=1 which can give more information. **EXCEPTION**: ```

“AFAIK networking was never implemented for the HTML5 platform.”
– vnen on 2017 May 4th

According to the posts on this page, “direct TCP” networking might not be possible for browser HTML5 games.

“That’s right, in fact this can’t be implemented, direct TCP is impossible in browsers.
However I want to get HTTPClient working in time for 3.0, maybe we’ll also add support for WebSocket or WebRTC eventually”
– eska014 on 2017 May 4th

Here’s a link to the github page for adding HTTPClient support for HTML5 games to Godot 3.0 :

Support HTTPClient in HTML5:

“Raw TCP might not be supported, but it would be nice to expose WebSocket support for all platforms, so then HTML5 does have something.”
– nhydock on 2017 July 10th

You could keep an eye on it every now and then to see how the progress is coming along.

Best wishes
& hope there’s a way to get your game working the way you want!

I’m not an expert on networking, so maybe there’s an alternative method to achieve the same functionality you’re looking for.