Workflow errors

« 
Previous topic
|
Install & configuration
|
Next topic
 »
Author Message

Eivind Marienborg

Wednesday 25 January 2006 7:45:32 am

On one of the sites I'm running, users can sign up, but have to get approved (using the collaboration-system) before actually being published, and thus able to log in.

Having runned this system for quite som time, I have discovered some mysterious behaviour from the system.

The objects appear in the collaboration-list. I enter the objects, and approve them for publishing. A cronjob-runned workflow runs the workflow.php script. But now it turns out that some objects doesn't get published.

Running the workflow-script manually with debug enabled, outputs this:

Running cronjobs/workflow.php
Checking for workflow processes

PHP Fatal error:  Call to a member function on a non-object in /data/www/html/vhost/dev.site.no/kernel/classes/workflowtypes/event/ezmultiplexer/ezmultiplexertype.php on line 214

Fatal error: eZ publish did not finish its request
The execution of eZ publish was abruptly ended, the debug output is present below.
Timing: ()
Script cronjobs/workflow.php starting

Warning: (PHP)
Undefined index:  no-cache-adviced in /data/www/html/vhost/dev.site.no/lib/ezi18n/classes/eztstranslator.php on line 64

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Error: (eZContentObject::fetch())
Object not found (29036)

Error: (Empty body memento in workflow.php)


Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Error: (eZContentObject::fetch())
Object not found (18092)

Error: (Empty body memento in workflow.php)


Error: (eZContentObject::fetch())
Object not found (27273)

Error: (Empty body memento in workflow.php)


Error: (eZContentObject::fetch())
Object not found (15700)

Error: (Empty body memento in workflow.php)


Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Error: (eZContentObject::fetch())
Object not found (16732)

Error: (Empty body memento in workflow.php)


Error: (eZContentObject::fetch())
Object not found (41355)

Error: (Empty body memento in workflow.php)


Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Warning: (PHP)
Use of undefined constant EZ_APPROVE_COLLABORATION_NOT_CREATED - assumed 'EZ_APPROVE_COLLABORATION_NOT_CREATED' in /data/www/html/vhost/dev.site.no/extension/points/eventtypes/event/ezuserapprove/ezuserapprovetype.php on line 257

Error: (eZContentObject::fetch())
Object not found (17058)

Error: (Empty body memento in workflow.php)


Error: (eZContentObject::fetch())
Object not found (32669)

Error: (Empty body memento in workflow.php)


Error: (eZContentObject::fetch())
Object not found (26878)

Error: (Empty body memento in workflow.php)


Error: (eZContentObject::fetch())
Object not found (26878)

Error: (Empty body memento in workflow.php)


PHP Notice:  Undefined variable:  relMemory in /data/www/html/vhost/dev.site.no/lib/ezutils/classes/ezdebug.php on line 1423
Script cronjobs/workflow.php starting 0.0000 sec
Total runtime: 3.4262 sec
Group ini_load:
Load cache: 0.0284 sec (0.8160%), 0.0041 avg sec (7)
Group Mysql Total:
Mysql_queries: 0.7483 sec (21.4680%), 0.0006 avg sec (1239)
Looping result: 0.0865 sec (2.4825%), 0.0001 avg sec (1097)
Group TS translator:
TS init: 0.0090 sec (0.2584%), 0.0045 avg sec (2)
TS cache load: 0.0034 sec (0.0976%), 0.0017 avg sec (2)
TS context load: 0.0016 sec (0.0468%), 0.0008 avg sec (2)

Total script time: 3.4855 sec

The objects remains "unpublished" when I access them in the collaboration view (by clicking them in the collaboration overview, and then the link to their object).

The strange thing is that this seems to happen to random objects.

I'm thinking this might be related to the errors that the workflow-script run into, but tracking down which objects it halts on gets complicated whith no experience with this part of the DB.

Could simply emptying all the collaboration tables be a possible sollution? Or is the data there used even after publishing?

I'm otherwise blank on this. Has anyone runned to this kind of thing before? Any ideas, anyone?

Thanks :)
- Eivind

Leif Arne Storset

Thursday 16 February 2006 8:22:12 am

I have similar problems. I have experienced your problem (random objects not getting published) but it disappeared after I tinkered for a while (I'm sorry to say I didn't record what I did). The problem that remains is that users that register show up directly in the content-object tree, bypassing approval.

I have isolated the bug to the case where ezapprove is set to section Users. If "all sections" is set, the approval process runs normally.

If I run the approval workflow it via the multiplexer, I get similar results: filtering by class or section makes the publishing process bypass approval, while deactivating filtering makes it work.

I get only two error messages running the workflow-cronjob script manually with debug:

Undefined index:  no-cache-adviced in /home/helsekom/public_html/lib/ezi18n/classes/eztstranslator.php on line 64

and 

Warning(): User not found, returning anonymous

.

I suspect something within ezapprove breaks during filtering. I will continue to investigate this problem, but am grasping at straws.

I am unsure whether this problem is related to the one you, Marienborg, are experiencing. How do you filter in your workflow? I cannot answer your question about the collaboration table properly, but suspect that its contents are used for the "collaboration/view/summary" view under "My account".

Leif Arne Storset

Leif Arne Storset

Friday 24 February 2006 6:42:01 am

I've had to give up on this problem. :(

Leif Arne Storset

Stéphane Bullier

Wednesday 01 March 2006 7:30:49 am

You have to erase ; in php.ini on line ;extension=mysql.so in section Dynamic Extensions

Stéphane

Leif Arne Storset

Friday 03 March 2006 2:09:28 am

bobo diallo,

Thank you for your suggestion! However, I am a bit confused.

Firstly, when I check php.ini, I find no option extension=mysql.so.

Additionally, though I know little of PHP's internal workings, I would expect that MySQL wouldn't work at all if the MySQL extension wasn't loaded. Does mysql.so perhaps not control all of PHP's MySQL support, but rather a portion of it?

Leif Arne Storset

Kåre Køhler Høvik

Friday 03 March 2006 2:27:15 am

Hi

I think this behavior is related to this bug : http://ez.no/bugs/view/7898
I've got a temporary patch for it ( see attached file ), but please use it with care. The attached patch will not fix workflow processes which have already been started.

Kåre Høvik
Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.