|
Home > Archive > Web Servers on Unix and Linux > May 2004 > Apache Server migration
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Apache Server migration
|
|
| Adam Smith 2004-05-11, 8:23 pm |
| I've upgraded my servers and currently migrating my files. FreeBSD O/S I
had customized, compiled and configured my apache 1.3.29, several
modules, ssl, vhosts etc. Now the install place files in several
locations, uses shared libraries etc. My ISP provides a default Apache,
which I'll be discarding.
The Question is how can I figure out what files are needed & from where
The files ported so far ==>
machine-1# apachectl configtest
Syntax OK
BUT ==> both
machine-1# apachectl startssl
/usr/local/sbin/apachectl startssl: httpd could not be started
and
machine-1# apachectl start
/usr/local/sbin/apachectl start: httpd could not be started
There are no entries in the /var/log/httpd-error.log file or for that
matter the /var/log/httpd-access.log file. I could not figure out a
debugging type routine to locate the problem
Hope someone as an idea of how to undo this SNAFU
Thanks
-- Adam --
Pl. reply to POST
| |
| David Efflandt 2004-05-11, 8:23 pm |
| On Sun, 09 May 2004 10:09:07 -0700, Adam Smith <adamsmith@econ.com> wrote:
> I've upgraded my servers and currently migrating my files. FreeBSD O/S I
> had customized, compiled and configured my apache 1.3.29, several
> modules, ssl, vhosts etc. Now the install place files in several
> locations, uses shared libraries etc. My ISP provides a default Apache,
> which I'll be discarding.
>
> The Question is how can I figure out what files are needed & from where
>
> The files ported so far ==>
> machine-1# apachectl configtest
> Syntax OK
>
> BUT ==> both
> machine-1# apachectl startssl
> /usr/local/sbin/apachectl startssl: httpd could not be started
>
> and
>
> machine-1# apachectl start
> /usr/local/sbin/apachectl start: httpd could not be started
>
> There are no entries in the /var/log/httpd-error.log file or for that
> matter the /var/log/httpd-access.log file. I could not figure out a
> debugging type routine to locate the problem
>
> Hope someone as an idea of how to undo this SNAFU
The first question is, do you own the whole box (colocation), or are you
just a virtual host with their default apache configured to run chroot in
your home dir (from inetd)? If the latter, there may be a 'virtual'
command which can be used as a commandline prefix in the shell to
configure/compile programs to run in your chroot jail. I help someone on
a FreeBSD server like that where the user has their own apache and
sendmail config, but those run chroot in their home dir.
That may explain why no logs (no such path under chroot).
--
David Efflandt - All spam ignored http://www.de-srv.com/
| |
| Adam Smith 2004-05-11, 8:23 pm |
| Hi David,
I am now in a dedicated server, not constrained my "a jail". The absence
of the error msg in the log file is due, I think, to httpd not even
getting started. The failure, I think starts before, and there is no
debugger to step through to the point of failure, or is there?.
David Efflandt wrote:
> On Sun, 09 May 2004 10:09:07 -0700, Adam Smith <adamsmith@econ.com> wrote:
>
>
>
> The first question is, do you own the whole box (colocation), or are you
> just a virtual host with their default apache configured to run chroot in
> your home dir (from inetd)? If the latter, there may be a 'virtual'
> command which can be used as a commandline prefix in the shell to
> configure/compile programs to run in your chroot jail. I help someone on
> a FreeBSD server like that where the user has their own apache and
> sendmail config, but those run chroot in their home dir.
>
> That may explain why no logs (no such path under chroot).
>
|
|
|
|
|