Interesting, mine shows: And it is that way in all these files (most notably the httpd.conf.default file)

httpd.conf
httpd.conf.defaultserver
httpd.conf.10.2
httpd.conf.default

(the 10.2 one I created as backup when going to 10.3)

So I think it is supposed to be sites. Between that and the User/Group thing, I think your httpd.conf file has been changed somehow. You might like to try this: I have made some changes to mine, but if yours is supposed to be quite default, you should not see too many differences between these files.

quite a few differences:

Looking at that I would probably shut down apache and copy the default file over your current on and restart, do you know where that file came from?For a personal machine you probably don't need 5-10 serversHmm, I guess I would probably never get to 100000 requests on my home machine so this is probably moot.hfs should probably be in there, rendezvous probably does not matter.Yep, that should probably change.who is root @ edo ?? you?Yep, the reason you needed to create public_html...Should be there if the rendezvous module is.

Anyway, like I said, I would probably replace your httpd.conf with the default one.

That did the trick! I can now see my sites in Rendezvous too. I'm not sure how my Apache httpd.conf file got so screwed up??

Thanks for all your help!

Hello to all of you!

I am so thankful to have found a thread where a probable solution to my problem lies. For the past several hours ( and it's now 2 am), I have been patiently and carefully following all the instructions here.

By the way, I am using Mac OS ver 10.2.8 with Apache/1.3.29 and php-4.3.4 from enthrophy. My problem is almost identical to "jkinberg's", I am unable to start my Apache by:


1) going to the system preference and click the 'Personal Web Sharing' start button
- icon greyed
- Personal Web Sharing waiting to start (this does not happen before)

2) typing "sudo /usr/sbin/apachectl start" on the terminal
- gives "Syntax error on line 2 of /etc/httpd/httpd.conf:
Invalid command '.so', perhaps mis-spelled or defined by a module not included in the server configuration" /usr/sbin/apachectl start: httpd could not be started


Tried replacing the httpd.conf with the httpd.conf.default and got this:

"Syntax error on line 2 of /etc/httpd/httpd.conf:
Invalid command 'od_status.so', perhaps mis-spelled or defined by a module not included in the server configuration" /usr/sbin/apachectl start: httpd could not be started



Thanks in advance for you kind assistance.

Jose

So you are getting error messages about line 2 of http.conf
What does this line 2 look like? Show us.

One idea: maybe the http.conf file has somehow got its line endings screwed up (e.g. if you edited it and saved with Mac or DOS line endings). Try running this Perl invocation on it:

sudo perl -pi~ -e 's/\r\n?/\n/g' /etc/httpd/httpd.conf

hayne,

Thanks for your input here. I really appreciate it.

Well, lately I have been using dreamweaver mx to edit my httpd.conf file since my trial version of bbedit expired. I am not aware that this might mess up my file.

But running the perl command that you suggested asked me for a password and then back to the prompt without giving out any specific messages.

As for the line 2, below is a part of my httpd.conf file.

-----------------------

1##
2## httpd.conf -- Apache HTTP server configuration file
3##
4
5#
6# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://www.apache.org/docs/> for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# After this file is processed, the server will look for and process
# /usr/conf/srm.conf and then /usr/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#


--------------


I hope this would be some more enlightenment.

regards,

Jose

This is a followup post after another try.

When I try to type 'sudo /usr/sbin/httpd -t', I get this error message

*****
"Syntax error on line 379 of /etc/httpd/httpd.conf: Invalid command '<Directory>', perhaps mis-spelled or defined by a module not included in the server configuration"
******

And this what I have on my line 379 of my httpd.conf file

******
<Directory>
Options FollowSymLinks
AllowOverride None
</Directory>
*****

Thanks!

1) The Perl command I gave you is not supposed to give any output - it just silently fixes the line endings in yoru file to be the UNIX style (expected by Apache).

2) If you have been editing the httpd.conf file in Dreamweaver, I wouldn't be surprised if it has been corrupted somehow. It is not an HTML file and so Dreamweaver may have screwed it up.
You should get some other text editor to use in editing config files. One that is already on your system is 'pico' (execute this from the Terminal command line and follow the directions at the bottom).

You probably should get a fresh copy of the httpd.conf file from your OS X install CD or by downloading it from Apache. Test that Apache works with this fresh copy before changing anything. Then save a copy and never edit that copy so you always have something you can compare with later.

Hayne,

I patiently tried your suggestion of installting a fresh httpd.conf file from an apache package. And with that, I tried restarting my computer and starting apache from the terminal but, I still get just about the same result that looks like this.

"/usr/sbin/apachectl start
Syntax error on line 2 of /etc/httpd/httpd.conf:
Invalid command '.so', perhaps mis-spelled or defined by a module not included in the server configuration
/usr/sbin/apachectl start: httpd could not be started
"

Always, there is something wrong with the line 2. The only thing that change is the word after "Invalid command. Either it's 'so' , 'ners' or 'dModule' . And this is when I install a different httpd.conf file.

I really hope that this would help enlighten us where the problem is really coming from.

Thanks a gain Hayne.

can you post the results of:It really sounds like you have some problem with the line endings on your file and this will show what they are.

stetner,

fisrt of all thanks for your time in helping me out.

earlier today i tried reinstalling my apache from the install disk of my osx and at the same time i tried reinstalling php which i got from enthropy. and with a bit of luck, i was able to run my apache once again.

i tried running "od -c /etc/httpd/httpd.conf| head" and i got the same result as what you have posted.

but with this problem solve, i know that there is still more to learn about apache and php. anyway, thank you all for the guidance and patience.

jose

The same problem, but different symptoms...
 

I tried following some online instructions on upgrading to Apache 1.3.29 a few days ago, but ever since, Personal Web Sharing refuses to start from System Preferences; it just greys-out when I click 'Start'.

At the end of the installation, it said it had been successfully installed:

Here are some commands and their outputs, which may help:

Seeing as I installed it a few days ago, surely the timestamp should be a date in May?

You might want to check your /etc/httpd/httpd.conf file to see if the hfs module is named right in it. Mine says: I seem to recall a naming change with this module a few versions back, but from what you posted it did not look like that.

As well, what does Show? Oh yeah, this will show you the library symbols

There seems to be a considerable number of library symbols more than you:

Hi George, again we are seeing a difference between your files and mine, even though we are both on 10.3.3.

How did you get to 10.3.3? upgrade or clean install? Have you installed the latest patches from software update?

I get the feeling that we may find ourselves in the same situation as the sudo issue, where re-installing the files from the source may be the solution.

I think I clean installed on version 10.3.2, and I've been using software update on a regular basis, so all available updates are installed at the moment.

I've reinstalled, but I'm left with Apache version 1.3.28. Is there any recommended of installing the upgrade to 1.3.29?

Your help is valued.

Looking through my receipts under /Library/Receipts it appears that /usr/sbin/httpd was updated last in 10.3.3 and /usr/libexec/httpd/mod_hfs_apple.so came from my original 10.3 install.