The solution appears to be to wipe all syslog files, then reboot.
-- Joe Golden /_\ www.Triangul.us /_\ websites with class On 03/21/2012 12:07 AM, joe golden wrote:
Thanx Bill. I think it has something to do with the cloud and replicated server images. Can I blow away all syslogs and restart logging? Yup, I appear to be hosed. >> root@Ubuntu0003:/var/log# ls -l |grep sys -rw-r----- 1 root root 0 2012-03-20 02:12 syslog -rw-r----- 1 root root 29616 2012-03-20 02:12 syslog.1 -rw-r----- 1 root root 9586 2012-03-14 00:40 syslog.2.gz -rw-r----- 1 root root 7013 2012-03-09 19:02 syslog.3.gz -rw-r----- 1 root root 5627 2012-03-08 18:56 syslog.4.gz -rw-r----- 1 root root 25342 2012-03-07 19:02 syslog.5.gz root@Ubuntu0003:/var/log# logger Testing syslog root@Ubuntu0003:/var/log# ls -l |grep sys -rw-r----- 1 root root 0 2012-03-20 02:12 syslog -rw-r----- 1 root root 29616 2012-03-20 02:12 syslog.1 -rw-r----- 1 root root 9586 2012-03-14 00:40 syslog.2.gz -rw-r----- 1 root root 7013 2012-03-09 19:02 syslog.3.gz -rw-r----- 1 root root 5627 2012-03-08 18:56 syslog.4.gz -rw-r----- 1 root root 25342 2012-03-07 19:02 syslog.5.gz root@Ubuntu0003:/var/log#
