Re: [Zope-dev] logging crash

2002-01-30 Thread Dieter Maurer

Terry Kerr writes:
 > ...
 > 2002-01-30T02:02:02 ERROR(200) ZServer uncaptured python exception, closing 
 > channel  requests:> (exceptions.AttributeError:'None' object has no attribute 'split' 
I use ZopeCVS (similar to Zope 2.5.0) still under Python 2.1.1.
I often see that objects suddenly become "None" objects.
Maybe, that's also your problem.

All know that there are serious memory corruption problems with
Python 2.1.1 and Zope 2.4.x (x <= 3).

I will upgrade in some minutes to Python 2.1.2 and see whether
my problems disappear. If not, then there is probably
another memory corruption problem in Zope. We tacitly expect
it in the new "cAccessControl". It can be disabled in favor
of the Python implented access control module...


Dieter

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] logging crash

2002-01-30 Thread Leonardo Rochael Almeida

On Wed, 2002-01-30 at 03:43, Terry Kerr wrote:
> [...]
> 
> 2002-01-30T02:02:02 ERROR(200) ZServer uncaptured python exception, closing 
> channel  requests:> (exceptions.AttributeError:'None' object has no attribute 'split' 
> [/usr/local/lib/python2.1/asyncore.py|poll|104] 
> [/usr/local/lib/python2.1/asyncore.py|handle_write_event|393] 
> [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/asynchat.py|handle_write|147] 
> [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/asynchat.py|initiate_send|209] 
> [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/asynchat.py|refill_buffer|196] 
> [/usr/local/zope/Zope-2.4.3-src/ZServer/Producers.py|more|108] 
> [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/http_server.py|log|287])
> --
> 2002-01-30T02:02:03 ERROR(200) zdaemon zdaemon: Wed Jan 30 13:02:03 2002: 
> Aiieee! 21875 exited with error code: 256

I don't know why your webserver might be crashing, but I do know that
'exited with error code: 256' usually means that the Zope process exited
normally with ERRORLEVEL 1, for instance, if it called sys.exit(1).

One of the places this happens is when you restart the Zope process thru
the Control_Panel.

-- 
Ideas don't stay in some minds very long because they don't like
solitary confinement.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )