Re: Testing upgrade and consequences
On Tue, Mar 13, 2001 at 03:41:42PM -0600, Chad C. Walstrom wrote:
> Redirecting further discussion of this user-based problem to
> debian-user...
I don't believe it is a user-based problem. It's not the first
post saying "perl upgrade broke my apache" -- unless I'm getting
e-mail from a parallel universe. I'm not complaining about it either
-- I know what "unstable" means. I repeat, I fup'ed because IMNSHO
when you see several messages saying "perl upgrade broke my apache",
you (no, not you personally) shouldn't answer with
"apache in woody is the same version as apache in stable hence
[it works fine|it's a luser-based problem|don't bother reporting it]".
Follow-ups set as requested, anyway.
>
> On Tue, Mar 13, 2001 at 02:29:02PM -0600, Dimitri Maziuk wrote:
... Apache failed to start up after that (did you try
> > to restart your apache lately? maybe you shouldn't.)
>
> So... It was working fine, your installation of the "broken" woody
> Apache, until your box made a "funny noise"...
Sometimes I wonder if I should enroll into an English course.
It was working fine, my installation of "working" woody Apache, until
I had to reboot the box. Quite a few packages got updated during its
(the box's) uptime so I cannot say "I've upgraded this particular package
to this particular version on this particular date and Apache crashed right
after that".
> This doesn't hint to a
> larger problem at all, does it? Perhaps you should run fsck.ext2 on
> your system's ext2 filesystems and make sure everything is clean and
> tidy.
Obviously, if I had a fsck'ed up hard drive I wouldn't be blaming apache
problems on a woody upgrade. Well, ok, not obviously. Maybe I should
start with "... I first installed Debian in -- hmm, what was it, 1994,
1996? -- anyway, around the time of version 1.0. Those were the days..."
> Has it occured to you to back up your custom config files in your home
> directory, purge the Apache installation, and reinstall? I would not
> normally suggest this, as it ignores possible bugs, BUT what you
> described above makes it sound like you've got some serious hardware
> issues to deal with -- one of them being possible file corruption.
No I don't have a serious hardware problem and the filesystem is clean.
No I don't have custom config files for apache -- except for my e-mail
address everything is as set up by dpkg.
I only use apache for dwww and while not having dwww on a local box is
annoying, it's not a good enough reason to dig out previous set of tapes,
reload the silo, rebuild browse indexes and restore /etc/apache/*.conf
that I never really changed in the first place (I'm talking Legato and
tape jukeboxes in case you're wondering).
> Also, has it occurred to you to actually edit your configuration files
> by hand?
Yes. Here's what I get with correct conffiles (BTW, why are there 3 of
them? I thought everyone's switched to single httpd.conf by now).
odyssey:/usr/sbin# ./apachectl start
./apachectl start: httpd started
odyssey:/usr/sbin# ./apachectl stop
./apachectl stop: httpd (pid 19342?) not running
Log:
---
[Tue Mar 13 16:59:17 2001] [warn] pid file /var/run/apache.pid overwritten
-- Unclean shutdown of previous Apache run?
Apache.pm failed to load!.
I think I'll wait for new versions of perl packages before purge/reinstalling.
Dima
--
E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home)
I'm going to exit now since you don't want me to replace the printcap. If you
change your mind later, run
-- magicfilter config script
Reply to: