Log problems

2004-04-26 Thread Nick Marino
Anyone have any idea why authentication info would not be going into the
radius.log file?

Each time the server starts it logs each server starting but after that no
authentication info gets logged and it was working prior to a restart of the
system now it does not.

I have double checked the logs to make sure it was set to write
authentication info to the radius log file and even restored a valid backup
of the radius.conf file that was working.

I have run check-radius-config to check the radius.conf file stops saying
there is another server running on port 3726... but there is no other server
running that i can find using ps.

Any other ways of checking whats running on a specific port? This is a linux
system.

Would be glad to post any other info needed.

Thanks.

P.S. I am not asking anyone to do any of the work for me just point me in a
direction that I have not already checked.



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-26 Thread Navid Sheik
What arguments are you passing to radiusd?

Are you using daemontools to supervise the process? I've seen some funny
behaviour of logging especially after sending a HUP signal under this
circumstance.

Navid Sheik

On Mon, 2004-04-26 at 21:47, Nick Marino wrote:
> Anyone have any idea why authentication info would not be going into the
> radius.log file?
> 
> Each time the server starts it logs each server starting but after that no
> authentication info gets logged and it was working prior to a restart of the
> system now it does not.
> 
> I have double checked the logs to make sure it was set to write
> authentication info to the radius log file and even restored a valid backup
> of the radius.conf file that was working.
> 
> I have run check-radius-config to check the radius.conf file stops saying
> there is another server running on port 3726... but there is no other server
> running that i can find using ps.
> 
> Any other ways of checking whats running on a specific port? This is a linux
> system.
> 
> Would be glad to post any other info needed.
> 
> Thanks.
> 
> P.S. I am not asking anyone to do any of the work for me just point me in a
> direction that I have not already checked.
> 
> 
> 
> - 
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> 


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-27 Thread Frédéric EVRARD
> Anyone have any idea why authentication info would not be going into the
> radius.log file?

put ../raddb/radiusd.conf parameters log_auth=yes, log_auth_badpass=yes,
log_auth_goodpass=yes if you need them. This three parameters are "no" by
default.
This logs are in ../var/log/radius/radact/auth-detail-[date].log

>
> Each time the server starts it logs each server starting but after that no
> authentication info gets logged and it was working prior to a restart of
> the
> system now it does not.
>
> I have double checked the logs to make sure it was set to write
> authentication info to the radius log file and even restored a valid
> backup
> of the radius.conf file that was working.
>
> I have run check-radius-config to check the radius.conf file stops saying
> there is another server running on port 3726... but there is no other
> server
> running that i can find using ps.

Don't forget to clean ../var/run/radiusd/radiusd.pid


>
> Any other ways of checking whats running on a specific port? This is a
> linux
> system.

look in /etc/services.. maybe it can help you ...

>
> Would be glad to post any other info needed.
>
> Thanks.
>
> P.S. I am not asking anyone to do any of the work for me just point me in
> a
> direction that I have not already checked.
>
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-27 Thread Nick Marino
 Original Message 
From: "Navid Sheik" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 26, 2004 10:42 PM
Subject: Re: Log problems

> What arguments are you passing to radiusd?
>
> Are you using daemontools to supervise the process? I've seen some
> funny behaviour of logging especially after sending a HUP signal
> under this circumstance.
>

Yes I am using daemon tools and I am passing -fyz -lstderr.
wierd thing is, this has been working fine for almost 2 years.

I have rebooted the server that is running the radius software many times
and it doesn't help.




- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-27 Thread Nick Marino
 Original Message 
From: "Frédéric EVRARD" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 27, 2004 3:55 AM
Subject: Re: Log problems

>> Anyone have any idea why authentication info would not be going into
>> the radius.log file?
>
> put ../raddb/radiusd.conf parameters log_auth=yes,
> log_auth_badpass=yes, log_auth_goodpass=yes if you need them. This
> three parameters are "no" by default.
> This logs are in ../var/log/radius/radact/auth-detail-[date].log
>
Yes I have all those entries and always have along with -fyz -lstderr for
the command line of radiusd.

It has been working for almost 2 years now it just stopped logging auth
info, not detail info.



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-27 Thread Alan DeKok
"Nick Marino" <[EMAIL PROTECTED]> wrote:
> Yes I have all those entries and always have along with -fyz -lstderr for
> the command line of radiusd.

  Don't pass command-line options to the server.  The interaction of
command-line options with configuration file options is awkward.

  Almost all command-line options will be removed in a future release.

  As to why it stopped logging, I'm not sure.  Try running it without
command-line options & seeing what happens then.

  Alan DeKok.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-27 Thread Nick Marino
 Original Message 
From: "Alan DeKok" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 27, 2004 9:52 AM
Subject: Re: Log problems

> "Nick Marino" <[EMAIL PROTECTED]> wrote:
>> Yes I have all those entries and always have along with -fyz
>> -lstderr for the command line of radiusd.
>
>   Don't pass command-line options to the server.  The interaction of
> command-line options with configuration file options is awkward.
>
>   Almost all command-line options will be removed in a future release.
>
>   As to why it stopped logging, I'm not sure.  Try running it without
> command-line options & seeing what happens then.
>
>   Alan DeKok.

Ok thanks I will try that and see what the results are. Although I got that
info from the FAQ on the freeradius website on setting up daemontools. You
may want to update that portion of the faq also.



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-27 Thread Nick Marino
 Original Message 
From: "Alan DeKok" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 27, 2004 9:52 AM
Subject: Re: Log problems

