detail logging not logging?

[Alan DeKok]

Brad Clemmons Jr wrote:
> The issue I'm having now though is that I can't seem to get the detail
> logging to work so the only time I get any logs is if I purposefully
> foul something up to cause it to error.  Right now I have the detail
> statement at the bottom of the file.

  Right there... there's a problem.

  The default configuration logs to the detail file.  There is literally
*nothing* you need to do to configure it to log to the detail file.

>  I've tried moving it into the
> modules section but that didn't make any different.  I also tried
> manually specifying the fully qualified path for the log file as well to
> no avail. 

  Making random changes without understanding how the server works won't
help.

> I verified user and group permissions in the necessary directories, but
> I must still be missing something.  Anyone able to point out what's
> wrong but right under my nose?
> 
> Also it's worth noting this is running on Solaris10x86 under a zone.

  You're either running an old version of the server, OR you've hacked
the default configuration files into oblivion.


> #$INCLUDE sites-enabled/
> 
> detail {
>         detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d
>         #detailfile = ${radacctdir}/%{NAS-IP-Address}/detail-%Y%m%d
>         #detailfile = ${radacctdir}/detail.log
>         detailperm = 0600
>         }

  And... yes.  You've completely butchered the default configuration files.

  Don't do that.

  Throw away everything you've done.  Replace it with the default
configuration files.  Add a client definition.  Run it in debugging
mode.  Send it accounting packets.  Verify that it writes to the detail
file.

  15 minutes.  Tops.

  What you've done is clearly to make drastic changes to the
configuration files without understanding how it works.  There *is*
documentation on the configuration files.  Please *read* it before
editing them.  There *are* lots of examples.  Please read them.

  Alan DeKok.