[ZCM] [ZC] 2239/10 Resolve "ascii codec error - file:error_log"

"Collector: Zope Bugs, Features, and Patches ..." <[email protected]>
Newsgroups gmane.comp.web.zope.devel.collector-monitor
Message-ID <[email protected]>
Issue #2239 Update (Resolve) "ascii codec error - file:error_log"
 Status Resolved, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2239

==============================================================
= Resolve - Entry #10 by ajung on Jan 13, 2007 6:33 am

 Status: Pending => Resolved

ZPT Unicode issues will be resolved in Zope 2.10.2+
________________________________________
= Comment - Entry #9 by knowit on Nov 17, 2006 9:09 am

ok we got the error, one user was "müller" with an german "Umlaute" so he was owner of an folder and objects. 

no object or folder was with an ü. 

so for the next time it would be nice that zope didnt accept usernames that can make problems in some cases. 

many thx for the help here
________________________________________
= Comment - Entry #8 by philikon on Nov 17, 2006 8:50 am

Also, can you please apply this patch:

  http://www.zope.org/Collectors/Zope/2180/zptunicode2.patch/view

and check whether the problem goes away...
________________________________________
= Comment - Entry #7 by ctheune on Nov 17, 2006 8:44 am

Actually I don't think it's a problem with a traceback. But that's easy to determine:

Can you try to restart the server and look at the log?

There shouldn't be any errors then, so if the unicode problem still occurs it's probably something else.

Maybe an Umlaut or something in some static data, like hostnames or similar?
________________________________________
= Comment - Entry #6 by philikon on Nov 17, 2006 8:36 am

That screenshot still is about the traceback you get because of the unicode problem. The unicode problem, however, is due to something behaving abnormally regarding 8bit strings. My *suspicion* is that that is a traceback that you can't see on the ZMI (simply because the unicode error is masking the other error). But you should be able to see it in one of the 'log' files on the filesystem.

If you're experiencing this problem on a production system (you say you can't switch to debug mode), then you should at least be able to reproduce this on your development system. Please provide more info on how to reproduce it, it will help us track down the problem.
________________________________________
= Comment - Entry #5 by knowit on Nov 17, 2006 8:32 am


Uploaded:  "zmi-rdb.jpg"
 - http://www.zope.org/Collectors/Zope/2239/zmi-rdb.jpg/view
I cant run the zope instance in debug mode now. The error occured when i do a click on the error_log. 

I have done an screenshot of the problem, in the source i dont get an traceback.
________________________________________
= Comment - Entry #4 by philikon on Nov 17, 2006 8:05 am

That's the traceback you got when viewing the error_log. But what's the original error+traceback that led to this problem?
________________________________________
= Comment - Entry #3 by knowit on Nov 17, 2006 8:02 am

here is the traceback

2006-11-17T13:54:39 ERROR Zope.SiteErrorLog https://rdb.kicms.de/error_log/manage_main
Traceback (innermost last):
  Module ZPublisher.Publish, line 115, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 41, in call_object
  Module Shared.DC.Scripts.Bindings, line 313, in __call__
  Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
  Module Products.PageTemplates.PageTemplateFile, line 121, in _exec
  Module Products.PageTemplates.PageTemplate, line 89, in pt_render
  Module zope.pagetemplate.pagetemplate, line 118, in pt_render
  Module StringIO, line 271, in getvalue
UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 2: ordinal not in range(128)
________________________________________
= Comment - Entry #2 by philikon on Nov 17, 2006 7:53 am

Can you elaborate on the circumstances a bit more, please? The error you're seeing is due to *something* containing non-unicode 8bit strings. Where you going to the error_log after an error occurred to see the traceback? If so, please provide that traceback (you can get it from one of the log files in INSTANCE/log, I believe).

________________________________________
= Request - Entry #1 by knowit on Nov 17, 2006 4:19 am

I have a problem with zope 2.10.0 - when i click on the error_log in the root folder i got this error: 

Site Error
Error Type: UnicodeDecodeError
Error Value: 'ascii' codec can't decode byte 0xfc in position 2: ordinal not in range(128)
==============================================================
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.