>
>Hello Danny -
>
>On Tue, 01 Feb 2000, Danny Whitesel wrote:
>> Is anyone here using Radiator under Linux and Authby RODOPI? More to the
>> point, has anyone successfuly hooked up to a MS SQL database using
>> DBD::Sybase???
>>
>> I have installed the Sybase client libraries. I have compiled the
DBD_Sybase
>> package. I have edited the "interfaces" file in the Sybase directory:
>>
>> ---
>> MAIL1
>> query tcp eth0 209.96.160.15 1433
>> master tcp eth0 209.96.160.15 1433
>> ---
>>
>> I have set the envs SYBASE, DSQUERY and SYBPLATFORM.
>>
>> ...And, this is what gets kicked back at me when I try to connect:
>>
>> connection to database failed: DBI->connect failed: OpenClient message:
>> LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
>> Message String: ct_connect(): network packet layer: internal net library
>> error: Net-Lib protocol driver call to connect two endpoints failed
>> Operating System Error: Socket connect failed - errno 111
>>
>> I'm pretty certain that it's reading the interfaces file. I had attempted
a
>> few connects before setting up the interfaces file and the errors were
>> indicating that it couldn't find the server name. After creating the
above
>> entry in the interfaces file, the errors changed to what you see above.
>>
>
>Have you installed the latest DBI? What version of Radiator are you
running?
>Have you set the DBI_TRACE environment variable to get more detailled
>information from DBI? If all of the above, can you send me a copy of your
>configuration file (no secrets) and a trace 4 debug and I 'll have a look
at it.
>
>Also have a look at the sample radius.cfg file in the main Radiator
directory
>and at the examples in goodies/rodopi.cfg and goodies/sql.cfg.
At this point, Hugh, it's not yet even a Radiator config issue. It's a
DBB::Sybase connecting to our MS SQL server issue. We are running DBI v1.13.
Following is a little snippet of code I whipped up to test the connection:
---
#!/usr/bin/perl -w
use DBI;
# eval { $dbh->ping };
eval { DBI->trace(4) };
if ($@) {
print "DBI->trace failed: $@";
}
eval { $dbh = DBI->connect("DBI:Sybase:server=MAIL1", "user", "passwd",
{RaiseError => 1}) };
if ($@) {
print "connection to database failed: $@";
}
exit 0;
---
Here are the results:
---
DBI 1.13-nothread dispatch trace level set to 4
-> DBI->connect(DBI:Sybase:server=MAIL1, user, passwd, HASH(0x80c3124))
-> DBI->install_driver(Sybase) for perl=5.00503 pid=24141 ruid=500
euid=500
syb_init() -> DBD::Sybase 0.21 initialized
OpenClient version: Sybase Client-Library/11.1.1/P/Linux Intel/Linux
2.2.5 i586/1/OPT/Mon Jun 7 07:50
:21 1999
install_driver: DBD::Sybase loaded (version 0.21)
New DBI::dr (for DBD::Sybase::dr, parent=, id=)
dbih_setup_handle(DBI::dr=HASH(0x81359e8)=>DBI::dr=HASH(0x8173658),
DBD::Sybase::dr, 0, Null!)
dbih_make_com(Null!, DBD::Sybase::dr, 84)
<- install_driver= DBI::dr=HASH(0x81359e8)
-> connect for DBD::Sybase::dr (DBI::dr=HASH(0x81359e8)~0x8173658
'server=MAIL1' 'user' 'passwd' HASH(
0x8115a14))
New DBI::db (for DBD::Sybase::db, parent=DBI::dr=HASH(0x8173658), id=)
dbih_setup_handle(DBI::db=HASH(0x81735bc)=>DBI::db=HASH(0x8173610),
DBD::Sybase::db, 8133218, Null!)
dbih_make_com(DBI::dr=HASH(0x8173658), DBD::Sybase::db, 1712)
!! ERROR: 4 'OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5)
NUMBER = (4)
Message String: ct_connect(): network packet layer: internal net library
error: Net-Lib protocol driver ca
ll to connect two endpoints failed
Operating System Error: Socket connect failed - errno 111
'
<- connect= undef at DBI.pm line 382.
-> errstr in DBD::_::common for DBD::Sybase::dr
(DBI::dr=HASH(0x81359e8)~0x8173658)
<- errstr= 'OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5)
NUMBER = (4)
Message String: ct_connect(): network packet layer: internal net library
error: Net-Lib protocol driver ca
ll to connect two endpoints failed
Operating System Error: Socket connect failed - errno 111
' at DBI.pm line 383.
<> DESTROY ignored for outer handle DBI::db=HASH(0x81735bc) (inner
DBI::db=HASH(0x8173610))
-> DESTROY for DBD::Sybase::db (DBI::db=HASH(0x8173610)~INNER)
DESTROY for DBI::db=HASH(0x8173610) ignored - handle not
initialised
<- DESTROY= undef at sytest line 16.
dbih_clearcom 0x81735bc (com 0x818fb48, type 2) done.
connection to database failed: DBI->connect failed: OpenClient message:
LAYER = (5) ORIGIN = (3) SEVERITY
= (5) NUMBER = (4)
Message String: ct_connect(): network packet layer: internal net library
error: Net-Lib protocol driver ca
ll to connect two endpoints failed
Operating System Error: Socket connect failed - errno 111
at ./sytest line 14
-> DBI::END
-> disconnect_all for DBD::Sybase::dr
(DBI::dr=HASH(0x81359e8)~0x8173658)
<- disconnect_all= 1 at DBI.pm line 424.
<- DBI::END complete
-> DESTROY in DBD::_::common for DBD::Sybase::dr
(DBI::dr=HASH(0x8173658)~INNER)
<- DESTROY= undef during global destruction.
dbih_clearcom 0x81359e8 (com 0x810c4d8, type 1) done.
<> DESTROY for DBI::dr=HASH(0x81359e8) ignored (inner handle gone)
---
Of course, "user" and "passwd" have been put in place of the actual user and
password for the test database I'm trying to connect to. If I've overlooked
any and the real u/p is in there anywhere, don't anyone waste their time
trying to connect to it. It's just an empty database, anyway.
What's interesting is that I did a full TCP port scan of our MS SQL server.
Port 1433 did not appear in the list of open ports. hmmmmmm... Does this
smell of an issue at the MS SQL server or is it just me?
-Danny
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
