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
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
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
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Sam Drinkard Sent: Sunday, July 23, 2006 12:21 PM To: CentOS mailing list Subject: Re: [CentOS] cron.weekly
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...
I think everyone that updated is getting this error in their logs. From what I've read, it's harmless.
Mike
On Sun, 2006-07-23 at 12:39 -0500, Mike Kercher wrote:
-----Original Message----- From: centos-bounces@centos.org
<snip> William L. Maltby wrote: > On Sun, 2006-07-23 at 09:47 -0400, Sam Drinkard wrote: > >><snip>
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?
<snip>
I think everyone that updated is getting this error in their logs. From what I've read, it's harmless.
JOOC: did they happen to mention the cause(ing package)? Any prognosis? Any work-around?
Its good to here it's harmless and I'm just nosy? :-)
Mike
<snip sig stuff>
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of William L. Maltby Sent: Sunday, July 23, 2006 12:52 PM To: CentOS General List Subject: RE: [CentOS] cron.weekly
On Sun, 2006-07-23 at 12:39 -0500, Mike Kercher wrote:
-----Original Message----- From: centos-bounces@centos.org
<snip> William L. Maltby wrote: > On Sun, 2006-07-23 at 09:47 -0400, Sam Drinkard wrote: > >><snip>
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?
<snip>
I think everyone that updated is getting this error in their logs. From what I've read, it's harmless.
JOOC: did they happen to mention the cause(ing package)? Any prognosis? Any work-around?
Its good to here it's harmless and I'm just nosy? :-)
Mike
<snip sig stuff>
-- Bill
http://bugs.centos.org/view.php?id=949
Mike
On Sun, 2006-07-23 at 13:19 -0500, Mike Kercher wrote:
-----Original Message----- From: centos-bounces@centos.org
<snip>
On Sun, 2006-07-23 at 12:39 -0500, Mike Kercher wrote:
<snip>
William L. Maltby wrote:
On Sun, 2006-07-23 at 09:47 -0400, Sam Drinkard wrote:
<snip>
I think everyone that updated is getting this error in their logs. From what I've read, it's harmless.
JOOC: did they happen to mention the cause(ing package)? Any prognosis? Any work-around?
Its good to here it's harmless and I'm just nosy? :-)
Mike <snip sig stuff><again>
Thx! That got me to a couple of solutions, and more importantly, the current status here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=170402
I'm trying to decide whether to try any of the workarounds or bide my time. Thinking, thinking... smoke ... flames... TG! Nascar!
Fugedaboudit!
Later.
Mike
<snip sig stuff>
William L. Maltby wrote:
On Sun, 2006-07-23 at 13:19 -0500, Mike Kercher wrote:
-----Original Message----- From: centos-bounces@centos.org
<snip>
On Sun, 2006-07-23 at 12:39 -0500, Mike Kercher wrote:
<snip>
William L. Maltby wrote:
On Sun, 2006-07-23 at 09:47 -0400, Sam Drinkard wrote:
<snip>
I think everyone that updated is getting this error in their logs. From what I've read, it's harmless.
JOOC: did they happen to mention the cause(ing package)? Any prognosis? Any work-around?
Its good to here it's harmless and I'm just nosy? :-)
Mike <snip sig stuff><again>
Thx! That got me to a couple of solutions, and more importantly, the current status here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=170402
I'm trying to decide whether to try any of the workarounds or bide my time. Thinking, thinking... smoke ... flames... TG! Nascar!
Fugedaboudit!
That's pretty much my sentiment too.. the bugs will get squished sooner or later!
-sam
Mike Kercher wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Sam Drinkard Sent: Sunday, July 23, 2006 12:21 PM To: CentOS mailing list Subject: Re: [CentOS] cron.weekly
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...
I think everyone that updated is getting this error in their logs. From what I've read, it's harmless.
Mike
If that's the case, I shan't worry about it. Let upstream fix the problem if they will. From the bug reports, it does not look like there is much concern about it..
-sam
On Sun, 2006-07-23 at 13:21 -0400, Sam Drinkard wrote:
William L. Maltby wrote:
On Sun, 2006-07-23 at 09:47 -0400, Sam Drinkard wrote:
<snip>
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.. <snip>
I hope I didn't mislead. That was for Jim, John, K etc. Normally if I hit a problem that I can't nail to my own foot (ouch!) I try and raise a flag. But I initially felt like I might have started this series problems of mine.
I seem to have backed out of them a bit (time will tell) by using my root fs backup as a "comparator" and adding *unsuspected* later things from the live system. Things stabilized at that point. Next cron-invoked prelink and/or yum update will probably enlighten me more though.
BTW, am running off the "backup" root fs created with my latest "semi- script" (semi=needs some coalescing and parameterization) and am about ready to put it into cron.
I gotta say, it is really neat doing backups while the production work (as if I really had any :-() kept on going. And cheap too! Commodity 100GB HDs about $40 after rebates. With some hdparm application for spin-down and up, should be pretty damn reliable.
As I promised in another thread, I will both post details about this (when ready) for other on-the-cheap users and try to test testdisk.
As stated in that post, slow going though.
thanks Bill...
-sam _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Mike Kercher -
Sam Drinkard -
William L. Maltby