Ignore:
Timestamp:
Dec 3, 2010, 10:44:38 PM (14 years ago)
Author:
katerina
Message:

Fix for ticket #229 (malfunction on CentOS 4.8 / gcc4), documentation update.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/docs/HOWTO-client+server-troubleshooting.html

    r91 r307  
    135135<ul>
    136136  <li>Almost all problems can only be diagnosed correctly by checking the
    137       <b>server</b> logs</li>
    138   <li>If the server does not write logs, <b>fix this first</b>. For debugging,
    139       stop the server, then run it in the foreground with
    140       <tt>yule -p info --foreground</tt></li>
     137      <b>server logs</b>.</li>
     138  <li>
     139    If the server does not write logs, <b>fix this first</b>. For debugging,
     140    stop the server, then run it in the foreground with
     141    <tt>yule -p info --foreground</tt>
     142    <ul>
     143      <li>
     144        By default, the server logs to the file
     145        <tt>/var/log/yule/yule_log</tt>, and since the server drops
     146        root privileges on startup, the directory <tt>/var/log/yule</tt>
     147        must be writable for the nonprivileged user the server runs
     148        as (the first existing out of: yule, daemon, nobody).
     149      </li>
     150      <li>
     151        Logging to the logfile must be enabled in the
     152        <tt>/etc/yulerc</tt> config file (e.g. LogSeverity=mark, or
     153        LogSeverity=info for enhanced verbosity).
     154      </li>
     155    </ul>
     156  </li>
    141157</ul>
    142158</div>
    … …  
    257273     <p>
    258274     <p>
    259      This does not work for a number of people because (1) the
    260      <tt>/etc/hosts</tt> file on the client machine has errors
    261      (yes, there are plenty machines with a completely
    262      messed up <tt>/etc/hosts</tt> file), (2) the
    263      server cannot resolve the client address because the local DNS is
    264      f***ed up, or (3) the client machine has multiple network interfaces, and
    265      the interface used is not the one the client name resolves to.
    266      </p>
    267 
    268        <p>
     275     This does not work for a number of people because
     276     <ol>
     277       <li>
     278         the
     279         <tt>/etc/hosts</tt> file on the client machine has errors
     280         (yes, there are plenty machines with a completely
     281         messed up <tt>/etc/hosts</tt> file),
     282       </li>
     283       <li>
     284         the
     285         server cannot resolve the client address because the local DNS is
     286         misconfigured, or
     287       </li>
     288       <li>
     289         the client machine has multiple network interfaces, and
     290         the interface used is not the one the client name resolves to.
     291       </li>
     292     </ol>
     293     </p>
     294
     295     <p>
    269296       If the client uses the wrong interface on a multi-interface machine,
    270297       there is a config file option
    … …  
    272299       that allows to choose the interface the client will use for
    273300       outgoing connections.
    274        </p>
    275        <p>
     301     </p>
     302     <p>
    276303       If you want to download the config file from the server, you
    277304       should instead use the corresponding command line option
    278305       <tt>--bind-address=</tt><i>IP address</i>
    279306       to select the interface.
    280        </p>
    281 
    282      <p>
    283      If you encounter problems, you may (1) fix your
    284      <tt>/etc/hosts</tt> file(s), (2) fix your local DNS, or
    285      (3) switch to the second method.
    286      </p>
    287      <p>
    288      Errors in name resolving/cross-checking can be avoided by setting a
    289      very low severity (lower than the logging threshold), e.g.
    290      </p>
    291      <p>
    292      <tt>SeverityLookup=</tt><i>debug</i>
    293      </p>
    294      <p>
    295      in the <i>Misc</i> section of the server configuration,
    296      if you prefer running <i>unsafe</i> at any speed
    297      instead of fixing the problem (you have been warned). Doing so will
    298      allow an attacker to pose as the client.
     307     </p>
     308
     309     <p>
     310       If you encounter problems, you may (1) fix your
     311       <tt>/etc/hosts</tt> file(s), (2) fix your local DNS, or
     312       (3) switch to the second method.
     313     </p>
     314     <p>
     315       Error messages related to name resolving/cross-checking can be
     316       suppressed by setting a
     317       very low severity (lower than the logging threshold), e.g.
     318     </p>
     319     <p>
     320       <tt>SeverityLookup=</tt><i>debug</i>
     321     </p>
     322     <p>
     323       in the <i>Misc</i> section of the server configuration,
     324       if you prefer running <i>unsafe</i> at any speed
     325       instead of fixing the problem (you have been warned). Doing so will
     326       allow an attacker to pose as the client.
    299327     </p>
    300328  </li>
    … …  
    325353<p>
    326354The client does <i>not</i> tell the server the path to the requested
    327 file - it just requests a config or a database file. It's entirely the
     355file - it just tells the <em>type</em> of the file, i.e.
     356either a configuration file or a database file. It is entirely the
    328357responsibility of the server to locate the correct file and send it.
    329358</p>
    … …  
    356385To fix: put the file in the correct location, make sure the permissions
    357386are ok.
     387<ul>
     388  <li>
     389    Note that <em>the server drops root privileges at startup</em> and
     390    runs as an unprivileged user (the first existing out of:
     391    yule, daemon, nobody).
     392  </li>
     393  <li>
     394    Also remember that to access a file, at least execute permission is required
     395    <em>for every directory in the path</em>.
     396  </li>
     397</ul>
    358398</p>
    359399
Note: See TracChangeset for help on using the changeset viewer.