StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I have the same problem with Ubuntu 9.10 Server and Apache 2.2.12. I'm setting up a Subversion server with <code>mod_dav_svn</code> and added a <code>CustomLog</code> directive to <code>/etc/apache2/mods-available/dav_svn.conf</code> to log Subversion requests, but had the same problem (the log file was created when Apache started, but was never written to):</p> <pre><code><Location /svn> ... </Location> LogFormat "%t %u %{SVN-ACTION}e" svn_log CustomLog /var/log/apache2/svn_access.log svn_log env=SVN-ACTION </code></pre> <p>There are two workarounds for the issue that I found, which basically amount to the same thing. I'm documenting both here because they have different pros and cons.</p> <h3>Workaround 1</h3> <ol> <li><p>Delete the <code>CustomLog</code> directive from your configuration file, if you have it set up in a separate configuration file.</p></li> <li><p>Add the <code>CustomLog</code> directive to your site's <code>VirtualHost</code> entry. For me this was in <code>/etc/apache2/sites-available/default-ssl</code> because I'm only allowing SSL access to the Subversion repository. If you are using <code>/etc/apache2/sites-available/default</code>, you will want to edit that file instead (or in addition to <code>default-ssl</code> if you are using both).</p></li> <li><p>Restart Apache:</p></li> </ol> <p><code>sudo /etc/init.d/apache2 restart</code></p> <p><strong>Pro</strong></p> <p>You can have multiple <code>CustomLog</code> directives in the <code>VirtualHost</code> entry for your site, and they will all work.</p> <p><strong>Con</strong></p> <p>You have to move your <code>CustomLog</code> entry into your site's <code>VirtualHost</code> entry instead of having it in a separate configuration file.</p> <h3>Workaround 2</h3> <ol> <li><p>Comment out the <code>CustomLog</code> directive(s) in your site's <code>VirtualHost</code> entry. If you're using one of the default site configurations (<code>default</code> or <code>default-ssl</code>), there will be a <code>CustomLog</code> directive for the access log that you will need to comment out (yes, this turns off Apache's default access logging).</p></li> <li><p>Add your <code>CustomLog</code> directive to the appropriate configuration file. For me this was <code>/etc/apache2/mods-available/dav_svn.conf</code>.</p></li> <li><p>Restart Apache:</p></li> </ol> <p><code>sudo /etc/init.d/apache2 restart</code></p> <p><strong>Pro</strong></p> <p>You can keep your <code>CustomLog</code> directive in a separate configuration file.</p> <p><strong>Con</strong></p> <p>This workaround has the obvious disadvantage that you have to disable Apache's default access logging, but for me I don't care that much since I'm only using the server for Subversion access.</p> <h2>Conclusion</h2> <p>Neither of these workarounds are really ideal, but so far I haven't found a way to get it to work other than than the two workarounds above. I suppose we'll have to wait for the next release of Apache for this issue to be fixed.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload