[sharp-discuss] apache2 not starting on Ubuntu 7.04 SHARP installation
Lee S Parsons
parsonsl at upstate.edu
Fri Aug 15 16:43:29 CEST 2008
Clemens Vonrhein wrote:
> Dear Lee,
>
> On Thu, Aug 14, 2008 at 12:33:08PM -0400, Lee S Parsons wrote:
>
>
> I see. the problem then is probably that the email that should have
> been sent out by this 'newuser' command didn't get to them? Often,
> email isn't setup on the machine you're running SHARP/autoSHARP. But
> the email is actually also saved in
>
>
Actually, that wasn't the problem, either. The email did go out (I made
myself an account to make sure that it worked). It simply wouldn't
allow the new user to log in - only the user I made at installation was
allowed in.
Though I'm not worried about this problem right now, since the web
server is completely non-functional from the perspective of SHARP, anyways.
>
>> As mentioned, restart_server (sorry about the earlier typo) dies
>> immediately with the "AuthUserFile" error that I mentioned earlier. Still
>> trying to figure out how to get around that one...
>>
>
> It's all related to you using a 2.X version of the Apache httpd
> distributed by the OS supplier (I'm prettu sure about that).
>
>
I'm willing to concede that the "AuthUserFile" problem is indeed an
apache installation problem and not your problem. I will continue with
a two-pronged approach to see if I can get either version of apache to
work correctly for sharp.
>
> This might have been unclear: we do supply a pre-compield Apache 1.3.X
> httpd binary that _should_ work out of the box (and running
> 'installSHARP -F' will automatically try using it). If it doesn't work
> right away, then the recommendation is to install a fresh 1.3.X
> version according to the README file mentioned.
>
>
I'll try building 1.3.x and see if that makes my life any better.
>
>> I just tried starting the 1.3.34 that came with SHARP - I extracted the
>> contents of the tarball into /usr/local/Helpers-server/ (notice the
>> intentional capitalization).
>>
>
> You should install it into $BDG_home too as part of the 'installSHARP
> -F'. You can in principle install it into a different directory, but
> that is just making your life difficult I guess.
>
>
>> I then tried
>>
>> /usr/local/Helpers-server/httpd -f
>> /usr/local/SHARP/sushi/conf/httpd-1.3.conf
>>
>> And the response was a core dump.
>>
>
> Yes.
>
>
Perhaps I missed something critical in the httpd.conf file, but my
understanding is that you can have apache residing anywhere on your
system, and then use an httpd.conf file from anywhere else on your
system, as long as you use the -f switch to specify the file.
I intentionally used a different directory name, because after the
installation of sharp, there was no "helpers-server" directory under
/usr/local/SHARP.
>> I've tried them, and found that:
>> ( .RedHat-FC3, .glibc23, .SuSE-9.1, .SuSE-9.3) return an error on not being
>> able to resolve the FQDN, and then promptly die without leaving any
>> messages
>>
>
> If you want to test different httpd binaries you need to do this
> through the 'httpd-setup' admin tool. So running the sequence
>
> % adm/bin/kill_server # just in case
> % adm/bin/httpd-setup # and pick the httpd and conf file you want
> # to use
> % adm/bin/restart_server
> % adm/bin/check_server
> % ps -efl | egrep "httpd|apache2" # just in case
>
> will show you if the combination of httpd binary and configuration
> file is working.
>
>
I might be missing something here. If Apache won't start from the
command line, why would it start from a script? I understand that I
need the adm/bin commands for starting it for sharp, but I guess I don't
see why it would work for sharp if it won't work without it.
>
>> When I opened the tarball "helpers_server.linux.tar.gz", there was no file
>> "apache_1.3.34.tar.gz" as suggested by httpd.README_GPhL. Should I
>> download that version directly from the Apache group and build it myself?
>>
>
> Yes - and you can download the latest from the 1.3.X series.
>
> This option is by far the safest for getting everything to work!
>
>
We will begin on that and see if it makes life any better.
>>>
>>>
>> As much as I didn't think I'd be saying this, we aren't really much at all
>> concerned about security on this system. You are correct that it is behind
>> a firewall, running as a non-root account. Apache2 was built just because
>> this system had no webserver on it prior, so it seemed logical at the time
>> to build the newest version. We certainly didn't expect to walk into this
>> mess with the Apache2 config files, or we would have built the older
>> version instead.
>>
>
> I agree: we need to find the time to move the system to the latest 2.X
> series of Apache ... touche ;-)
>
>
Perhaps I'll get lucky and finish my PhD before you complete the move to
Apache 2.x, so someone else here can work on that transition for our
installation...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.globalphasing.com/pipermail/sharp-discuss/attachments/20080815/1f0c15d8/attachment.htm
More information about the sharp-discuss
mailing list