Closed (fixed)
Project:
Provision
Version:
5.x-0.1-alpha1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Apr 2008 at 22:31 UTC
Updated:
12 Jun 2014 at 08:41 UTC
Jump to comment: Most recent
Comments
Comment #1
anarcat commentedWhat should be made clear here is that the big problem here is that the provisionning command doesn't return a properly serialized value. That mysql warning should never appear out there, it breaks the hosting's framework expectations (which is: serialized output).
I guess the IPC should be rationalized around here...
Comment #2
adrian commentedi changed things around a bit.
now it returns 1 on success. meaning that it needs to complete successfully to trigger removing from the queue.
Comment #3
anarcat commentedI don't get this error anymore so I assume this was fixed somehow.
Comment #4
anarcat commentedActually, no I still see this error.
Steps to reproduce:
* create test.hostmaster.koumbit.net, run the queue
* create test2.hostmaster.koumbit.net, run the queue
* create test3.hostmaster.koumbit.net, run the queue, this error shows up:
Running the provision hook manually works.
Comment #5
anarcat commentedNote that the error doesn't happen the second time the queue is run. This is a very weird bug.
Comment #6
anarcat commentedThis could be related to the work done on the status field:
http://drupal.org/node/259382#comment-855943
Comment #7
adrian commentedI still have no idea how this works. Never had it happen to me.
Nor had it happen on hm2.bryght.com.
We're going to need additional testers on this issue.
Comment #8
anarcat commentedSo if this doesn't happen anymore, the bug is fixed. I'll open another issue for the more general IPC problem.
Comment #9
anarcat commentedThere: http://drupal.org/node/269914
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.