zope/pone dies without traceback:cant uplaod data with umlauts anymore
Hi there, I want to upload data trough a form into a database. This used to work fine for a year or so. Now when ever there are non ascii characters in the text to upload zope dies without any traceback but the following: There is no entry in the error log, neither in plone nor in one of zope's log files. I tried to intercept the data, but it looks as if the error happens before I have a chance to see it. I am grateful for any help Robert Zope runs on a linux Zope Version (Zope 2.7.8-final, python 2.3.5, linux2) Python Version 2.3.5 (#1, Feb 20 2005, 19:08:57) [GCC 3.3.3 (SuSE Linux)] System Platform linux2 SOFTWARE_HOME /home/zope/Zope/lib/python ZOPE_HOME /home/zope/Zope INSTANCE_HOME /home/zope/instances/redcor CLIENT_HOME /home/zope/instances/redcor/var Network Services ZServer.HTTPServer.zhttp_server (Port: 8180) ZServer.FTPServer.FTPServer (Port: 8121) ZServer.HTTPServer.zwebdav_server (Port: 9180) Process Id 20147 (1115786160) Site Error An error was encountered while publishing this resource. *Error Type: UnicodeDecodeError* *Error Value: 'ascii' codec can't decode byte 0xc3 in position 0: ordinal not in range(128)* ------------------------------------------------------------------------ Troubleshooting Suggestions * The URL may be incorrect. * The parameters passed to this resource may be incorrect. * A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the error log. If the error persists please contact the site maintainer. Thank you for your patience.
robert rottermann wrote:
*Error Type: UnicodeDecodeError* *Error Value: 'ascii' codec can't decode byte 0xc3 in position 0: ordinal not in range(128)*
I would be extremely suprised is this actually killed the Zope process. What database adapter are you using? If Zope was dying, how did it render the above message?! Unicode errors can be tricky to read, but if you do so carefully, you'll see that something is trying to turn a string into a unicode, and that string contains data which the default ascii codec can't handle. This will happen most often when you should be manually decoding a unicode encoded string... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
robert rottermann wrote at 2005-11-8 20:22 +0100:
I want to upload data trough a form into a database. This used to work fine for a year or so.
Now when ever there are non ascii characters in the text to upload zope dies without any traceback but the following:
Thus, you use a C level debugger to find out why Zope dies. You attach the C level debugger to your Zope process (works with both GDB under *nix and the MS C level debugger under Windows) and provoke the Zope death. The debugger should get control and you can analyse where the death would happen. You probably will need a Python build with debugging symbols. -- Dieter
participants (3)
-
Chris Withers -
Dieter Maurer -
robert rottermann