SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2012-11-17 16:14:14

antiv0rtex
#! Die Hard
From: Earth
Registered: 2012-10-05
Posts: 574

[apache2] something's not quite working right...

I have for the past while been working on getting a simple LAMP web server to function correctly. Once it is working, its resources will be shared between myself and a friend of mine - but it is beginning to seem like that day is farther away than ever.

The system is running Statler because I am so impressed with #!'s preformance and allocation of system resources, and because Openbox is a good compromise between a relatively-unfriendly pure CLI  and a full-blown desktop environment.

I have been attempting to get the system's installation of the Apache web server configured with Virthual Hosts as per this artlce, but I am not really very experienced at all with Apache and I think I may have edited something wrong, because now Apahe does not seem to be working.

Here is what I am trying to accomplish, more-or-less in this order:

  • Successfully coerce Apache into running on port 7490 - or a different port, if someone here has a better suggestion.

  • Host (at least) twp different domain names, each with their own separate directories for uploads and logs.

I assume the reason that all is not functioning normally is some edit of mine in a configuration file, so here are copies of various "important-looking" files -

/etc/apache2/apache2.conf wrote:

#
# 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 http://httpd.apache.org/docs/2.2/ 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. 
#
# 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 "foo.log"
# with ServerRoot set to "/etc/apache2" will be interpreted by the
# server as "/etc/apache2/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.
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
LockFile ${APACHE_LOCK_DIR}/accept.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

##
## Server-Pool Size Regulation (MPM specific)
##

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
    StartServers          5
    MinSpareServers       5
    MaxSpareServers      10
    MaxClients          150
    MaxRequestsPerChild   0
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadLimit: ThreadsPerChild can be changed to this maximum value during a
#              graceful restart. ThreadLimit can only be changed by stopping
#              and starting Apache.
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
    StartServers          2
    MinSpareThreads      25
    MaxSpareThreads      75
    ThreadLimit          64
    ThreadsPerChild      25
    MaxClients          150
    MaxRequestsPerChild   0
</IfModule>

# event MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_event_module>
    StartServers          2
    MaxClients          150
    MinSpareThreads      25
    MaxSpareThreads      75
    ThreadLimit          64
    ThreadsPerChild      25
    MaxRequestsPerChild   0
</IfModule>

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#

AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy all
</Files>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain


#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

