(RADIATOR) Perl error connecting mysql

[Terry Simons]

I probably don't know enough about MySQL to answer this, but it looks 
like the MySQL server you are trying to connect to is requesting some 
form of authentication that your client can not perform.

Try connecting manually to the database with the "mysql" command and 
see if that works.  If you can't get that to work, then you won't be 
able to get Radiator working with things, most likely.

I have MySQL connections working for logging purposes, and I've never 
had this sort of issue, but the error message you get specifically 
states that your client doesn't appear to be supporting the required 
authentication mechanisms and recommends upgrading MySQL.

- Terry

On Dec 29, 2004, at 6:41 PM, Adrian Tan wrote:

> Hi ,
>  I am a newbie in installing the Radiator.
>
> Currently I am trying to get Radiator to work with mysql.
>
> Anyone can help me ?
>
> Regards,
>  Adrian
>
> DBI connect('surf2fun','radius',...) failed: Client does not support 
> authenticatio
>  n protocol requested by server; consider upgrading MySQL client at 
> C:/Perl/site/
>  lib/Radius/SqlDb.pm line 110
>  Thu Dec 30 09:33:11 2004: ERR: Could not connect to SQL database with 
> DBI->conne
>  ct dbi:mysql:surf2fun, radius, surffun:  Client does not support 
> authentication p
>  rotocol requested by server; consider upgrading MySQL client
>  Thu Dec 30 09:33:11 2004: ERR: Could not connect to any SQL database. 
> Request is
>   ignored. Backing off for 600 seconds
>
> My config file.
>  # common-sql.cfg
>  #
>  # Example Radiator configuration file that allows you to
>  # authenticate from an SQL database.
>  # With Radiator you can interface with almost any databse schema,
>  # and there are many more configurable parameters that allow you
>  # to control database fallback, select statements, column names
>  # and arrangements etc etc etc.
>  # See the reference manual for more details.
>  # This is a very simple exmaple to get you started. It will
>  # work with the tables created by the goodies/*.sql scripts.
>  #
>  # You should consider this file to be a starting point only
>  # $Id: sql.cfg,v 1.9 2004/10/04 10:35:03 mikem Exp $
>
> Foreground
>  LogStdout
>  LogDir          c:/Program Files/Radiator
> DbDir           c:/Program Files/Radiator
> Trace           4
>
> # You will probably want to change this to suit your site.
>  <Client DEFAULT>
>          Secret  mysecret
>          DupInterval 0
>  </Client>
>
> # You can put client details in a database table
>  # and get their details from there with something like this:
>  <ClientListSQL>
>                 DBSource    dbi:mysql:surf2fun
>                 DBUsername  radius
>                  DBAuth  surffun
>          # If RefreshPeriod is set to non-zero, it specifies the 
> period in seconds that the client list will
>          # be refreshed by rereading the database. Each RefreshPeriod 
> the previous client list
>          # is cleared and a new list of clients read from the database
>          # The same effect can be got by signalling the process with 
> with SIGHUP
>          #RefreshPeriod 600
>  </ClientListSQL>
>
> # This will authenticate users from SUBSCRIBERS
>  <Realm DEFAULT>
>      <AuthBy SQL>
>          # Adjust DBSource, DBUsername, DBAuth to suit your DB
>
>         DBSource    dbi:mysql:surf2fun
>         DBUsername  radius
>          DBAuth  surffun
>
>         # You may want to tailor these for your ACCOUNTING table
>          # You can add your own columns to store whatever you like
>          AccountingTable ACCOUNTING
>          AcctColumnDef   USERNAME,User-Name
>          AcctColumnDef   TIME_STAMP,Timestamp,integer
>         AcctColumnDef   ACCTSTATUSTYPE,Acct-Status-Type
>          AcctColumnDef   ACCTDELAYTIME,Acct-Delay-Time,integer
>         AcctColumnDef   ACCTINPUTOCTETS,Acct-Input-Octets,integer
>         AcctColumnDef   ACCTOUTPUTOCTETS,Acct-Output-Octets,integer
>         AcctColumnDef   ACCTSESSIONID,Acct-Session-Id
>          AcctColumnDef   ACCTSESSIONTIME,Acct-Session-Time,integer
>         AcctColumnDef   ACCTTERMINATECAUSE,Acct-Terminate-Cause
>          AcctColumnDef   NASIDENTIFIER,NAS-Identifier
>          AcctColumnDef   NASPORT,NAS-Port,integer
>         AcctColumnDef   FRAMEDIPADDRESS,Framed-IP-Address
>
>         # You can arrange to log accounting to a file if the
>          # SQL insert fails with AcctFailedLogFileName
>         # That way you could recover from a broken SQL
>          # server
>          #AcctFailedLogFileName %D/missedaccounting
>
>         # Alternatively, you can arrange to save failed SQL accounting 
> insert queries to a text
>          # file with SQLRecoveryFile
>         SQLRecoveryFile %D/missedaccounting
>
>         # You can run a hook whenever Radiator (re)connects to the 
> database. This
>          # can be useful for doing database-specific config or setup
>          # The hook is called like hook($object, $handle)
>          # $object is the SqlDb object that is doing the connecting,
>          # and $handle is the database handle if the newly connected 
> database
>          # This example shows how to set some connection specific 
> attributes
>          # for Interbase
>          #ConnectionHook sub {$_[1]->func(-access_mode => 
> 'read_write',\
>         #       -isolation_level => 'read_committed',\
>         #       -lock_resolution => 'wait',\
>          #       'ib_set_tx_param')}
>
>     </AuthBy>
>  </Realm>
>
>  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 13084 bytes
Desc: not available
URL: <http://www.open.com.au/pipermail/radiator/attachments/20041229/c4e8b83c/attachment.bin>