Segmentation fault #538
Comments
|
Contents of |
|
Same here (#311 (comment)) I suspect this came from an update either of krb5 last week or postgresql@14/libpq last month (unlikely) The temporary fix in #311 is still working, just |
|
Great! Temporary fix worked. Thanks @jk779 |
|
Thank you SO much for the temp workaround. That solved it for me. |
|
I'm not sure if there's anything that can be done to fix it in this library. See #311 (comment) for more details. |
|
Thanks for the detailed info, @stanhu. In case it helps anyone else, in a Rails app you can edit which will disable GSSAPI on macOS without requiring every developer to set |
|
I'm getting the same but none of the Postgres 11.16 |
|
@Meekohi If you include the crash log from macOS, that might help. |
|
I rolled back to the older Amazon AMI (Amazon Linux 2) and confirm everything works fine there, so it seems to be something with the newest AMI2023. Apologies but I ditched the machines without getting the logs. |
|
@Meekohi Ok, the GSSAPI issue really only pertains to macOS, so if you're using a Linux system you're likely running into a different problem. |
|
Experiencing this issue as well Postgres 14.5 Running temp fix mentioned above worked for me. Thanks a lot for that 🙏 |
4 tasks
11 tasks
Wow - I spend hours trying to find a resolution to this issue. This was very helpful |
|
Actually after upgrading Rails from 6 to 7, the issue disappeared for me. Maybe because of connection flusher, weird. |
|
fwiw was encountering this in my last role, and we were on Rails 7 on an m1
mac. Not on that code base any more though so can't share any other
interesting details. The workarounds outlined in the above comments did
work for me
…On Thu, Sep 14, 2023 at 3:21 PM Dmitry Vorotilin ***@***.***> wrote:
Actually after upgrading Rails from 6 to 7, the issue disappeared for me.
Maybe because of connection flusher, weird.
—
Reply to this email directly, view it on GitHub
<#538 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLBNRPTYH5HZJLXACVGGCTX2NKLFANCNFSM6AAAAAAZGTBCNI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
This is still happening on Rails 7. |
|
Potentially same segmentation fault occurring with: OS: MacOS Sonoma (14.1.1) Using |
|
Hi guys, I have also the segfaults randomly poping and flushing my databases. ruby 3.2.2,
Thx !!! This is the segfault message : |
|
As mentioned, setting My settings:
|
|
I've recently started to experience this (or a similar) issue when connecting to an RDS instance. Edit: details moved to #555 |
@grncdr Please open a separate issue with the relevant details. |
@Meekohi hey, seems like I have the same issue. Can you describe in more details what have you done to fix it? In your setup do you use RDS or postgresql hosted on EC2? |
|
I rolled back to Amazon Linux 2 and have not tried the newer versions again since. We connect to RDS although I don't think it should matter. |
|
Perhaps this issue should be retitled, There is a separate segfault described in #555. |
robacarp
pushed a commit
to AllYourBot/hostedgpt
that referenced
this issue
Feb 7, 2024
tuxagon
added a commit
to testdouble/double-up
that referenced
this issue
Feb 15, 2024
More information about it can be found [here](ged/ruby-pg#538).
tuxagon
added a commit
to testdouble/double-up
that referenced
this issue
Feb 23, 2024
Introduce matchmaking groups as a replacement to yaml exclusivity This is a pretty large change and some of it was to migrate tests for classes that were touched. The primary aspects to this change include a UI piece for creating matchmaking groups and refactoring the group collection to incorporate the database groups with the yaml config groups. Also, there was a HACK to prevent segfault in test & development with pg See more information [here](ged/ruby-pg#538). --------- Co-authored-by: Ali Ibrahim <[email protected]>
|
Same here: |
|
Same issue here running mutation testing against a rails 7 app with ruby 3.2.3 |
|
I have same issue I try set This project on exactly the same server, but only with PostgreSQL 11 it works without problems. I understood what the reason was. I compared two servers on both Ubuntu 22 and PostgreSQL 12, the only difference was in the openssl version. On openssl version 1.1.1f everything worked fine, but not on version 1.0. After I installed openssl 1.1.1f on the server, everything began to work without problems and without |
|
I ran into this issue as well on CentOS Stream 9, however I was able to work around it by installing an older version of openssl. OS: CentOS Stream release 9 If I manually downgrade to openssl rpm version 3.0.7 without changing anything else, |
jagthedrummer
added a commit
to bullet-train-co/bullet_train
that referenced
this issue
Jul 1, 2024
Some users are reporting crashes on MacOS when first trying to access the database. There's an issue open on `ruby-pg` that describes this temporary workaround. ged/ruby-pg#538 Hopefully fixes: #1379
jagthedrummer
added a commit
to bullet-train-co/bullet_train
that referenced
this issue
Jul 1, 2024
Some users are reporting crashes on MacOS when first trying to access the database. There's an issue open on `ruby-pg` that describes this temporary workaround. ged/ruby-pg#538 Hopefully fixes: #1379
|
If you ended up here like me and no of the fixes mentioned worked, what did work for me was upgrading Postgres to 14.11+, because it seems it was an issue caused by some incompatibility with some openssl version. I'm on macOS 14.5 with M1 Pro, and installed postgres via asdf. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
When trying to access the database I'm receiving a
Segmentation fault.Tried to reinstall the gem, libpq, and the ruby itself. Not sure how to proceed here. Can anyone help me figure it out what is going on?
System
OS: MacOS Ventura (13.4)
Chip: Apple M1
Ruby: 3.2.2
ruby-pg: 1.5.3
Behaviour
The text was updated successfully, but these errors were encountered: