-
-
Notifications
You must be signed in to change notification settings - Fork 329
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
Segmentation fault from release binary #675
Comments
Update: I failed to note which database it's using. It's SQLite. |
Really not sure what could be causing this, but seems like something in the underlying dependencies on the machine. Here's a comment that might be helpful -- is your VPS using a |
Nope, it's a fairly standard Arch install, with glibc 2.37-2. I don't think that comment is the same issue; in my case the segfault isn't intermittent, it happens immediately every single time I use My desktop is also running Arch with glibc 2.37-2 and everything works fine there; no problems with |
It should be fine with that much RAM. This looks like the salient part to me:
Could you try running |
Ah, that did it. Doing that gives this:
That led me to find that
...allows writefreely to start with |
I don't want to start a "me too" precedent, but... me too. Exact same issue, same solution. To help any decisions about long-term resolution, I'll add:
|
Thanks for confirming @joatca and @xxxserxxx. To solve this particular error, we can release future binaries that use Go DNS resolution instead of libc, so admins get these useful error messages (following gitea's lead here). Just need to update the If either of you want to submit a PR for those, please feel free! Otherwise will get to it when I can. |
A note that replacing |
@joatca while I ended up binding to a different interface (VPN), the lookups are/were only causing segfaults looking up |
Yes, I changed it to the public URL, as served by my reverse proxy. The docs say Full hostname (including scheme) users will see - is that the correct thing to do? |
Caveat: I'm not one of the devs, so all I can say is how mine is set up. In my config, |
This builds with the `netgo` tag, ensuring WF binaries use Go DNS resolution instead of libc, preventing unhelpful errors when the application can't resolve addresses. Closes #675
Not sure if this is related, but I get a different segfault:
This is a new installation in a docker container where I successfully completed the other steps for configuration and key generation. The suggested debug statement above did not reveal anything, but it seems to complain about templates. Is there a default of example template available that I can use? |
@RapidRotator That seems to be a different issue, caused by an uncaught error at templates.go:149. Could you open a separate issue for that? |
Will do. |
Describe the bug
Segfault after setup with the current release binary running in a 1G VPS.
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
./writefreely config start
and./writefreely keys generate
work as expectedwritefreely
segfaults:Expected behavior
No segfault :-)
Application configuration
Version or last commit:
0.13.2
VPS details
The text was updated successfully, but these errors were encountered: