-----Original Message-----
From: Ken Dunnington [mailto:[EMAIL PROTECTED]
Sent: 09 January 2004 20:48
To: CF-Linux
Subject: Re: CF Unstable, fails (randomly) nightly?
Well, I reinstalled this morning. No problems, everything went great,
no problems at all today - until 2:57pm when CF stopped responding,
prompting a service restart. Since I was right there when it happened,
I was able to figure the time very closely, and thus was able to scan
the logs with some precision. But there was nothing in them. This is
crazy, I can't run a web server like this.
Can anyone suggest a script that will check if the server is
responding, and restart CF if it isn't? At least that would avoid
scheduled reboots and could help diagnosing.
On Jan 6, 2004, at 2:25 PM, Ken Dunnington wrote:
> No problem, I appreciate any input whatsoever :)
>
> I tried reverting to 1.3.27-3, the previous build, but the problem
> persisted. I'm not sure what was changed, as it was an RPM upgrade. The
> security issue was a relatively minor one, in which an attacker could
> execute arbitrary code using .htaccess files, which isn't something I'm
> worried about on my server. I'm actually led to believe, by what I've
> read about CF and Apache, that it was all a coincidence. There is also
> an issue with openSSL that I've read about, but it's only slightly
> related to my problems here.
>
> I'm moving my biggest client to a different box, and then am going to
> reinstall CF, and probably go back to Apache 1.3.27-3. I haven't
> reinstalled CF in a long time, so I can't remember if it resets all my
> datasources/preferences or not, but I have a feeling it does.
>
> Ah, the joys of server administration. :)
>
> On Jan 6, 2004, at 1:23 PM, Dave Carabetta wrote:
>
> > >Unfortunately, Plesk, our admin software, only supports Apache 2 on
> > Red
> > >Hat 9, and since RH is dropping regular Linux, we aren't going to go
> > >that route. They also don't support Enterprise 3 yet, which is based
> > on
> > >RH 9. So we're stuck with Enterprise 2.1 (based on 7.3) until then.
> > >I've heard that 2.0 is more stable, and I might try and kludge it
> if I
> > >can't find any other solution.
> > >
> >
> > Fair enough. Out of curiosity, have you looked in to the specific
> > changes
> > between your previous version of Apache 1.3 vs. the new patch you
> > applied?
> > Perhaps you could get narrow down what has changed and how it might
> > have
> > effected your installation. If that's too cumbersome, couldn't you
> just
> > revert to your previous install? Was their something specific in the
> > latest
> > patch that you needed that provoked the upgrade?
> >
> > Sorry I'm not directly answering your question. But I don't have
> enough
> > experience with the latest 1.3.x build to speak to its stability or
> any
> > potential complications.
> >
> > Regards,
> > Dave.
> >
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
