FCGIServer.py broken again?
hi, i just wanted to set up a zope server on another machine: - apache on port 80 + mod_fastcgi-snapshot - zope 2.1.1 using fcgi via socket i'm running the very same config on another machine without any problems but here i get tracebacks after the first request for a zope page: -------------------------------------------------- Traceback (innermost last): File "/usr/local/lib/Zope-2.1.1-src/z2.py", line 583, in ? asyncore.loop() File "/usr/local/lib/Zope-2.1.1-src/ZServer/medusa/asyncore.py", line 107, in loop poll_fun (timeout) File "/usr/local/lib/Zope-2.1.1-src/ZServer/medusa/asyncore.py", line 66, in poll x.handle_error() File "/usr/local/lib/Zope-2.1.1-src/ZServer/medusa/asyncore.py", line 321, in handle_error self.close() File "/usr/local/lib/zope/ZServer/FCGIServer.py", line 573, in close p.more() # free up resources held by producer File "/usr/local/lib/Zope-2.1.1-src/ZServer/Producers.py", line 108, in more getattr(self.logger, self.method)(self.bytes) File "/usr/local/lib/zope/ZServer/FCGIServer.py", line 496, in log_request time.gmtime(time.time()) TypeError: illegal argument type for built-in operation -------------------------------------------------- the code that seems to be causing the traceback is this: self.server.logger.log ( self.addr[0], '%d - - [%s] "%s %s" %d' % ( self.addr[1], time.strftime ( '%d/%b/%Y:%H:%M:%S ', time.gmtime(time.time()) ) + tz_for_log, method, path, bytes ) ) when i replace the %d for self.addr[1] to %s it seems to work but then the logging looks ugly... anybody with the same problem or maybe even a solution...?! the strange thing is that the same config is working on another machine so i guess maybe some external influence (apache, proxy) is causing the problem... thilo -- mezger@innominate.de innominate AG networking people fon: +49.30.308806-11 fax: -77 web: http://innominate.de pgp: /pgp/tm
participants (1)
-
news-list.zope.dev@innominate.de