Re: Fwd: (RADIATOR) log files behavior

2001-08-06 Thread Mariano Absatz

Hi Mike, Hugh...

it's been more than a couple of months since this message... in fact, the
Log.pm got into 2.18.2 in the meantime... the problem I have is that I still
couldn't solve my first item:

  1) As I noted in a message exchange with Hugh (cc: the list) a couple of
  weeks ago, AuthLog FILE is not working. The file isn't created at all
  (and Radiator has sufficient permissions since a Log FILE in the same
  directory IS created.
 

Today I added an AuthLog SQL besides the AuthLog FILE to no avail... I
also erased all of my Radiator installation (since I had used it to test some
modules you sent me prior to release) and re-installed the plain 2.18.2
(without any patches, since none of them seem to be at all related with my
problem).

I still can't get it working...

Whatever I do, the log files aren't created (there is no permissions problem,
in fact, Radiator is running as root), the database table for authlogging is
empty.

I'm attaching all of my config files radius-*.cfg (one of them is for
accounting only, other for authentication only and the larger one is included
in both). The other files include an add-on for the dictionary (with faked
attributes) and other files included from the config files.

Do you have a clue on why it isn't working? Anything I can do to check here?

Here's a small portion of an authentication seen from the authentication
debug log


##
Mon Aug  6 11:15:11 2001: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 33754 
Code:   Access-Request
Identifier: 190
Authentic:  1234567890123456
Attributes:
User-Name = baby@pert
Service-Type = Framed-User
NAS-IP-Address = 200.59.130.83
NAS-Port = 1234
Called-Station-Id = 123456789
Calling-Station-Id = 987654321
NAS-Port-Type = Async
User-Password = A/225x%251233:238192220`17612\146

Mon Aug  6 11:15:11 2001: DEBUG: Rewrote user name to baby@pert
Mon Aug  6 11:15:11 2001: DEBUG: Rewrote user name to baby@pert
Mon Aug  6 11:15:11 2001: DEBUG: Check if Handler Request-Type = Access-
Request should be used to handle this request
Mon Aug  6 11:15:11 2001: DEBUG: Handling request with Handler 'Request-Type
= Access-Request'
Mon Aug  6 11:15:11 2001: DEBUG: SessDBUsers Deleting session for baby@pert,
200.59.130.83, 1234
Mon Aug  6 11:15:11 2001: DEBUG: do query is: DELETE FROM USUARIOS_EN_LINEA
WHERE USUA_IP_NAS='200.59.130.83' AND USUA_PORT='12
34'

Mon Aug  6 11:15:11 2001: DEBUG: Handling with Radius::AuthSQL
Mon Aug  6 11:15:11 2001: DEBUG: Handling with Radius::AuthSQL
Mon Aug  6 11:15:11 2001: DEBUG: Query is: SELECT U.USU_CLAVE, S.SER_CODIGO,
S.SER_MAX_SESSION_CONCURRENTES, S.TIMEFRAMEID, S.S
ER_GEN_CHECK, S.SER_GEN_REPLY, VS.VISP_SER_VALID_DNIS, U.USU_IP_NRO_FIJA,
U.USU_IP_MASC_FIJA, U.USU_TIEMPO_RESTANTE, U.USU_BYTE
S_RESTANTES, U.USU_SUSPENDIDO, U.USU_GEN_CHECK, U.USU_GEN_REPLY, NC.POOL_NAME
FROM USUARIOS U, VISP V, SERVICIOS S, VISP_SERVIC
IOS VS, NAS_CALIDAD NC WHERE U.VISP_CODIGO = V.VISP_CODIGO AND U.SER_CODIGO =
S.SER_CODIGO AND VS.VISP_CODIGO = V.VISP_CODIGO A
ND VS.SER_CODIGO = S.SER_CODIGO AND U.USU_CODIGO = 'baby' AND U.VISP_CODIGO =
'pert' AND S.CAL_CODIGO = NC.CAL_CODIGO AND NC.NA
S_IDENTIFIER = '200.59.130.83'

Mon Aug  6 11:15:11 2001: DEBUG: Radius::AuthSQL looks for match with
baby@pert
Mon Aug  6 11:15:11 2001: INFO: Access rejected for baby@pert: No such user
Mon Aug  6 11:15:11 2001: DEBUG: Packet dump:
*** Sending to 127.0.0.1 port 33754 
Code:   Access-Reject
Identifier: 190
Authentic:  1234567890123456
Attributes:
Reply-Message = Request Denied
##


El 10 May 2001, a las 11:31, Mike McCauley escribió:

 Hello Mariano,

 Thanks for raising item 2 below.
 It is indeed a bug, which we have now fixed. The problem was that global
 LogFile and Trace parameters would not be effected until after the
 configuration file had been completely read.

 I have attached new files of 3 files required to fix this problem. Perhaps you
 would like to test it?

 The new files are radiusd, Log.pm and ServerConfig.pm.
 We apologise for this problem.
 Please let me know how you go.

 Cheers.

 On May 10,  8:05am, Hugh Irvine wrote:
  Subject: Fwd: (RADIATOR) log files behavior
 
  Mikey -
 
  More on the logging problem.
 
  cheers
 
  Hugh
 
  --  Forwarded Message  --
  Subject: (RADIATOR) log files behavior
  Date: Wed, 9 May 2001 15:00:46 -0300
  From: Mariano Absatz [EMAIL PROTECTED]
  To: Radiator List [EMAIL PROTECTED]
 
 
  Hi,
 
  wrapping up my messages of the last days, I see two (somehow) weird
  things happening with the logs.
 
  1) As I noted in a message exchange with Hugh (cc: the list) a couple of
  weeks ago, AuthLog FILE is not working. The file isn't created at all
  (and Radiator has sufficient permissions since a Log FILE in the same
  directory

Re: (RADIATOR) log files behavior

2001-05-10 Thread Mariano Absatz

El 10 May 2001, a las 10:25, Hugh Irvine escribió:

 
 Hello Mariano -
 
 Is the problem with AuthLog just because you are only logging failures (the 
 default)?
Nope... it's logging both (it is so set in the config file that I 
attached to the other message)... and besides, I'm also radpwtsting with 
wrong passwords... I get the rejections, but the file still isn't being 
created (what an awful construction in English... I have to stop using so 
many passive constructions :-)

 
 Mike is still looking at the Log FILE.
Great!

 
 regards
 
 Hugh
 
 On Thursday 10 May 2001 04:00, Mariano Absatz wrote:
  Hi,
 
  wrapping up my messages of the last days, I see two (somehow) weird
  things happening with the logs.
 
  1) As I noted in a message exchange with Hugh (cc: the list) a couple of
  weeks ago, AuthLog FILE is not working. The file isn't created at all
  (and Radiator has sufficient permissions since a Log FILE in the same
  directory IS created.
 
  2) It seems there is a different behavior between the global LogFile and
  the Log FILE.
 
  I usually have Log FILE somehow fixed in the standard production
  logging level (usually 2 or 3, depending on our customer desires), and
  the global Trace set to 0. When I want to do some debugging, I change the
  global trace to 4 and check the global LogFile.
 
  However, when an error is produced while Radiator is starting (like, for
  instance the Oracle error I get when I do a kill -HUP, the global log
  goes to %L/logfile... (btw LogDir is not /var/log/radius, so it's not
  the default)... also, LogFile is set just below LogDir, so variable is
  already setup (since the log goes to $LogDir/logfile and not to
  /var/log/radius/logfile.
 
 
 
 
  ===
  Archive at http://www.open.com.au/archives/radiator/
  Announcements on [EMAIL PROTECTED]
  To unsubscribe, email '[EMAIL PROTECTED]' with
  'unsubscribe radiator' in the body of the message.
 
 -- 
 Radiator: the most portable, flexible and configurable RADIUS server 
 anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
 -
 Nets: internetwork inventory and management - graphical, extensible,
 flexible with hardware, software, platform and database independence.
 ===
 Archive at http://www.open.com.au/archives/radiator/
 Announcements on [EMAIL PROTECTED]
 To unsubscribe, email '[EMAIL PROTECTED]' with
 'unsubscribe radiator' in the body of the message.


===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



(RADIATOR) Log files

2000-09-07 Thread Gordon L. Foster



I have a user who 
for some reason skips being logged to the log files. I am running a failed 
attempt log, a detail log, and a password log. They appear in the detail log but 
for some reason they seem to slide between the cracks in the passlog. I show the 
users who log in before and after just not them for some reason. Anybody else 
experience this?
Gordon L. Foster System Administrator OTZ Telephone Cooperative, INC. Ph. 
907-442-3114 Fax 907-442-2123 



Re: (RADIATOR) Log files

2000-09-07 Thread Hugh Irvine


Hello Gordon -

I will need to see a copy of your configuration file (no secrets) together with
a trace 4 debug showing what is happening.

thanks

Hugh


On Fri, 08 Sep 2000, Gordon L. Foster wrote:
 
 I have a user who for some reason skips being logged to the log files. I am
 running a failed attempt log, a detail log, and a password log. They appear
 in the detail log but for some reason they seem to slide between the cracks
 in the passlog. I show the users who log in before and after just not them
 for some reason. Anybody else experience this?
 Gordon L. Foster
 System Administrator
 OTZ Telephone Cooperative, INC.
 Ph. 907-442-3114
 Fax 907-442-2123
 
 
 


Content-Type: text/html; name="unnamed"
Content-Transfer-Encoding: quoted-printable
Content-Description: 


-- 
Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.



===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.