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,  is not working. The file isn't created at all
> > (and Radiator has sufficient permissions since a  in the same
> > directory IS created.
> >

Today I added an  besides the  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/<225>x%<251><233>:<238><192><220>`<176><12>\<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

Re: Fwd: (RADIATOR) log files behavior

2001-05-14 Thread Mariano Absatz

Hi Mike, 

the last modification you made to ServerConfig.pm worked OK... 


I want to state that I've never got such good and fast response from any 
software company or group, open or close, that, in fact has less delays 
in make repairments than those that I have installing and testing them.



El 11 May 2001, a las 9:21, Mike McCauley escribió:

> Hi Mariano,
> 
> On May 10,  3:19pm, Mariano Absatz wrote:
> > Subject: Re: Fwd: (RADIATOR) log files behavior
> > WOW
> >
> > I call this dedication and prompt response "a damn excelent QoS" :-)
> 
> Thanks for reporting the problem with the patch I sent. I have made another
> change to ServerConfig.pm that will fix that error message.
> 
> I would like to thank you for your patience while we resolved this problem.
> 
> Cheers.
> 
> >
> >
> > 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?
> > OK, it got better, now %L/logfile isn't created AND the info goes to the
> > correct file, after a reload (kill -HUP) and even after a fresh start.
> >
> > But now, in the LogFile (not in the ) I see, everytime it's
> > started or reloaded (i.e. by means of a kill -HUP), there is a line
> > telling me that 'LogFile' is an unknown keyword:
> >
> > Thu May 10 15:04:50 2001: NOTICE: SIGHUP received: restarting
> > Thu May 10 15:04:50 2001: ERR: Unknown keyword 'LogFile' in
> > /app/Radiator/etc/radius-common.cfg line 17
> > Thu May 10 15:04:50 2001: INFO: Server started: Radiator 2.18.1 on mr-visp
> > Thu May 10 15:06:34 2001: NOTICE: SIGTERM received: stopping
> > Thu May 10 15:06:36 2001: ERR: Unknown keyword 'LogFile' in
> > /app/Radiator/etc/radius-common.cfg line 17
> > Thu May 10 15:06:37 2001: INFO: Server started: Radiator 2.18.1 on mr-visp
> > Thu May 10 15:06:39 2001: NOTICE: SIGHUP received: restarting
> > Thu May 10 15:06:40 2001: ERR: Unknown keyword 'LogFile' in
> > /app/Radiator/etc/radius-common.cfg line 17
> >
> >
> > Note that in  it doesn't happen:
> > Thu May 10 15:04:50 2001: NOTICE: SIGHUP received: restarting
> > Thu May 10 15:04:50 2001: INFO: Server started: Radiator 2.18.1 on mr-visp
> > Thu May 10 15:06:34 2001: NOTICE: SIGTERM received: stopping
> > Thu May 10 15:06:37 2001: INFO: Server started: Radiator 2.18.1 on mr-visp
> > Thu May 10 15:06:39 2001: NOTICE: SIGHUP received: restarting
> >
> >
> > The config files are the same I sent you on Tuesday.
> > >
> > > The new files are radiusd, Log.pm and ServerConfig.pm.
> > > We apologise for this problem.
> > > Please let me know how you go.
> > This I'm doing right now :-)
> >
> > >
> > > 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,  is not working. The file isn't created at all
> > > > (and Radiator has sufficient permissions since a  in the same
> > > > directory IS created.
> > > >
> > > > 2) It seems there is a different behavior between the global LogFile and
> > > > the .
> > > >
> > > > I usually have  somehow "fixed" in the standard "producti