this is file apache error <br><br><br><br>Based upon the NCSA server configuration files originally by Rob McCool.<br>#<br># This is the main Apache server configuration file. It contains the<br># configuration directives that give the server its instructions.<br>
# See <a href="http://httpd.apache.org/docs/2.2/">http://httpd.apache.org/docs/2.2/</a> for detailed information about<br># the directives.<br>#<br># Do NOT simply read the instructions in here without understanding<br># what they do. They're here only as hints or reminders. If you are unsure<br>
# consult the online docs. You have been warned. <br>#<br># The configuration directives are grouped into three basic sections:<br># 1. Directives that control the operation of the Apache server process as a<br># whole (the 'global environment').<br>
# 2. Directives that define the parameters of the 'main' or 'default' server,<br># which responds to requests that aren't handled by a virtual host.<br># These directives also provide default values for the settings<br>
# of all virtual hosts.<br># 3. Settings for virtual hosts, which allow Web requests to be sent to<br># different IP addresses or hostnames and have them handled by the<br># same Apache server process.<br>#<br>
# Configuration and logfile names: If the filenames you specify for many<br># of the server's control files begin with "/" (or "drive:/" for Win32), the<br># server will use that explicit path. If the filenames do *not* begin<br>
# with "/", the value of ServerRoot is prepended -- so "/var/log/apache2/foo.log"<br># with ServerRoot set to "" will be interpreted by the<br># server as "//var/log/apache2/foo.log".<br>
#<br><br>### Section 1: Global Environment<br>#<br># The directives in this section affect the overall operation of Apache,<br># such as the number of concurrent requests it can handle or where it<br># can find its configuration files.<br>
#<br><br>#<br># ServerRoot: The top of the directory tree under which the server's<br># configuration, error, and log files are kept.<br>#<br># NOTE! If you intend to place this on an NFS (or otherwise network)<br># mounted filesystem then please read the LockFile documentation (available<br>
# at <URL:<a href="http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile">http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile</a>>);<br># you will save yourself a lot of trouble.<br>#<br># Do NOT add a slash at the end of the directory path.<br>
#<br>ServerRoot "/etc/apache2"<br><br>#<br># The accept serialization lock file MUST BE STORED ON A LOCAL DISK.<br>#<br>#<IfModule !mpm_winnt.c><br>#<IfModule !mpm_netware.c><br>LockFile /var/lock/apache2/accept.lock<br>
#</IfModule><br>#</IfModule><br><br>#<br># PidFile: The file in which the server should record its process<br># identification number when it starts.<br># This needs to be set in /etc/apache2/envvars<br>#<br>PidFile ${APACHE_PID_FILE}<br>
<br>#<br># Timeout: The number of seconds before receives and sends time out.<br>#<br>Timeout 300<br><br>#<br># KeepAlive: Whether or not to allow persistent connections (more than<br># one request per connection). Set to "Off" to deactivate.<br>
#<br>KeepAlive On<br><br>#<br># MaxKeepAliveRequests: The maximum number of requests to allow<br># during a persistent connection. Set to 0 to allow an unlimited amount.<br># We recommend you leave this number high, for maximum performance.<br>
#<br>MaxKeepAliveRequests 100<br><br>#<br># KeepAliveTimeout: Number of seconds to wait for the next request from the<br># same client on the same connection.<br>#<br>KeepAliveTimeout 15<br><br>##<br>## Server-Pool Size Regulation (MPM specific)<br>
## <br><br># prefork MPM<br># StartServers: number of server processes to start<br># MinSpareServers: minimum number of server processes which are kept spare<br># MaxSpareServers: maximum number of server processes which are kept spare<br>
# MaxClients: maximum number of server processes allowed to start<br># MaxRequestsPerChild: maximum number of requests a server process serves<br><IfModule mpm_prefork_module><br> StartServers 5<br> MinSpareServers 5<br>
MaxSpareServers 10<br> MaxClients 150<br> MaxRequestsPerChild 0<br></IfModule><br><br># worker MPM<br># StartServers: initial number of server processes to start<br># MaxClients: maximum number of simultaneous client connections<br>
# MinSpareThreads: minimum number of worker threads which are kept spare<br># MaxSpareThreads: maximum number of worker threads which are kept spare<br># ThreadsPerChild: constant number of worker threads in each server process<br>
# MaxRequestsPerChild: maximum number of requests a server process serves<br><IfModule mpm_worker_module><br> StartServers 2<br> MinSpareThreads 25<br> MaxSpareThreads 75 <br> ThreadLimit 64<br>
ThreadsPerChild 25<br> MaxClients 150<br> MaxRequestsPerChild 0<br></IfModule><br><br># event MPM<br># StartServers: initial number of server processes to start<br># MaxClients: maximum number of simultaneous client connections<br>
# MinSpareThreads: minimum number of worker threads which are kept spare<br># MaxSpareThreads: maximum number of worker threads which are kept spare<br># ThreadsPerChild: constant number of worker threads in each server process<br>
# MaxRequestsPerChild: maximum number of requests a server process serves<br><IfModule mpm_event_module><br> StartServers 2<br> MaxClients 150<br> MinSpareThreads 25<br> MaxSpareThreads 75 <br>
ThreadLimit 64<br> ThreadsPerChild 25<br> MaxRequestsPerChild 0<br></IfModule><br><br># These need to be set in /etc/apache2/envvars<br>User ${APACHE_RUN_USER}<br>Group ${APACHE_RUN_GROUP}<br>
<br>#<br># AccessFileName: The name of the file to look for in each directory<br># for additional configuration directives. See also the AllowOverride<br># directive.<br>#<br><br>AccessFileName .htaccess<br><br>#<br># The following lines prevent .htaccess and .htpasswd files from being <br>
# viewed by Web clients. <br>#<br><Files ~ "^\.ht"><br> Order allow,deny<br> Deny from all<br></Files><br><br>#<br># DefaultType is the default MIME type the server will use for a document<br># if it cannot otherwise determine one, such as from filename extensions.<br>
# If your server contains mostly text or HTML documents, "text/plain" is<br># a good value. If most of your content is binary, such as applications<br># or images, you may want to use "application/octet-stream" instead to<br>
# keep browsers from trying to display binary files as though they are<br># text.<br>#<br>DefaultType text/plain<br><br><br>#<br># HostnameLookups: Log the names of clients or just their IP addresses<br># e.g., <a href="http://www.apache.org">www.apache.org</a> (on) or 204.62.129.132 (off).<br>
# The default is off because it'd be overall better for the net if people<br># had to knowingly turn this feature on, since enabling it means that<br># each client request will result in AT LEAST one lookup request to the<br>
# nameserver.<br>#<br>HostnameLookups Off<br><br># ErrorLog: The location of the error log file.<br># If you do not specify an ErrorLog directive within a <VirtualHost><br># container, error messages relating to that virtual host will be<br>
# logged here. If you *do* define an error logfile for a <VirtualHost><br># container, that host's errors will be logged there and not here.<br>#<br>ErrorLog /var/log/apache2/error.log<br><br>#<br># LogLevel: Control the number of messages logged to the error_log.<br>
# Possible values include: debug, info, notice, warn, error, crit,<br># alert, emerg.<br>#<br>LogLevel warn<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><div class="gmail_quote">
On Mon, Jan 3, 2011 at 6:51 PM, Randall Rowe <span dir="ltr"><<a href="mailto:r.rowe@lincolnlibraries.org">r.rowe@lincolnlibraries.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
It means that the file /etc/apache2/sites-enabled/koha has an error.<br>
There is a closing </VirtualHost> without an opening <VirtualHost>.<br>
Check the file and see if you can figure out the problem or post it and we'll see what went wrong.<br>
<br>
<p>Randy Rowe<br>
Lincoln City Libraries I.T.</p><div class="im">
<br>
-----Original Message-----<br>
From: "Yatheesh Y" <<a href="mailto:yatheeshb@gmail.com" target="_blank">yatheeshb@gmail.com</a>><br>
Sent 1/3/2011 5:19:10 AM<br>
To: <a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a><br>
Subject: [Koha] unable to run apache after upgrade from 3.0 to 3.2<br>
<br>
after upgrading unable to run apache it gives following error<br>
<br>
what is this?<br>
<br>
<br>
Restarting web server apache2 apache2: Syntax error on line 265 of /etc/apache2/apache2.conf: Syntax error on line 95 of /etc/apache2/sites-enabled/koha: </VirtualHost> without matching <VirtualHost> section<br>
<br clear="all">
<br></div><div><div></div><div class="h5">
-- <br>
<div style="text-align: left;">----------------------------<br>
</div>
<span style="font-family: times new roman,serif; font-size: 18px;">Y.Yatheesh babu<br>
Librarian<br>
Shri Shakti College of Hotel Management<br>
Venus Plaza Begumpet<br>
Hyderabad-500 016<br>
09966178388</span><br>
<br>
<pre>_______________________________________________
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a>
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a>
</pre></div></div></blockquote></div><br><br clear="all"><br>-- <br><div style="text-align: left;">----------------------------<br></div><font style="font-family: times new roman,serif;" size="4">Y.Yatheesh babu<br>Librarian<br>
Shri Shakti College of Hotel Management<br>Venus Plaza Begumpet<br>Hyderabad-500 016<br>09966178388</font><br><br>