I get server error any time I try to add any node:
EACCELERATOR(11010): PHP crashed on opline -4919132149891353083 of form_execute_handlers() at ...../includes/form.inc:1390
When I switch off Domain Access, the error goes away. I've tried to go back to Domain 7.x.2.12 - same thing happens. I'm not sure if it's a bug or I just need to adjust some server settings.

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

No idea. I don't use eAccelerator, though I see that MAMP supports it.

That sounds like a missing include file.

julia_g’s picture

julia_g commented

In fact, digging further, it looks like the actual error was different:
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2280-1-domain_id' for key 'PRIMARY': INSERT INTO {node_access} (nid, realm, gid, grant_view, grant_update, grant_delete) 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); Array ( [:db_insert_placeholder_0] => 2280 [:db_insert_placeholder_1] => domain_id [:db_insert_placeholder_2] => 1 [:db_insert_placeholder_3] => 1 [:db_insert_placeholder_4] => 1 [:db_insert_placeholder_5] => 1 ) in node_access_write_grants() (line 3334 of ...../node/node.module).

I'm not sure if this has anything to do with eaccelerator issue, maybe it was just a coincidence and I should open a new issue.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Category: bug » support

Well, that insert error shouldn't happen, and suggests a core bug or a module not following the API. Definitely does not happen with eAccelerator disabled.

The actual insert into {node_access} -- the cause of that error -- is handled by http://api.drupal.org/api/drupal/modules--node--node.module/function/nod... after invocation by http://api.drupal.org/api/drupal/modules--node--node.module/function/nod...

Labeling as support request, because this is not really a module issue.

julia_g’s picture

julia_g commented
Category: support » bug

I've disabled eAccelerator and the PHP crash doesn't happen any more, but the PDOException is still there. Should I submit it as core issue? This error doesn't happen without Domain Access, so they might send me back to you.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented

This is probably of no use but DA6.x works fine with eAccelerator without any tweaking.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Well, 7.x.3 is not stable or supported. Why are you using that version and not 7.x.2?

Turning on eAccelerator seems to have no effect.

I also can't replicate that PDO error.

What other node access modules do you have installed? How are you saving nodes?

FILING BACK TO SUPPORT REQUEST. People need to *stop changing my tags*.

julia_g’s picture

julia_g commented

OK, figured it out finally.
There was a conflict with the Rules module - I had a rule that was publishing page if submitted by trusted contributors, and keep unpublished otherwise. The Rules module called node_save the second time. Sorry for wasting your time.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

It's ok. Still, Rules shouldn't be causing the PDO error. That sounds like a Rules bug.

fago’s picture

fago
Primary language German
Location Vienna
commented

FYI: see #1146244: node_access integrity constraint violation on module_invoke_all('node_' . $op, $node);