Exact error:
Uncaught exception thrown in shutdown function.
PDOException: SQLSTATE[23505]: Unique violation: 7 ERROR: duplicate key value violates unique constraint "sessions_ssid_key" DETAIL: Key (ssid)=(1hjc116js0k0jivn25gmfubga0) already exists.: INSERT INTO sessions (uid, cache, hostname, session, timestamp, sid, ssid) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6); Array ( ) in _drupal_session_write() (line 169 of /path/to/drupal-7.0-alpha5/includes/session.inc).
Comments
Comment #1
Damien Tournoud CreditAttribution: Damien Tournoud commentedAre you installing using an HTTPS connection?
This is probably related to #715108: Make Merge queries more consistent and robust (and to the related fixes in the secured session support).
Comment #2
DrLou CreditAttribution: DrLou commentedDamien, (sorry, posts crossing in the ether)
Yes, installing over https, as an experiment. Production would often(always?) be under https space.
This error only appeared on attempt to install in https:// space.
To continue with our testing - of a great number of other things - what would you propose as a strategy?
Leave the testbed in non-SSL space?
Or, are are you suggesting that 715108.patch is curative in a PostgreSQL environment?
Comment #3
Damien Tournoud CreditAttribution: Damien Tournoud commentedNot exactly. I'm saying that we need to fix this exact issue with how we store SSL cookies to move #715108: Make Merge queries more consistent and robust forward.
Comment #4
DrLou CreditAttribution: DrLou commentedTks for that reply...
I should surmise then that - ostensibly - moving the site out of SSL space will let us do our other testing (nuts and bolts, interfaces to Drupal) without running into this?
IE, it only comes up in an SSL session-handling environment? TIA, Lou
Comment #5
ogi CreditAttribution: ogi commentedsubscribe