Just looked at the log from the x86_64 machine and I see the same zcat: stdout: Broken pipe in the 00-makewhatis.cron job as on the x86 machine. Did I miss some thread about current updates somewhere? sam -- Sam W.Drinkard -- sam at wa4phy.net NOAA Cooperative Observer http://wa4phy.net Augusta Area Mesonet
On Sun, 2006-07-23 at 09:47 -0400, Sam Drinkard wrote:> Just looked at the log from the x86_64 machine and I see the same zcat: > stdout: Broken pipe in the 00-makewhatis.cron job as on the x86 > machine. Did I miss some thread about current updates somewhere?If so, I missed it too! I am 100% current (based on current knowledge). Other than the prob you mention, I have also seen messages from glibc.common regarding double releases. Saw some in dmesg and some while in X. Some apps have been locking, never completing startup, crashing, etc. B4 proj guys holler about reporting, I've been completing a more standard b/u procedure using my el-cheapo LVM-based stuff and that took priority once I saw the symptoms. My needs came first.> > sam >-- Bill -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20060723/bc9e9af6/attachment-0001.sig>
William L. Maltby wrote:> On Sun, 2006-07-23 at 09:47 -0400, Sam Drinkard wrote: > >> Just looked at the log from the x86_64 machine and I see the same zcat: >> stdout: Broken pipe in the 00-makewhatis.cron job as on the x86 >> machine. Did I miss some thread about current updates somewhere? >> > > If so, I missed it too! I am 100% current (based on current knowledge). > Other than the prob you mention, I have also seen messages from > glibc.common regarding double releases. Saw some in dmesg and some while > in X. Some apps have been locking, never completing startup, crashing, > etc. > > B4 proj guys holler about reporting, I've been completing a more > standard b/u procedure using my el-cheapo LVM-based stuff and that took > priority once I saw the symptoms. > > My needs came first. >It's very possible I missed anything about the problem, as I don't read everything.. I scan what I think might apply to me sometime. I did miss the clamav thread back awhile, and after reading it, realized it was a repo problem. I don't update very often, and never have had any issues with anything. There is a lot I don't quite understand about how the update processes are *supposed* to work, but again, it's always done just fine, no problems. I'm getting lazy in my old age and don't want too many things going bump in the night.. If it works, I don't try to fix it either. Might not be the best policy, but where I have things that *must* run, I tend not to do dumb things and shoot myself in the big toe :-) thanks Bill... -sam
This has been an ongoing issue. I have had this problem before. From what I can recall. Usually after a fresh install, the first cron.weekly to run, this error will show up...Which then each following cron.weekly will not have this error...And also, same as if there is a update to the system...Sometimes during a yum update, no particular one, the cron.weekly error will ocurr. Like i said this has been ongoing, and i recognize this error from years back. I believe it to be harmless and i really wouldnt worry about as I dont.