Re: [Zope] configurating Zopes for merged logs
Exactly what I was planning to do. The docs themselves indicate they are incomplete. Is there any documentation beyond that supplied with the distribution. (I have read the "logging" docs and PEP 282.) Not sure what you *need* in terms of documentation. There are only a couple parameters, like logging host and log facility, to specify. Why don't you just try it out and see what happens? Python 2.4.1 seems to be clean and stable with Zope 2.7.6. We've been running it in production for a while with no problems attributable to it. My understanding is that the only reason it is "unsupported" is that a security audit has not been done on the changes from Python 2.3.5. "Seems clean and stable" wouldn't be a good-enough reason for me to put production servers on an unsupported combination of software. But that's everyone's personal choice. jens ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] configurating Zopes for merged logs
Exactly what I was planning to do. The docs themselves indicate they are incomplete. Is there any documentation beyond that supplied with the distribution. (I have read the "logging" docs and PEP 282.) Python 2.4.1 seems to be clean and stable with Zope 2.7.6. We've been running it in production for a while with no problems attributable to it. My understanding is that the only reason it is "unsupported" is that a security audit has not been done on the changes from Python 2.3.5. On Mon, 1 Aug 2005, Jens Vagelpohl wrote: > > Zope 2.7.6 with ZEO > > Python 2.4.1 > > > > I would like to configure for a single merged log. If BE is the > > backend > > machine running ZEO and FEA FEB and FEC are various front-ends for the > > ZEO, what's the configuration supposed to look like to get a merged > > log > > collected on the machine on which ZEO runs. The only log I need > > to merge > > is the Z2.log--the othes can be left per-Zope frontend. While it > > would be > > nice if the merged entries were serialized, it is not strictly > > necessary. > > Cross machine transmission can be either UDP or TCP. > > Apart from the fact that Python 2.4.1 is unsupported on Zope 2.7.6, > have you looked at the logger section in zope.conf? You can configure > a syslog loghandler for any log and send the logging output to a > syslog server. See zope.conf and /lib/python/zLOG/component.xml > for the configuration knobs. > > jens > > ___ > Zope maillist - Zope@zope.org > http://mail.zope.org/mailman/listinfo/zope > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope-dev ) > -- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] configurating Zopes for merged logs
Yup, that is one of my fallback approachs. It seems to me that I should be able to write a configuration for the Zopes that either invokes a remote syslogd server (or other server) which will merge multiple logging entries into a single file on one of the machines in the cluster, preferably the ZEO host. Another approaches would be to maintain local logs and then have a process running on the remote machine that performs the merge. We post-process the logs in nearly real-time and we expect related transactions to spread across multiple Zopes. On Mon, 1 Aug 2005, Andreas Jung wrote: > > > --On 1. August 2005 09:51:37 -0700 Dennis Allison > <[EMAIL PROTECTED]> wrote: > > > > > Zope 2.7.6 with ZEO > > Python 2.4.1 > > > > I would like to configure for a single merged log. If BE is the backend > > machine running ZEO and FEA FEB and FEC are various front-ends for the > > ZEO, what's the configuration supposed to look like to get a merged log > > collected on the machine on which ZEO runs. The only log I need to merge > > is the Z2.log--the othes can be left per-Zope frontend. While it would > > be nice if the merged entries were serialized, it is not strictly > > necessary. Cross machine transmission can be either UDP or TCP. > > I don't know what the sense of a merged Z2.log is. You can install a > front-end proxy + load balancer so you could use the logfile of the proxy > or write a small script to merge the the Z2.log from multiple clients into > a single file. You should be straight forward with some line of Python. > > -aj -- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] configurating Zopes for merged logs
Zope 2.7.6 with ZEO Python 2.4.1 I would like to configure for a single merged log. If BE is the backend machine running ZEO and FEA FEB and FEC are various front-ends for the ZEO, what's the configuration supposed to look like to get a merged log collected on the machine on which ZEO runs. The only log I need to merge is the Z2.log--the othes can be left per-Zope frontend. While it would be nice if the merged entries were serialized, it is not strictly necessary. Cross machine transmission can be either UDP or TCP. Apart from the fact that Python 2.4.1 is unsupported on Zope 2.7.6, have you looked at the logger section in zope.conf? You can configure a syslog loghandler for any log and send the logging output to a syslog server. See zope.conf and /lib/python/zLOG/component.xml for the configuration knobs. jens ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] configurating Zopes for merged logs
--On 1. August 2005 09:51:37 -0700 Dennis Allison <[EMAIL PROTECTED]> wrote: Zope 2.7.6 with ZEO Python 2.4.1 I would like to configure for a single merged log. If BE is the backend machine running ZEO and FEA FEB and FEC are various front-ends for the ZEO, what's the configuration supposed to look like to get a merged log collected on the machine on which ZEO runs. The only log I need to merge is the Z2.log--the othes can be left per-Zope frontend. While it would be nice if the merged entries were serialized, it is not strictly necessary. Cross machine transmission can be either UDP or TCP. I don't know what the sense of a merged Z2.log is. You can install a front-end proxy + load balancer so you could use the logfile of the proxy or write a small script to merge the the Z2.log from multiple clients into a single file. You should be straight forward with some line of Python. -aj pgpe3aHYeyZW8.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] configurating Zopes for merged logs
Zope 2.7.6 with ZEO Python 2.4.1 I would like to configure for a single merged log. If BE is the backend machine running ZEO and FEA FEB and FEC are various front-ends for the ZEO, what's the configuration supposed to look like to get a merged log collected on the machine on which ZEO runs. The only log I need to merge is the Z2.log--the othes can be left per-Zope frontend. While it would be nice if the merged entries were serialized, it is not strictly necessary. Cross machine transmission can be either UDP or TCP. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
