Running cron I see the following output (several thousand lines of it) before we get a segmentation fault:

Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Duplicate entry '0' for key 'PRIMARY' [warning]
query: INSERT INTO subscriptions_user (uid) VALUES(0) database.mysql.inc:148
Segmentation fault

Any idea what could be going on? I suspect it's a drupal_write_record gone wrong?

Comments

salvis’s picture

salvis
he/his
commented
Status: Active » Postponed (maintainer needs more info)

Any idea what could be going on?

No, no idea. I assume this has worked before? Find out what has changed between when it worked and when it started failing.

You're using an old version. This is probably not the cause of this issue, but after you've found and fixed the cause, you should update.

salvis’s picture

salvis
he/his
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

No follow-up.

sillygwailo’s picture

sillygwailo
Location Toronto, ON
commented

I got similar errors (not quite the same) and the segmentation fault. It was because I had used an ancient version of the module before. The fix was to

  1. backup my database
  2. delete all references to the Subscription module in the {system} table
  3. drop the {subscriptions} table
  4. re-enable the module(s)