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

Mac OS ARM - P2Pool 3.6.1 fails to run #274

Closed
nullifiedtoast opened this issue Sep 2, 2023 · 16 comments
Closed

Mac OS ARM - P2Pool 3.6.1 fails to run #274

nullifiedtoast opened this issue Sep 2, 2023 · 16 comments

Comments

@nullifiedtoast
Copy link

3.6.1 seems to build and start up just fine, however the longest I have gotten it to run for was 1 minute 16 seconds with the usually time of 5-7 seconds before it suddenly just stops with the exit code of failed. However there is absolutely nothing being shown in the logs about any errors. Everything looks normal and like 3.5 did and then it just abruptly stops.

@SChernykh
Copy link
Owner

Did you build it yourself, or use the release binary?

@nullifiedtoast
Copy link
Author

I have tried both options, as well as trying to let Gupax update its bundled version and test that one. All three are doing the same thing with no reason given in the logs for the abrupt exit.

@SChernykh
Copy link
Owner

What's the version of your MacOS SDK? There is a known issue with macOS arm builds: monero-project/monero#8657 (comment)

But does P2Pool v3.5 release binary work fine?

@nullifiedtoast
Copy link
Author

The SDK is 13.3 and the v3.5 does work just fine and is what I am still currently using.

@SChernykh
Copy link
Owner

So it probably means that the new way release binaries are built also uses new MacOS SDK, this is unfortunate. I'll have to revert to the previous build script for MacOS ARM binaries.

@nullifiedtoast
Copy link
Author

I shall await patiently for the next patch to be released and try to update from v3.5 then. Thank you for all your hardwork and dedication towards helping the monero community!

@SChernykh
Copy link
Owner

@nullifiedtoast
Copy link
Author

I tried both the release binary and building from source again and they both still only run for about 20 seconds before the exit with the failed code. Once again checked the logs and it shows it running normal and then just abruptly stops again.

@nullifiedtoast
Copy link
Author

Built from source runs for about 20-30 seconds and the release binary doesn't even want to start it immediately throws the failed exit code

@SChernykh
Copy link
Owner

@nullifiedtoast can you test the binary in the attachment? If this one doesn't work, then I don't know what changed since v3.5
p2pool.gz

@nullifiedtoast
Copy link
Author

The version you just sent me started up and is running just like the v3.5 was with no issues

@SChernykh
Copy link
Owner

Good. So it has something to do with LTO (link-time optimization). Apple clang compiler has some bug somewhere in LTO. I'll update the v3.6.2 release with this binary.

@nullifiedtoast
Copy link
Author

I am glad you were able to figure out the issue. Thank you again for the fast responses to get it fixed.

@nullifiedtoast
Copy link
Author

Only thing I noticed about the version you just sent me was that my miners were not able to connect to the pool with it.

@SChernykh
Copy link
Owner

Check your firewall settings (path to the binary, port numbers). You probably need to approve the new binary.

@nullifiedtoast
Copy link
Author

I needed to move the binary into the folder with the rest of p2pool files. That was my mistake all is working correctly.

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

2 participants