[RADIATOR] Could not connect to SQL database
Faisal Imtiaz
faisal at snappydsl.net
Wed Nov 16 09:50:31 CST 2011
My apologies about the First section..... (the list email copy came in
delayed).
:(
Faisal Imtiaz
Snappy Internet& Telecom
7266 SW 48 Street
Miami, Fl 33155
Tel: 305 663 5518 x 232
Helpdesk: 305 663 5518 option 2 Email: Support at Snappydsl.net
On 11/16/2011 10:47 AM, Faisal Imtiaz wrote:
> Hi Nuno,
>
> A few pointers for you:-
>
> First of all , the Radiator List serve is setup in such a manner that
> if you don't do a Reply ALL to the email you will only send the email
> to the person and not the list.. (i.e. this email only came to me, did
> not go to the listserve).
>
> If you are running radiator on linux/unix platform, and trying to
> connect to the SQL server running Microsoft SQL, you need to review
> the following for additional config....
>
> http://www.open.com.au/radiator/faq.html#14
>
> If you are looking for more hints... obviously you need to review the
> Radiator Documentation Manual, and also there are good sample files
> located in the goodies directory... see the sample files call
> Emerald or Emerald4..... that is a for a billing system which ran /
> run on Microsoft Platform and uses Microsoft SQL as the backend
> database..
>
> The nice thing about Radiator is that the config file can be
> consistent regardless of what back end is being used for data storage,
> (not withstanding that the data fields structure is the same... for
> the most part your config should be fine.. it may need some minor
> adjustments based on the data structure.
>
> Hope this helps.
>
> Faisal Imtiaz
> Snappy Internet& Telecom
> 7266 SW 48 Street
> Miami, Fl 33155
> Tel: 305 663 5518 x 232
> Helpdesk: 305 663 5518 option 2 Email:Support at Snappydsl.net
>
> On 11/16/2011 10:18 AM, Nuno Marques wrote:
>>
>> After looking around I ended up discovering that I'm actually trying
>> to connect to a Microsoft SQL server and all my research was around
>> mysql.
>>
>> Now I'm almost back to stage zero and many problems/questions arise.
>>
>> Meanwhile the attempts I've done:
>>
>> -Installed DBD module Msql-Mysql-modules as proposed in 26.2 mSQL --
>> manual version 4.9
>>
>> -Ended up discovering that this msql is actually a mini-sql from
>> Hugher and not Microsoft SQL (correct me if I'm wrong)
>>
>> Can you explain me how can I inject accounting from radiator directly
>> into Microsoft SQL server 7.0, can I re-use any code I've proposed
>> below?
>>
>> Thanks in advance,
>>
>> Nuno Marques
>>
>> *From:*Faisal Imtiaz [mailto:faisal at snappydsl.net]
>> *Sent:* terça-feira, 15 de Novembro de 2011 14:56
>> *To:* Nuno Marques
>> *Subject:* Re: [RADIATOR] Could not connect to SQL database
>>
>> Could be a couple of possibilities...
>>
>> First things first, can you connect to the MySql Server from the
>> command line (where Radiator is running ) ?
>>
>> Most likely this is a firewall or connectivity issue ....
>>
>> Regards
>>
>> Faisal Imtiaz
>> Snappy Internet& Telecom
>> 7266 SW 48 Street
>> Miami, Fl 33155
>> Tel: 305 663 5518 x 232
>> Helpdesk: 305 663 5518 option 2 Email:Support at Snappydsl.net <mailto:Support at Snappydsl.net>
>>
>>
>> On 11/15/2011 9:45 AM, Nuno Marques wrote:
>>
>> Hello,
>>
>> I'm trying to store accounting into a SQL daba-base
>> and I'm getting this error:
>>
>> **
>>
>> *Tue Nov 15 14:19:32 2011: ERR: Could not connect to SQL database
>> with DBI->connect dbi:mysql:Accounting:192.168.69.222, xxxx, xxxx:*
>>
>> *Tue Nov 15 14:19:32 2011: ERR: Could not connect to any SQL
>> database. Request is ignored. Backing off for 600 seconds*
>>
>> **
>>
>> Radiator doesn't even try to reach the data-base IP address (sniffed
>> the traffic to confirm this).
>>
>> I've no idea what's wrong, all looks fine. Any help is greatly
>> appreciated.
>>
>> Thanks in advance,
>>
>> Nuno Marques
>>
>> **
>>
>> *radius.cfg:*
>>
>> LogDir /var/log/radius
>>
>> DbDir /etc/radiator/
>>
>> Trace 4
>>
>> AuthPort 1812
>>
>> AcctPort 1813
>>
>> <Client 10.240.1.1>
>>
>> Secret xxxxxxxxxxxxxxxxxxxxxxxx
>>
>> </Client>
>>
>> <AuthBy RADIUS>
>>
>> Identifier PEAP_IAS
>>
>> Secret xxxxxxxxxxx
>>
>> AuthPort 1812
>>
>> AcctPort 1813
>>
>> Retries 3
>>
>> SSLeayTrace 4
>>
>> Host ubidc1.ubi.pt
>>
>> </AuthBy>
>>
>> <AuthBy SQL>
>>
>> Identifier SQLAccounting
>>
>> DBSource dbi:mysql:Accounting:192.168.69.222
>>
>> DBUsername xxxx
>>
>> DBAuth xxxxx
>>
>> IgnoreAuthentication
>>
>> AuthSelect
>>
>> AccountingTable Accounting-table
>>
>> HandleAcctStatusTypes Start,Stop
>>
>> #Just putting something into the DB
>>
>> AcctColumnDef Nome, User-Name
>>
>> </Authby>
>>
>> <Handler Realm=/ubi.pt/i>
>>
>> AuthByPolicy ContinueAlways
>>
>> AuthBy SQLAccounting
>>
>> AuthBy PEAP_IAS
>>
>> </Handler>
>>
>> *_Logfile:_*
>>
>> Tue Nov 15 14:19:32 2011: ERR: Attribute number 1 (vendor 52) is not
>> defined in your dictionary
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: Packet dump:
>>
>> *** Received from 10.240.1.1 port 20009 ....
>>
>> Code: Accounting-Request
>>
>> Identifier: 15
>>
>> Authentic: <<235><173>x<164><226>d<193><171><168>0<239>)<240>g&
>>
>> Attributes:
>>
>> Acct-Status-Type = Stop
>>
>> Acct-Authentic = RADIUS
>>
>> Acct-Multi-Session-Id = "SESS-63907-d2d8d0-365628-402"
>>
>> Acct-Session-Id = "SESS-63907-d2d8d0-365628-402"
>>
>> User-Name = "xxxxxx at ubi.pt" <mailto:xxxxxx at ubi.pt>
>>
>> Event-Timestamp = 1321366775
>>
>> Calling-Station-Id = "00-1C-BF-72-63-92"
>>
>> NAS-Port-Id = "AP7/1"
>>
>> Called-Station-Id = "00-11-88-D2-D9-62:RAD-Test"
>>
>> NAS-Port = 185
>>
>> Framed-IP-Address = 192.168.228.121
>>
>> Class =
>> "l<127><6>F<0><0><1>7<0><1><2><0><192><168>d<1><0><0><0><0><0><0><0><0><0><0><0><0><1><204><159><178><6>2n<159><0><0><0><0><0><18><155>-"
>>
>> Acct-Session-Time = 1146
>>
>> Acct-Output-Octets = 1349445
>>
>> Acct-Input-Octets = 1925391
>>
>> Acct-Output-Packets = 3538
>>
>> Acct-Input-Packets = 13777
>>
>> NAS-Port-Type = Wireless-IEEE-802-11
>>
>> NAS-IP-Address = 10.240.1.1
>>
>> NAS-Identifier = "enterasys"
>>
>> Acct-Delay-Time = 0
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: Handling request with Handler
>> 'Realm=/ubi.pt/i', Identifier ''
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: Deleting session for
>> nmarques at ubi.pt <mailto:nmarques at ubi.pt>, 10.240.1.1, 185
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: Handling with Radius::AuthSQL:
>> SQLAccounting
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: Handling accounting with Radius::AuthSQL
>>
>> *Tue Nov 15 14:19:32 2011: ERR: Could not connect to SQL database
>> with DBI->connect dbi:mysql:Accounting:192.168.69.222, xxxx, xxxx:*
>>
>> *Tue Nov 15 14:19:32 2011: ERR: Could not connect to any SQL
>> database. Request is ignored. Backing off for 600 seconds*
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: do query is: 'insert into
>> Accounting-table (Nome) values ()':
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: AuthBy SQL result: IGNORE, Database
>> failure
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: Handling with Radius::AuthRADIUS
>>
>> Tue Nov 15 14:19:32 2011: DEBUG: Packet dump:
>>
>> ------------------------------------------------------------------------
>>
>>
>> UBI amiga do ambiente: Antes de imprimir este e-mail pense bem se tem
>> mesmo que o fazer. As árvores são um bem imprescindível.
>>
>>
>>
>> _______________________________________________
>> radiator mailing list
>> radiator at open.com.au <mailto:radiator at open.com.au>
>> http://www.open.com.au/mailman/listinfo/radiator
>>
>> ------------------------------------------------------------------------
>>
>> UBI amiga do ambiente: Antes de imprimir este e-mail pense bem se tem
>> mesmo que o fazer. As árvores são um bem imprescindível.
>
>
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open.com.au/pipermail/radiator/attachments/20111116/7b67b767/attachment-0001.html
More information about the radiator
mailing list