Thank you for your response and any help you can give. You undoubtedly
saw my later post with a different subject of "after upgrade backups
cause machine crash" which had some additional information but no
respondents.
I am not altogether convinced it is a kernel problem entirely as I
cannot go back to the old kernel and do the backups as I once did before
the upgrade. If I wanted to get a newer kernel I presume I could
include testing in my sources.list and install the latest kernel-image
from there. That would make the machine even more 'mixed', however.
Some other issues with this machine that may or may not be related. In
kern.log, I occassionally get messages like:
kernel: BUG: dst underflow 0: f5c09580 at f8dd7c57
kernel: BUG: dst underflow 0: f5f74e80 at c022fc29
surrounded by:
kernel: icmpv6_send: addr_any/mcast source
I haven't found much googling to indicated what that is about
Last week the kernel logger stopped logging to syslog and related files
even though the daemon was still in 'ps' output. Restarting the daemon
seemed to have corrected that.
I am wondering if something needed in the upgraded packages was assumed
to be in place and wasn't or that the older packages that weren't
upgraded now don't have something needed from the newer packages. Why
doesn't the pre-update kernel work for backups as it once did?
I have fsck'd the filesystem and found nothing amiss.
I really don't know what to try next. Any help would be appreciated.
Karen
Kevin Mark wrote:
On Mon, Feb 20, 2006 at 05:39:11PM -0600, Karen Larson wrote:
Thank you for your reply. Let me clarify a bit.
I know I should not put testing on a production server, but testing at
that point (January a year ago) was almost the stable sarge and I took a
chance. Woody was just too old. I didn't think of using dist-upgrade
as I was going from the old testing-sarge to stable-sarge. All the
security updates that I did over the last year were done with just the
security update line in sources.list.
In January this year, I replaced the commented out testing lines from
the original install with uncommented sarge lines in sources.list, left
the security one, did an aptitude update followed by an aptitude
upgrade. I then installed the 2.6.8-2-686-smp kernel from
stable-Sarge. That one as well as the original testing-sarge one
(2.6.8-1-686-smp)are both crashing when doing the backups.
Any other ideas?
Karen
Hi Karen,
your first reply was written in the third person, so I was not sure if
you were the one familar with the server but with your last reply, I see
you are the one who did the update. My only guess is that it is a kernel
issue and you may want to get a more recent kernel. Since you are
running a 2.6 kernel, you may benefit from the recent changes. I'm not
sure about doing this as I run 'unstable' on my desktop and my laptop
which has sarge does not have a 'tape' drive. So maybe someone else on
the list could point you to updating to a recent kernel with a sarge
system. I'd also suggest going on #debian on irc.freenode.net as they
have some good folks who may know even more useful stuff and you get
faster replys.
Cheers,
Kev
--
Karen Larson UW - Parkside 262-595-2450
System Administrator 900 Wood Road [EMAIL PROTECTED]
Computer Science Dept Kenosha, WI 53141-2000
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
