Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade
Neil Darlow wrote: Hi, Kris Kennaway wrote: Again, it's not bzip2 that is your underlying problem. I can't see what else it could be. I watched newsyslog kick-in at 11:00UTC to rotate logs and that's what happened. There was no esoteric hardware access, e.g. writing to DVD, happening at the time so I'm at a loss to explain what's happening. Did you track down the cause of your interrupt storm? Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade
Hi, Kris Kennaway wrote: Again, it's not bzip2 that is your underlying problem. I can't see what else it could be. I watched newsyslog kick-in at 11:00UTC to rotate logs and that's what happened. There was no esoteric hardware access, e.g. writing to DVD, happening at the time so I'm at a loss to explain what's happening. Regards, Neil Darlow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade
Neil Darlow wrote: Hi, I've caught bzip2 misbehaving. The following "top" output is for compression of /var/log/messages (just over 100kB size) and it's not finished yet: 21172 root 1 1180 11360K 8248K RUN 11:02 100.00% bzip2 Over 11 minutes, and still going, at 100% CPU. Now that's definitely not right. Anyone else seeing this? Again, it's not bzip2 that is your underlying problem. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade
Hi, I've caught bzip2 misbehaving. The following "top" output is for compression of /var/log/messages (just over 100kB size) and it's not finished yet: 21172 root 1 1180 11360K 8248K RUN 11:02 100.00% bzip2 Over 11 minutes, and still going, at 100% CPU. Now that's definitely not right. Anyone else seeing this? Regards, Neil Darlow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade
On Thursday 06 March 2008 13:14:02 Neil Darlow wrote: > I've rebooted the system and watched cron execute newsyslog to rotate > the logs. I have a bzip2 process that's consuming over 90% of CPU. That > can't be normal? It's normal. It's not normal if the files don't get compressed. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade
Hi, Kris Kennaway wrote: This should be unrelated to bzip since that is purely CPU bound. What is causing the interrupts? Check vmstat -i. That is likely to be your real problem. The cause of the high interrupt incidence was failed DMA operations on my DVD-RW drive. The situation arose as follows: 1) My backup program executes at 11:30 UTC and uses growisofs to create a DVD on-the-fly. 2) newsyslog executes at 00:00 UTC and compresses the logfiles with bzip2. 3) The DVD-RW drive DMA errors appear. I've rebooted the system and watched cron execute newsyslog to rotate the logs. I have a bzip2 process that's consuming over 90% of CPU. That can't be normal? Regards, Neil Darlow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd and bzip2 hogs after 6.3 to 7.0 upgrade
Neil Darlow wrote: Hi, I have recently upgraded from RELENG_6_3 to RELENG_7_0 via the source method. I followed the upgrade instructions in the 7.0 release notes and rebuilt all ports successfully. My hardware is a VIA EPIA PD1 (VIA Centerhauls CPU) with gmirrored IDE disks and GELI encrypted swap (using padlock). My kernel is GENERIC with removal of 386, 486 and 585 CPU support and addition of options for: DEVICE_POLLING, HZ=1000, ALTQ, PFLOG, PFSYNC and QUOTA. I use PF for my firewalling and device polling on my two integrated Via Rhine NICs. This setup worked great under RELENG_6_2 and RELENG_6_3 (only for a short period due to RELENG_7_0 becoming available) with absolutely no issues whatever. Since upgrading to RELENG_7_0 I have a problem when the nightly rotation of logfiles occurs. A number of bzip2 processes appear which, with syslogd, consume huge amounts of CPU. FreeBSD 7 switches to bzipping logfiles rather than gzipping. Looking at the output of "top" I see that my interrupt CPU usage has increased to 46% and userland CPU usage to 44%. The remainder is system and there is no idle CPU time left. This should be unrelated to bzip since that is purely CPU bound. What is causing the interrupts? Check vmstat -i. That is likely to be your real problem. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