# Include module configuration:
Include mods-enabled/*.load
Include mods-enabled/*.conf

# Include all the user configurations:
Include httpd.conf

# Include ports listing
Include ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
Include conf.d/

# Include the virtual host configurations:
Include sites-enabled/

/etc/apache2/ports.conf wrote:

# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default
# This is also true if you have upgraded from before 2.2.9-3 (i.e. from
# Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and
# README.Debian.gz

NameVirtualHost xxx.xxx.xxx.xx:80
Listen 80
Listen 7490

<IfModule mod_ssl.c>
    # If you add NameVirtualHost *:443 here, you will also have to change
    # the VirtualHost statement in /etc/apache2/sites-available/default-ssl
    # to <VirtualHost *:443>
    # Server Name Indication for SSL named virtual hosts is currently not
    # supported by MSIE on Windows XP.
    Listen 443
</IfModule>

<IfModule mod_gnutls.c>
    Listen 443
</IfModule>

/etc/apache2/sites-enabled/www.xyz.org (actual domain name used has been removed in example) wrote:

#
#  xyz.org (/etc/apache2/sites-available/www.xyz.org)
#
<VirtualHost xxx.xxx.xxx.xx:7490>
        ServerAdmin deskacenter@mailoo.org
        ServerName  www.xyz.org
        ServerAlias xyz.org

        # Indexes + Directory Root.
        DirectoryIndex index.html
        DocumentRoot /home/www/www.xyz.org/public_html/

        # CGI Directory
        ScriptAlias /cgi-bin/ /home/www/www.xyz.org/cgi-bin/
        <Location /cgi-bin>
                Options +ExecCGI
        </Location>


        # Logfiles
        ErrorLog  /home/www/www.xyz.org/logs/error.log
        CustomLog /home/www/www.xyz.org/logs/access.log combined
</VirtualHost>

/etc/apache2/sites-enabled/000-default wrote:

<VirtualHost xxx.xxx.xxx.xx:80 xxx.xxx.xxx.xx:7490>
    ServerAdmin deskacenter@mailoo.org

    DocumentRoot /var/www
    <Directory />
        Options FollowSymLinks
        AllowOverride None
    </Directory>
    <Directory /var/www/>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride All
        Order allow,deny
        allow from all
    </Directory>

    ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
    <Directory "/usr/lib/cgi-bin">
        AllowOverride None
        Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
        Order allow,deny
        Allow from all
    </Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log

    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn

    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

/etc/apache2/conf.d/virtual.conf wrote:

#
#  We're running multiple virtual hosts.
#
NameVirtualHost *

If someone more literate than I could give me advice on what to do next, I would be very happy.

It would be worth mentioning that if need be, I can always start over again with a fresh install of Statler. That being said, I wanted to check here before doing anything that drastic wink

Thank you in advance for any information provided.

/L

Offline

Be excellent to each other!

#2 2012-11-17 16:58:15

CBizgreat!
#! Die Hard
Registered: 2011-07-27
Posts: 1,498

Re: [apache2] something's not quite working right...

<Pointless babble>Not @ all tryin to be a smart@rse + AM NOT an apache guru. Would hit google, get a pdf ... they're a dime a dozen online. Hopefully a newer and/or more extensive one than the article you're using for a reference. Just an opinion on this topic, could be ALOT of things ... ALOT < w caps for emphasis.  glasses

Making my head hurt just thinking about all the poss's. When you say things like "apache isn't working"??? That leaves ALOT of ground. Would think it a good idea to clarify (more clearly) describe what that means. Isn't working for you locally, isn't working for the friend you're trying to share it with remotely ? Stuff like ... how do you even know the problem is apache2 ? Mentioned you're port forwarding/etc ... could be that perhaps ? Did you set that up correctly ? Anyway ... <add about a gazillion other poss's here.>

Though you don't need to reinstall #! to fix whatever it may be. Just purge apache2 in synaptic ( mark for complete removal.) or apt-get/aptitude instead ? May not be server guru ... but know enough to know it's not a simple subject ... thusly doubtful anyone can give a simple answer for you. Ya wanna learn about something ... Pretty much no way of getting around well ... learning about it. wink

Sighs ... yep I realize, this post is Soooo not helping. Just 2 cents and random babble ... arghhh !


</Pointless babble>


Vll !   monkey


Ha ! More babble ! tongue

Some afterthoughts:
#1. That ginormous post you posted broke my scroll wheel THANKS ALOT DOOD. sad ( kidding.)

#2. Am not saying there's anything wrong ( imo) w reinstalling to fix borkage either ... whatever gets da job done etc. Could be a good opp to learn how to back up #! and restore it ? Thataway you can break it as many times as you like and be up and running again more quickly ?

Last edited by CBizgreat! (2012-11-17 17:18:04)


Some common cbiz abbreviations. This will save me time and yet @ same time tell folks what the babble is supposed to mean.

Vll ! = ( Viva la gnu/Linux !)    Vl#!! = ( Viva la #! !)    Last but not least, UD ... OD ! = ( Use Debian ... or die !) tongue

Offline

#3 2012-11-18 01:27:24

dura
Bloated Gimp
From: interzone
Registered: 2012-09-15
Posts: 2,106

Re: [apache2] something's not quite working right...

Apache is notoriously difficult to get working. If you're like me and struggle with it because you don't know what you're doing, I'd recommend trying lighttpd and mysql/sqlite instead. Much, much easier to set up and actually get working. Not a solution, just a suggestion.

Offline

#4 2012-11-18 02:19:31

benginm
#! Junkie
From: Underneath!
Registered: 2012-11-11
Posts: 488

Re: [apache2] something's not quite working right...

Hi R3nCi, define not working! .. am sure you'll get more assistance if you provide more details .

# Now , when it comes to hosting web server and setting up a LAMP .. linode Guides/Reference got to be the best i came across on the web.

http://library.linode.com/hosting-website

http://library.linode.com/lamp-guides

Offline

#5 2012-11-18 07:19:30

antiv0rtex
#! Die Hard
From: Earth
Registered: 2012-10-05
Posts: 574

Re: [apache2] something's not quite working right...

CBizgreat! wrote:

<Pointless babble>Not @ all tryin to be a smart@rse + AM NOT an apache guru. Would hit google, get a pdf ... they're a dime a dozen online. Hopefully a newer and/or more extensive one than the article you're using for a reference. Just an opinion on this topic, could be ALOT of things ... ALOT < w caps for emphasis.  glasses

Making my head hurt just thinking about all the poss's. When you say things like "apache isn't working"??? That leaves ALOT of ground. Would think it a good idea to clarify (more clearly) describe what that means. Isn't working for you locally, isn't working for the friend you're trying to share it with remotely ? Stuff like ... how do you even know the problem is apache2 ? Mentioned you're port forwarding/etc ... could be that perhaps ? Did you set that up correctly ? Anyway ... <add about a gazillion other poss's here.>

Though you don't need to reinstall #! to fix whatever it may be. Just purge apache2 in synaptic ( mark for complete removal.) or apt-get/aptitude instead ? May not be server guru ... but know enough to know it's not a simple subject ... thusly doubtful anyone can give a simple answer for you. Ya wanna learn about something ... Pretty much no way of getting around well ... learning about it. wink

Sighs ... yep I realize, this post is Soooo not helping. Just 2 cents and random babble ... arghhh !


</Pointless babble>


Vll !   monkey


Ha ! More babble ! tongue

Some afterthoughts:
#1. That ginormous post you posted broke my scroll wheel THANKS ALOT DOOD. sad ( kidding.)

#2. Am not saying there's anything wrong ( imo) w reinstalling to fix borkage either ... whatever gets da job done etc. Could be a good opp to learn how to back up #! and restore it ? Thataway you can break it as many times as you like and be up and running again more quickly ?

Hm, for some reason I had not thought of simply purging apache2. I will keep that option in mind in future, but this time I will simply reinstall as I enjoy fresh starts. smile

dura wrote:

Apache is notoriously difficult to get working. If you're like me and struggle with it because you don't know what you're doing, I'd recommend trying lighttpd and mysql/sqlite instead. Much, much easier to set up and actually get working. Not a solution, just a suggestion.

I have heard this about Apache from several sources. I should probably make an attempt at configuring lighttpd once the reinstall is finished. Thanks!

Sary wrote:

Hi R3nCi, define not working! .. am sure you'll get more assistance if you provide more details .

# Now , when it comes to hosting web server and setting up a LAMP .. linode Guides/Reference got to be the best i came across on the web.

http://library.linode.com/hosting-website

http://library.linode.com/lamp-guides

As I've mentioned in my responses to the above posts, I am going to make an attempt at re-installing Statler and being a bit more careful with regards to editing configuration files. If I run into problems with that, I will surely update this thread.

Thank you, also, for the links to Linode's LAMP guides.

Many thanks,

/L

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.

Debian Logo