Re: help me

"zhaohongjie" <zhao.hongjie-sCcLdqTp3/[email protected]>
Newsgroups gmane.comp.web.zope.chinese
Message-ID <001001c494b5$98762ed0$2865a8c0@zhaohongjie>
谢谢,以下是日志信息:
2004-09-07T14:45:54 INFO(0) ZODB conflict error at /dotcom/c/stock/superfind (1 conflicts since startup at 2004-09-07T14:45:15) 

2004-09-07T14:31:52 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 192.168.101.40:3054 at 0x11b73878 channel#: 8818 requests:> (socket.error:(10054, 'Connection reset by peer') [C:\Program Files\Zope-2.7.0\bin\Lib\asynchat.py|initiate_send|218] [C:\Program Files\Zope-2.7.0\lib\python\ZServer\medusa\http_server.py|send|417] [C:\Program Files\Zope-2.7.0\bin\Lib\asyncore.py|send|337])

但这些错误都不会导致zope崩溃,现在崩溃的原因根本每法找到,还要请教:
zope日志是不是event.log,Z2.log?还是有其他的?
另外,windows的操作日志里也没有错误记录。
还有一个特点就是,其他用户没有反映这个错误,而且我的同事频繁的访问同一个站点也不会造成它崩溃,只有我自己一台计算机会造成它崩溃

----- Original Message ----- 
From: "March Liu" <[email protected]>
To: <[email protected]>
Sent: Tuesday, September 07, 2004 2:22 PM
Subject: Re: [zope-chinese] help me


> 可以给出详细的出错信息、出错条件吗?比如出错时系统的应用程序日志有没有记录?有没有什么准确的规律?试试将Zope改为命令行模式运行,看看有没有更详细的出错纪录?
> 
> On Tue, 7 Sep 2004 13:15:51 +0800, zhaohongjie <[email protected]> wrote:
> > 
> >  
> > 各位好:
> >  
> >      在使用zope2.7时候,会出现服务器崩溃的现象,不知是何原因,请赐教
> >  
> >      我的环境是windows 2000 数据库是sql server,数据连接方式是odbc
> > 
> > _______________________________________________
> > zope-chinese list
> > [email protected]
> > http://zope.cn/mailman/listinfo/zope-chinese
> > 
> > 
> > 
> 
> 
> 
> -- 
> 刘鑫
> March.Liu
> 


--------------------------------------------------------------------------------


> _______________________________________________
> zope-chinese list
> [email protected]
> http://zope.cn/mailman/listinfo/zope-chinese
>

_______________________________________________
zope-chinese list
[email protected]
http://zope.cn/mailman/listinfo/zope-chinese
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.