Binary executables - Flyio

Questions / Help
1

Hello, I have mentioned this in a previous post, but I thought it would be more appropriate to open a new topic. chmod: cannot access 'engines/komodo-141-linux'$'\r': No such file or directory

I don’t understand how I can run “Binary executable” files on Flyio, I’m working on a Python project and while these python files are running, a “chess engine”, a “.exe” file needs to run behind the scenes. But just like I do on Heroku, Since it wouldn’t work after deploying, I found Linux binary format versions and deployed it that way. But even though I did the same thing what i did on Heroku (at least as far as I remember) , I couldn’t run it and I get an error:

2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] ERROR Quitting lichess-bot due to an lichess-bot.py:1091
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] error:
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] Traceback (most recent call
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] last):
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] File
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] “/workspace/lichess-bot.py”,
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] line 1088, in
–
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] chess.engine.EngineTerminatedEr
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] ror: engine process died
2023-10-24T17:46:31.126 app[e2860eec460768] ams [info] unexpectedly (exit code: -11)
2023-10-24T17:46:32.149 app[e2860eec460768] ams [info] INFO Main child exited normally with code: 0

Images:

image
image905×276 10.7 KB

config.yml:
image

fly.toml
image

run.sh
image

And my Procfile
image

My python files are working fine, i guess.
Thank you in advance for your help!

2

Hi,

Your process is segfaulting (died unexpectedly (exit code: -11)). This is either a binary that’s somehow incompatible, or an out-of-memory situation.

The first thing I would recommend trying is increasing memory, since this was running on the smallest instance (256MB). If that doesn’t help, you can try logging into the instance (fly ssh console) and running the engine process manually to see what it says . I think the engine process is ./engines/komodo14.

  • Daniel
3

Yes, Increasing the Memory and vCPU with the “fly scale vm shared-cpu-4x” command solved the problem. Thank you for the support, they are working now.

4

From How To to Questions / Help

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.