Skip to content
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

Error opening child process: No such file or directory #29

Open
zzmOVO opened this issue Oct 12, 2021 · 5 comments
Open

Error opening child process: No such file or directory #29

zzmOVO opened this issue Oct 12, 2021 · 5 comments

Comments

@zzmOVO
Copy link

zzmOVO commented Oct 12, 2021

Can you tell me how to solve this problem ?

@alexandervanrenen
Copy link
Collaborator

We would need a lot more context to even try. I would recommend to just use a debugger (gdb) and figure out why it is crashing. Overall it is quite a bit of code, but the individual benchmarks are only a few 100 lines each. So the first step would be to figure out for which communication method it crashes.

Feel free to post any progress on the problem, we would be interested in fixing this :)

@zzmOVO
Copy link
Author

zzmOVO commented Oct 12, 2021

when I run mq.server, it point out 'Reduced the message size to 2048 bytes!',can you tell me how to reduced the message?

@alexandervanrenen
Copy link
Collaborator

This is because message queues are limited to a certain size. On our testing systems it was 2048. You can try increasing the limit and see if it works on your machine. If you find a better way of doing that, let us know:

// Note that 2048 seems to the maximum allowed
// size on my system. There is no way to adjust
// this value, unfortunately (can only adjust
// the maximum amount of messages allowed in the
// queue, but not change the size of messages)
#define MAXIMUM_MESSAGE_SIZE 2048

@DanielEbert
Copy link

DanielEbert commented Jan 29, 2022

Can you tell me how to solve this problem ?

Had the same problem because I named the 'build' folder something else. Naming it 'build' fixed the problem for me

@manzidi
Copy link

manzidi commented Mar 23, 2022

I also had the same issue when I built the binaries from one machine and copied them to another machine. So you might consider rebuilding if you copy the files to another machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants