Strange errors from logrotate daily: (98)

Virtualmin Professional is installed, latest version.

Dear all, I got the following email from my cron daemon:

date: Sun, May 11, 2008 at 6:25 AM
subject: Cron <root@poseidon> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

/etc/cron.daily/logrotate:
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver1.com/logs/access_log
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver1.com/logs/error_log
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver2.com/logs/access_log
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver2.com/logs/error_log
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver3.com/logs/access_log
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver3.com/logs/error_log
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver4.com/logs/access_log
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
httpd not running, trying to start
error: error running postrotate script for /home/virtualserver4.com/logs/error_log
run-parts: /etc/cron.daily/logrotate exited with return code 1

Does anyone have any idea what this is all about?
My apache server runs to port 80 on all IPs (at least now it does):
netstat -pan
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 2530/apache2

However the /var/log/apache/error.log file starts at exactly that time:
/var/log/apache2) $ cat error.log
[Sun May 11 06:25:09 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)

Also many log files start at this time:
syslog: May 11 06:25:09 poseidon syslogd 1.4.1#18: restart.
messages: May 11 06:47:01 poseidon syslogd 1.4.1#18: restart.

Also all .0 log files not zipped:
auth.log.0, dmesg.0 …

However nothing indicates a system reboot…

Could this be a breach…all help deeply appreciated…

P.S: Why logrotate (or is it something else ???) needs to bind to port 80?

Hmmm…it seems it is a known serious bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301702

Any ideas how to fix ???

and probably the solution:
from: http://www.heckofaworld.com/category/linux/

(it would be nice to have a patch from virtualmin, no?)

Apache2 - error running shared postrotate script

So something happened not too long ago such that in one of our Xen development environments (running Debian etch), apache was bailing every Sunday morning at a conspicuously consistent time.

This fairly obviously pointed to something going on inside of cron with the likely suspect being log rotation. Even more of a no-brainer given cronâ