ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
* [ruby-core:95230] [Ruby master Bug#16239] Crash when access postgresql-12
       [not found] <redmine.issue-16239.20191004175906@ruby-lang.org>
@ 2019-10-04 17:59 ` mark.siemers
  2019-10-04 18:11 ` [ruby-core:95231] [Ruby master Bug#16239] Crash when accessing postgresql-12 merch-redmine
  2019-12-04 21:10 ` [ruby-core:96113] " bandy.chris
  2 siblings, 0 replies; 3+ messages in thread
From: mark.siemers @ 2019-10-04 17:59 UTC (permalink / raw)
  To: ruby-core

Issue #16239 has been reported by marksiemers (Mark Siemers).

----------------------------------------
Bug #16239: Crash when access postgresql-12
https://bugs.ruby-lang.org/issues/16239

* Author: marksiemers (Mark Siemers)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
This may have been caused by a recent upgrade to postgresql 12 on my local machine (running OS X Mojave). pgAdmin 4 is also giving me an error.

I am running a rails console, and as soon as I try to do anything with ActiveRecord that accesses the database, I get an error and a crash report,



---Files--------------------------------
ruby_2019-10-04-105528_Marks-MacBook-Pro.crash (57.3 KB)


-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [ruby-core:95231] [Ruby master Bug#16239] Crash when accessing postgresql-12
       [not found] <redmine.issue-16239.20191004175906@ruby-lang.org>
  2019-10-04 17:59 ` [ruby-core:95230] [Ruby master Bug#16239] Crash when access postgresql-12 mark.siemers
@ 2019-10-04 18:11 ` merch-redmine
  2019-12-04 21:10 ` [ruby-core:96113] " bandy.chris
  2 siblings, 0 replies; 3+ messages in thread
From: merch-redmine @ 2019-10-04 18:11 UTC (permalink / raw)
  To: ruby-core

Issue #16239 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Open to Third Party's Issue

This crash happens inside the pg gem. It's either caused by the pg gem, libpq (PostgreSQL), or one of the internal Mac OS libraries listed. 

```
7   ???                           	0x0000000200000000 0 + 8589934592
8   com.apple.security            	0x00007fff3f57c059 invocation function for block in Security::KeychainCore::StorageManager::tickleKeychain(Security::KeychainCore::KeychainImpl*) + 287
9   libdispatch.dylib             	0x00007fff5fd6d63d _dispatch_client_callout + 8
10  libdispatch.dylib             	0x00007fff5fd79129 _dispatch_lane_barrier_sync_invoke_and_complete + 60
11  com.apple.security            	0x00007fff3f57be47 Security::KeychainCore::StorageManager::tickleKeychain(Security::KeychainCore::KeychainImpl*) + 441
12  com.apple.security            	0x00007fff3f37cae2 Security::KeychainCore::KCCursorImpl::next(Security::KeychainCore::Item&) + 230
13  com.apple.security            	0x00007fff3f523c98 Security::KeychainCore::IdentityCursor::next(Security::SecPointer<Security::KeychainCore::Identity>&) + 192
14  com.apple.security            	0x00007fff3f545f2f SecIdentitySearchCopyNext + 145
15  com.apple.security            	0x00007fff3f550956 SecItemCopyMatching_osx(__CFDictionary const*, void const**) + 238
16  com.apple.security            	0x00007fff3f553fc5 SecItemCopyMatching + 316
17  com.apple.Heimdal             	0x00007fff4feae830 0x7fff4fe5c000 + 337968
18  com.apple.Heimdal             	0x00007fff4fead35e hx509_certs_find + 67
19  com.apple.Heimdal             	0x00007fff4fe88a6c _krb5_pk_find_cert + 246
20  com.apple.GSS                 	0x00007fff364dbd8e _gsspku2u_acquire_cred + 386
21  com.apple.GSS                 	0x00007fff364cb0d8 gss_acquire_cred + 523
22  libpq.5.dylib                 	0x0000000112b4b77d pg_GSS_have_cred_cache + 54
23  libpq.5.dylib                 	0x0000000112b39edf PQconnectPoll + 6377
24  libpq.5.dylib                 	0x0000000112b36f8b connectDBComplete + 232
25  libpq.5.dylib                 	0x0000000112b37112 PQconnectdb + 36
26  pg_ext.bundle                 	0x000000011157ab01 gvl_PQconnectdb_skeleton + 17
27  ruby                          	0x000000010f1dfff9 call_without_gvl + 185
28  pg_ext.bundle                 	0x000000011157aadd gvl_PQconnectdb + 45
29  pg_ext.bundle                 	0x000000011157fcb9 pgconn_init + 121
30  ruby                          	0x000000010f221b1c vm_call0_body + 604
```

If I had to guess, this is a PostgreSQL issue with GSS authentication on Mac OS.  Since PostgreSQL 12 was just released, it may be a regression.  Please try contacting the PostgreSQL developers.

----------------------------------------
Bug #16239: Crash when accessing postgresql-12
https://bugs.ruby-lang.org/issues/16239#change-81906

* Author: marksiemers (Mark Siemers)
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.4p104 (2019-08-28 revision 67798) [x86_64-darwin18]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
This may have been caused by a recent upgrade to postgresql 12 on my local machine (running OS X Mojave). pgAdmin 4 is also giving me an error.

I am running a rails console, and as soon as I try to do anything with ActiveRecord that accesses the database, I get an error and a crash report,



---Files--------------------------------
ruby_2019-10-04-105528_Marks-MacBook-Pro.crash (57.3 KB)


-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [ruby-core:96113] [Ruby master Bug#16239] Crash when accessing postgresql-12
       [not found] <redmine.issue-16239.20191004175906@ruby-lang.org>
  2019-10-04 17:59 ` [ruby-core:95230] [Ruby master Bug#16239] Crash when access postgresql-12 mark.siemers
  2019-10-04 18:11 ` [ruby-core:95231] [Ruby master Bug#16239] Crash when accessing postgresql-12 merch-redmine
@ 2019-12-04 21:10 ` bandy.chris
  2 siblings, 0 replies; 3+ messages in thread
From: bandy.chris @ 2019-12-04 21:10 UTC (permalink / raw)
  To: ruby-core

Issue #16239 has been updated by cbandy (Chris Bandy).


@jeremyevans0 is correct. This is a fatal interaction between the PostgreSQL 12 client libraries and the GSS implementation provided by macOS. This is being tracked in the pg gem at https://github.com/ged/ruby-pg/issues/311.

An immediate workaround is to include `gssencmode: "disable"` or `gssencmode=disable` in your connection configuration.

----------------------------------------
Bug #16239: Crash when accessing postgresql-12
https://bugs.ruby-lang.org/issues/16239#change-82972

* Author: marksiemers (Mark Siemers)
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.4p104 (2019-08-28 revision 67798) [x86_64-darwin18]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
This may have been caused by a recent upgrade to postgresql 12 on my local machine (running OS X Mojave). pgAdmin 4 is also giving me an error.

I am running a rails console, and as soon as I try to do anything with ActiveRecord that accesses the database, I get an error and a crash report,



---Files--------------------------------
ruby_2019-10-04-105528_Marks-MacBook-Pro.crash (57.3 KB)


-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-12-04 21:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <redmine.issue-16239.20191004175906@ruby-lang.org>
2019-10-04 17:59 ` [ruby-core:95230] [Ruby master Bug#16239] Crash when access postgresql-12 mark.siemers
2019-10-04 18:11 ` [ruby-core:95231] [Ruby master Bug#16239] Crash when accessing postgresql-12 merch-redmine
2019-12-04 21:10 ` [ruby-core:96113] " bandy.chris

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).