Your message dated Tue, 18 Nov 2008 20:50:02 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Closing old zope bugs
has caused the Debian Bug report #397421,
regarding zope: logrotate doesn't handle the absence of logs correctly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
397421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397421
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: zope
Version: 2.6.4-1.8
Severity: normal
/etc/logrotate.d/zope correctly specifies "missingok", but as the
postrotate script (zopectl logrotate) is run unconditionally and
as zopectl chokes on performing a logrotate for instances that
are not running at the time, useless emails about zope brokenness
/etc/cron.daily/logrotate:
error: error running shared postrotate script for /var/log/zope/*/*.log
run-parts: /etc/cron.daily/logrotate exited with return code 1
appear weekly. Whether the postrotate script should make itself
consistent with the presence of the missingok diretcive (i.e.
only call zopectl if there were in fact log files to rotate) or,
more robustly, whether zopectl should deal gracefully with
log rotation requests for non-running instances (i.e. silently
and successfully do nothing) is an open question, but the current
behaviour is a little broken.
(I'd suggest the latter approach as the problem is with an
instance being down at the time of rotation regardless of how
long it's been down for, rather than that it's been down for
an entire calendar week; the solution should test for whether an
instance is running, which is zopectl's domain.)
- Raz
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.18-1-686
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Versions of packages zope depends on:
ii adduser 3.63 Add and remove users and groups
ii debconf 1.4.30.13 Debian configuration management sy
ii dpkg 1.10.28 Package maintenance system for Deb
ii libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii python2.2 2.2.3dfsg-2sarge1 An interactive high-level object-o
ii python2.2-xml 0.8.4-1 XML tools for Python (2.2.x)
ii zopectl 0.3.4.3 Zope instances controlling utility
-- debconf information:
zope/instance_home/move: true
* shared/zope/restart: end
zope/upgrade/2.6.1-7:
* zope/admin-user: admin
--- End Message ---
--- Begin Message ---
Hello,
I'm closing this bug report because it refers to the old zope (2.6) package
and the current zope in testing/unstable (2.10) doesn't show this problem.
--
Fabio Tranchitella http://www.kobold.it
Free Software Developer and Consultant http://www.tranchitella.it
_____________________________________________________________________
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
--- End Message ---
