|
Author
|
Message
|
|
Marc Boon
|
Saturday 18 February 2006 1:12:23 pm
I had this same error 4 weeks ago: can't login to admin site, browser returns "Document contains no data" after about 5 seconds. Public site runs fine.
When I had this error 4 weeks ago, I posted a forum message(1) but did not get any response (just like 3 other questions still waiting for an answer...(2)) and then I just reinstalled everything.
But now I have a lot of work done, and I don't want to start from scratch again!
Not a single error message in the eZ publish logs, or Apache logs. What can I do? Is the database corrupted? How can I check this?
I restarted Apache, increased PHP memory limit to 128M, what else can I do?
Apache 2.0.55
PHP 4.4.2
MySQL 4.1.16
eZ Publish 3.7.3
Win32 1) http://ez.no/community/forum/general/can_t_login_to_admin_anymore_document_contains_no_data
2)
http://ez.no/community/forum/install_configuration/how_to_create_multiple_multilingual_sites_in_one_install
http://ez.no/community/forum/setup_design/template_encoding_problem
http://ez.no/community/forum/setup_design/fetching_an_image_from_related_objects_of_different_kind
|
|
Paul Borgermans
|
Sunday 19 February 2006 3:57:02 am
That looks like a dirty cache problem, try clearing all ("by hand"). Do you run a php accelerator too? I don't run ezp on Win32, it may be a platform specific problem too. --paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Marc Boon
|
Sunday 19 February 2006 4:23:23 am
Clearing cache was the first thing I did (deleted everything from \var\cache).
Is there any way tho check database integrity? Even manually...
|
|
Paul Borgermans
|
Sunday 19 February 2006 12:34:19 pm
Do you have Zend optimiser running? xampp? If yes, disable it: http://blog.coomanskristof.be/2006/01/21/ez-publish-on-combell-webhosting/ and http://ez.no/community/forum/general/document_contains_no_data/re_document_contains_no_data__2 hth --paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
Marc Boon
|
Sunday 19 February 2006 1:58:21 pm
I don't use any optimizer, but thanks for your advice anyway.
I really need to fix this, otherwise the only way I can proceed is to start from scratch, and I'm not looking forward to that.
|
|
Marc Boon
|
Tuesday 21 February 2006 2:42:44 am
Still fighting with this serious issue. Figuring out what causes this, I created a new clean database for testing. After creating some content classes, some nodes, and some objects, I ran into this "Document contains no data"message again. It always happens during browsing for a location for adding a second location to an object, or when moving a node in the content tree.
The module/function where it happens is admin/content/browse/<node_id>.
The first time the browsing for a location succeeds, but the second time it failed. If I click on OK after selecting the location I get the "Document contains no data" message. Clicking on Cancel gives the same message, so I'm completely stuck.
Closing the browser and clearing cookies also doesn't help. I can't login to admin site anymore, with the same message.
This really has to be solved, otherwise eZ Publish is not working for me.
|
|
Łukasz Serwatka
|
Tuesday 21 February 2006 3:50:22 am
Marc, what is your hardware configuration (CPU, RAM, etc)? Do you run any background applications which can take a lot of resources? Can you check Apache logs? Do you have any errors in eZ publish logs? When this error will appear try restart only MySQL, then tell us if this helps. Check also if all tables are correct (use phpmyadmin for example.)
Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog
|
|
Marc Boon
|
Tuesday 21 February 2006 10:08:15 am
Hardware: Pentium 4 2.0GHz, 512MB RAM, Windows 2000 Pro
Taskmanager shows 100% CPU and about 400MB mem usage for 5-10s, after that, the "Document contains no data" popup appears in the browser, and CPU usage falls to 3%, mem usage falls to about 380MB. There doesn't appear to be a resource limit.
I don't get any error message in Apache logs, PHP logs, or eZ Publish logs.
Restarting Apache or MySQL doesn't solve the problem. The database is corrupted somehow. I created a pre-crash and post-crash database dump, and after I restore the database to the pre-crash state, I can access the admin site again. I will file a bug report and include those dumps. Hopefully someone with enough insight can find the source of the error.
I just noticed someone else has a similar problem:
http://ez.no/community/forum/general/help_needed_cannot_log_in_to_admin_siteaccess_anymore
|
|
Marc Boon
|
Tuesday 21 February 2006 10:35:21 am
Filed bug report http://ez.no/bugs/view/7866
|
|
Łukasz Serwatka
|
Wednesday 22 February 2006 4:02:54 am
Marc, I tried yesterday night reproduce your problem in my environment. It crashed once. I used your database dump for tests. But it crashed in different way. I have successfully added locations from your bug report many times. But eZp crashed when I tried remove object. I'm not sure where is the problem yet Since this happens on your database dump only. I tried on new plain installation and everything works without troubles. My test environment was:
Windows XP Proffessional
Apache 1.3.34
PHP 4.4.1 + eAccelerator 0.9.4-dev
MySQL 4.1.15
eZ publish 3.7.3 I will take a look on your problem once again soon.
Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog
|
|
Marc Boon
|
Wednesday 22 February 2006 5:36:06 am
Thanks for testing, Lukasz. I don't use any PHP accelarator, so that might be the reason your crash is different.
Also, I experience the crash in different modules/functions, sometimes in admin/content/browse (when adding location of moving node), sometimes in admin/content/edit (when creating a new subitem).
Now I do a database dump before every edit. In all cases, restoring the pre-crash database after a crash allows me to resume, but if I try to repeat the same action on the same object/node, it crashes again. So I can't really continue with my work.
I also tried reverting to 3.7.2 as suggested by Pascal (database schema is the same, I just copied my design/settings from 3.7.3), but that didn't make any difference.
|