Problems with basic configuration and config file issues

1. I've been starting the httpsd daemon and port 443 just won't turn on. Now I dont yet have a certificate, but I should be able to get to the default splash page on port 443 right?

You'll at least need a test certificate before the SSL part of the server will start properly. See the instructions in your manual and in this FAQ under the SSL section.

2. This server just won't run and I can't figure out why... what I should I do first to try and troubleshoot the problem?

Apache tries to be helpful when it encounters a problem. In many cases, it will provide some details by writing one or more messages to the server error log. Sometimes this is enough for you to diagnose & fix the problem yourself (such as file permissions or the like). The default location of the error log is /var/log/httpd/error_log, but see the ErrorLog directive in your config files for the location on your server.

3. Why do I get "setgid: Invalid argument" at startup?

Your Group directive (probably in conf/httpd.conf) needs to name a group that actually exists in the /etc/group file (or your system's equivalent). This problem is also frequently seen when a negative number is used in the Group directive (e.g., "Group #-1"). Using a group name -- not group number -- found in your system's group database should solve this problem in all cases.

4. How do I tell what modules have been compiled into SWS?

Do this at the command line:

[root@ntbox conf]# /usr/sbin/httpsd -l
Compiled-in modules:
http_core.c
mod_so.c

5. How can I detect syntax errors in my config files?

Do this at the command line:

[root@ntbox conf]# /usr/sbin/httpsd -t
Syntax OK

6. How can I keep from having to use srm.conf and access.conf?

You can override these two files by putting ResourceConfig and/or AccessConfig directives in your httpd.conf. If you do that the other two files will not be read. Notably the default install of SWS comes preconfigured to only use the httpd.conf file. If it's using the srm.conf and access.conf files you have made changes to the defaults which enabled those files.

7. What's the best way to read and understand the config files for Apache?

These files are documented very well in-line. The key when working with the config files is to develop a good understanding of Directive syntax and to mix that understanding with some experimentation in a non-production environment!