> "Nick Marino" <[EMAIL PROTECTED]> wrote:
>> Yes I have all those entries and always have along with -fyz
>> -lstderr for the command line of radiusd.
>
>   Don't pass command-line options to the server.  The interaction of
> command-line options with configuration file options is awkward.
>
>   Almost all command-line options will be removed in a future release.
>
>   As to why it stopped logging, I'm not sure.  Try running it without
> command-line options & seeing what happens then.
>
>   Alan DeKok.
>

Ok I removed everything from the command line for radiusd except -f and
lstderr that is supposed to be required for daemontools to work correctly.

Still same result there are no authentication log entries in the radius.log.
Here is a section of what is showing up when radiusd is started or
restarted.
Logging had been working fine for almost 2 years then it stops.. Something
must have changed but where?


  File: radius.logCol 0  4109 bytes
100%
Mon Apr 26 19:18:16 2004 : Info: rlm_sql: Starting connect to MySQL server
for #3
Mon Apr 26 19:18:16 2004 : Info: rlm_sql: Starting connect to MySQL server
for #4
Mon Apr 26 19:30:13 2004 : Info: rlm_sql: Driver rlm_sql_mysql loaded and
linked
Mon Apr 26 19:30:13 2004 : Info: rlm_sql: Attempting to connect to
[EMAIL PROTECTED]:3306/defuniak
Mon Apr 26 19:30:13 2004 : Info: rlm_sql: Starting connect to MySQL server
for #0
Mon Apr 26 19:30:13 2004 : Info: rlm_sql: Starting connect to MySQL server
for #1
Mon Apr 26 19:30:13 2004 : Info: rlm_sql: Starting connect to MySQL server
for #2
Mon Apr 26 19:30:13 2004 : Info: rlm_sql: Starting connect to MySQL server
for #3
Mon Apr 26 19:30:13 2004 : Info: rlm_sql: Starting connect to MySQL server
for #4
Mon Apr 26 20:09:21 2004 : Info: rlm_sql: Driver rlm_sql_mysql loaded and
linked
Mon Apr 26 20:09:21 2004 : Info: rlm_sql: Attempting to connect to
[EMAIL PROTECTED]:3306/defuniak
Mon Apr 26 20:09:21 2004 : Info: rlm_sql: Starting connect to MySQL server
for #0
Mon Apr 26 20:09:21 2004 : Info: rlm_sql: Starting connect to MySQL server
for #1
Mon Apr 26 20:09:21 2004 : Info: rlm_sql: Starting connect to MySQL server
for #2
Mon Apr 26 20:09:21 2004 : Info: rlm_sql: Starting connect to MySQL server
for #3
Mon Apr 26 20:09:21 2004 : Info: rlm_sql: Starting connect to MySQL server
for #4
Mon Apr 26 20:11:43 2004 : Info: rlm_sql: Driver rlm_sql_mysql loaded and
linked
Mon Apr 26 20:11:43 2004 : Info: rlm_sql: Attempting to connect to
[EMAIL PROTECTED]:3306/defuniak
Mon Apr 26 20:11:43 2004 : Info: rlm_sql: Starting connect to MySQL server
for #0
Mon Apr 26 20:11:43 2004 : Info: rlm_sql: Starting connect to MySQL server
for #1
Mon Apr 26 20:11:43 2004 : Info: rlm_sql: Starting connect to MySQL server
for #2
Mon Apr 26 20:11:43 2004 : Info: rlm_sql: Starting connect to MySQL server
for #3
Mon Apr 26 20:11:43 2004 : Info: rlm_sql: Starting connect to MySQL server
for #4
Mon Apr 26 21:40:00 2004 : Info: rlm_sql: Driver rlm_sql_mysql loaded and
linked
Mon Apr 26 21:40:00 2004 : Info: rlm_sql: Attempting to connect to



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-28 Thread Alan DeKok
"Nick Marino" <[EMAIL PROTECTED]> wrote:
> Ok I removed everything from the command line for radiusd except -f and
> lstderr that is supposed to be required for daemontools to work correctly.

  Ah..

> Still same result there are no authentication log entries in the radius.log.

  No.. you told it to log to stderr.  That's what "-lstderr" means.
If you don't say "-lstderr", logging goes to wherever it says in
"radiusd.conf", usually "radius.log" somewhere.

  Unless... if you mean that the "radius.log" is one created by
daemontools...

> Logging had been working fine for almost 2 years then it stops.. Something
> must have changed but where?

  I'm not sure what you're doing, so I can't say for sure.

  Alan DeKok.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Re: Log problems

2004-04-28 Thread Nick Marino
>   No.. you told it to log to stderr.  That's what "-lstderr" means.
> If you don't say "-lstderr", logging goes to wherever it says in
> "radiusd.conf", usually "radius.log" somewhere.
>
>   Unless... if you mean that the "radius.log" is one created by
> daemontools...
>
>> Logging had been working fine for almost 2 years then it stops..
>> Something must have changed but where?
>
>   I'm not sure what you're doing, so I can't say for sure.
>
>   Alan DeKok.

No lstderr tells svc (daemontools) to send its errors to stderr not
freeradius and we are not talking about standard errors we are talking about
authentication entries being added to radius.log when someone logs in auth
entries are to be written via either command line options -yz or the entries
in radiusd.conf. Guess I dont have to tell you that though.

Anyway I solved the problem of the it not logging.
The problem was that radiusd is set to run as user radius and in the config
file it was set to user=radius
group=radius

I removed the existing radius.log file so that a new one would be created
but for some reason the new log was created but as root/radius (owner root -
group radius) and after radiusd got past the initial startup it starts
trying to do things as user radius so when it went to write to the
radius.log file that had just been created ( by root) it didnt have
permission. I changed the permissions on the radius.log file to
radius/radius and all is well now and  it is putting in the authentication
info like it is supposed to now.

Maybe this will help someone in the future.



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html