This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » Install & configuration » Error after upgrading eZDFS Cluster...

Error after upgrading eZDFS Cluster to 4.5

Error after upgrading eZDFS Cluster to 4.5

Thursday 26 May 2011 11:25:31 am - 1 reply

Hello eZ Community!

I have a big problem after upgrading a eZDFS Cluster to eZ Publish 4.5. I started upgrading a few days ago on eZ Publish 4.2 with the result that all following version are working well, excepted the latest release 4.5.

If I try to enter the frontend siteaccess I'm getting just a fatal error (Debug output enabled, but not shown at that moment):

Fatal error: eZ Publish did not finish its request

But I think I have discovered the problem in the warning.log, all other log files seem to be fine.

[ May 25 2011 11:31:15 ] [IP address] Timing Point: Module start 'content'
[ May 25 2011 11:31:15 ] [IP address] eZClusterFileHandler::cleanupGeneratingFiles:
Execution was stopped while one or more files were generating. This should not happen.

Accessing the admin siteaccess worked well, so I started to debug the frontend siteaccess to locate the problem. After some time of debugging I found out that a simple type of fetch caused the error:

{def $simple_fetch = fetch( 'content', 'node', hash( 'node_id', 2 ) )}

I included this example fetch in the admin siteaccess and from that point on it stopped working like the frontend with the same error.

After more testing I found out that not the fetch caused the problem. The output or the way the fetch result is being accessed seems to be the problem, because this worked well:

{def $simple_fetch = fetch( 'content', 'node', hash( 'node_id', 2 ) )}

I have no idea how to go on. Any hints are appreciated.

Thanks in advance for your replies!


Friday 03 June 2011 6:25:35 pm

I have not tested your code, but I think attribute() requires  "show" to be a string when passed.

{$test|attribute( 'show' )}

See the doc page:


Also be sure to check the Apache error logs just to be sure you're not missing anything else.


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from