title: uWSGI with --master causing Illegal Seek errors
body: <p>uWSGI is causing Illegal Seek errors.  I finally narrowed it down to the <code>--master</code> flag. If I have the master process enabled, then after starting uWSGI I get tons of these, about 1 per second:</p>
  <pre><code>uwsgi_check_logrotate()/lseek(): Illegal seek [core/logging.c line 497]
  </code></pre>
  <p>I've been pouring over the uWSGI docs but cannot find anything on how to correctly set up the master or what it needs to function properly.</p>
  <p>Any help would be appreciated, as I've read the master process is quite crucial for a production environment.</p>
  <p>I'm uncertain why turning on the <code>--master</code> process would cause this to happen, but I finally stumbled on a possible cause:</p>
  <blockquote>
  <p>The most basic form of logging in uWSGI is writing requests, errors, and &gt;informational messages to stdout/stderr. This happens in the default &gt;configuration. The most basic form of log redirection is the <code>--logto</code> / <code>--logto2</code> / <code>&gt;--daemonize</code> options which allow you to redirect logs to files.</p>
  </blockquote>
  <p>I had had <code>logto = path/to/logfile</code> declared and didn't realize that the default behavior was to send logs to stdout. So I'd made a system link to stdout from my log file.</p>
  <p>However this doesn't seem to be a problem when the <code>--master</code> process is not turned on.</p>