Mailing List Archive


Back to the month index Back to the list index
David J. Hughes (bambi@Hughes.com.au)
Tue, 20 Apr 1999 09:08:00 +1000 (EST) 

Date: Tue, 20 Apr 1999 09:08:00 +1000 (EST)
From: "David J. Hughes" <bambi@Hughes.com.au>
Subject: Re: Socket error
Message-ID: <Pine.BSF.3.96.990420090515.7583B-100000@fawn.Hughes.com.au>

On Mon, 19 Apr 1999, Rutger Wessels wrote:

> ERROR:Can't connect to MSQL server on odur.let.rug.nl
> Socket read on -1 for length failed : Bad file number

This implies that the socket isn't valid. Do you check the return value
of msqlConnect() in your code? Looks like it's failing as the socket
value is -1.

> The error occurs when running the script over the web and when running
> as a standalone lite script. The scripts used to run fine.
>
> Our operating system is HP-UX 10.20. We upgraded from msql 2.0.4.

In 2.0.4, the server by default allowed connections from remote machines.
In 208 and 209 it isn't. If you _must_ use a remote connection (i.e. if
the server is not on the local machine) edit the config file and set
Remote_Access=True.

If it's on the same machine then check your args to msqlConnect(). In C
use an arg of NULL, in Lite use no arg at all. That will tell it to use a
local connecton that bypasses the TCP code. It's much faster and also
allows you to refuse remote connection attempts (for security reasons).

Bambi
...