-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Arch Linux (stable) on Scaleway C1 ARMv7 (32 bits), it won't fully start #384
Comments
|
@viraptor he's running 1.5.8 from arch upstream and it looks like seccomp again, as the journal logs have some seccomp prints. I'm confused as to how it could fail this way after the latest changes :( |
|
That's likely. I don't have an ARM system to test on unfortunately. I'd be happy to assist in debugging, but for now, making seccomp x86/64-only may be a better option - all of it is pretty much architecture-specific. @ChazyTheBest If you have time, could you look at Line 50 in 3b11d16
|
|
I swear I tested it on my rpi's... I don't personally have access to whatever system this is, so I'll probably blacklist arm like you said. |
|
The thing is that the code depends on:
Even if you tried on Rpi, it could have a differ in some way from Scaleway's platform :( I'd love to support as many as possible, but it's actually only doable if you have the platform available for testing. I'll submit a whitelist patch soon. |
|
Yeah, this is not quite as fun as I was hoping. People are enabling this without much/any testing and we're probably losing users. :( |
|
@viraptor Sure, provided there's no omitted steps in that guide, I think I can manage. I'll start once I get home. |
|
This is what I get: http://termbin.com/u8fa Sorry I don't understand much, If i'm missing something please specify and I'll do it. https://gist.github.com/ChazyTheBest/c22312485b10bcb5bee0752f71906f08 |
|
good project! |
|
@viraptor anything I can help with? I'm planning on cutting another release in the next week, almost been a month already. would be excellent to nip this. |
|
looks like I'll be blacklisting ARM from seccomp, fwiw. |
|
ended up flipping the defaults in 1.5.9. leaving this open a little longer in case we want to try to understand what the delta was. |
|
gonna close this out. no complaints on 1.5.9, and we're continuing to slowly work on it now that it's been moved to safer defaults. |
Today I performed a full system upgrade and memcached stopped working, I can connect to it though, but it won't respond anything:
I have to open another terminal (ssh) and use systemctl to stop memcached for it to release the other session.
It works if I manually build the latest tarball from https://memcached.org/.
The text was updated successfully, but these errors were encountered: