Mailing List Archive


Back to the month index Back to the list index
Bill Wilson (atijapan@gol.com)
Sat, 21 Sep 1996 11:36:35 +0900 (JST) 

Date: Sat, 21 Sep 1996 11:36:35 +0900 (JST)
Message-Id: <199609210236.LAA08135@gol1.gol.com>
From: Bill Wilson <atijapan@gol.com>
Subject: Re: [mSQL] Newbe - wdb/w3-msql permission denied error

<REPOST>

> Date: Fri, 13 Sep 1996 12:57:54
> To:msql-list@bunyip.com
> From:Bill Wilson <atijapan@gol.com>
> Subject:Re: [mSQL] Newbe - wdb/w3-msql permission denied error
>

Thanks for the suggestions.

First, as per your (Glen's) suggestion, I set my path so I no longer need to
 do "./" to invoke the msql command from shell. This worked, THANKS:) Next,
 I checked my Makefile for w3-msql to see whether I was using my installatio
ns LIB and INC rather than the root system's, and confirmed that w3-msql was
 compiled referencing my installation of msql.

Here's the flow of my debugging labors:

1) decided for debugging purposes to give up on WDB for now, since this reli
es on msqlperl and could complicate things.
2) with some help from my system admin, I had the root version altered so I
could use it from a different account on the same system, thus allowing my t
o see whether the problem is with the way I have w3-msql set up, rather than
 the msql settings themselves.
3) confirmed that all msql functions work from shell on the new account.
4) installed w3-msql on the new account based on the root installation of msql
5) tried sample.html and bookmarks demo, both the former yielding "malformed
 header" error from httpd, and the later giving me a strange "@q1.0"> output
 with link buttons non-functional.

The error signals in "5)" above are the exact problems that are occuring wit
h "my" installation of msql/w3-msql, so I have failed to diagnose whether th
is is a connection problem from "www" to msql or just me being careless on t
he installation of w3-msql. So, looking into the mail-list archives, I foun
d some of the same problems (httpd erroe on w3-msql) listed without clear so
lutions, so I decided to try another msql interface.

Thus, I did the following:
1) downloaded websql
2) installed on the new account
3) fired it up - bingo, got the connection

4) installed websql on the server with "my" installation of msql, double che
cking paths making sure the Makefile is not referencing the root msql
5) compiled nicely
6) fired it up - boooo, got "Couldn't connect to engine! Can't connect to lo
cal MSQL server " error.

Which tells me I have a problem connecting to my installation of msql. Again
, I rechecked my acl file, which is as follows for test:

database=test
read=*
write=*
host=*
access=local,remote

(I also tried with no entry for "test", which I believe gives anybody permis
sions to do anything with the db??).

Atleast now I know for sure I have a problem with connecting from www and no
t a config problem with the interface (websql). Any other suggestions on how
 I might solve this problem would be greatly appriciated.

Thanks,
Bill
> At 08:05 96/09/11 -0500, you wrote:
> > Hi,
> >
> > These may all be obvious to you already, but here are a few
> > thoughts, in case they might help.
> >
> > You can make a simple "relshow", "msql", etc. call your version
> > rather than the root installation in several ways: You could
> > set your $PATH so that your msql area appears before the root
> > one. You could define aliases for the relevant commands, that
> > invoke your versions.
> >
> > When your HTML page invokes w3-msql, it will use whichever msql
> > the w3-msql in your CGI area was compiled with. If there's
> > already a "w3-msql" there from the root installation, you might
> > need to compile your own and name it "w3-msql_c" or something,
> > and then use that name in the links on your HTML pages.
> >
> > I've never used WDB, but I assume that it also gets compiled/
> > linked/whatever with a particular installation of msql, so that
> > you'd need to recompile your own WDB, referring to your msql.
> >
> > You don't say what kind of CGI scripts you're using, but if they
> > are in C or perl or etc., again you'd need to make sure that they
> > (or your msqlperl) got linked to your msql.
> >
> > Apologies if you've already been through the above. Good luck,
> > Glenn
> >
> >
> > >Been fighting this problem for over a month, and now posting on the mai
l list.
> > >
> > >I have installed msql on a server (bsdi/NCSA) for which I do not have r
oot p
> > >ermissions. msql is running as:
> > >% cd usr/local/etc/httpd/msql/bin
> > >% ./msqladmin version
> > >Version Details :-
> > >
> > > msqladmin version 1.0.10
> > > mSQL connection Localhost via UNIX socket
> > > mSQL server version 1.0.10
> > > mSQL protocol version 6
> > > mSQL TCP socket 4333
> > > mSQL UNIX socket /tmp/msql.sock
> > > mSQL root user connpro
> > >
> > >There is another msql installation running on the same host as:
> > >%msqladmin version
> > >Version Details :-
> > >
> > > msqladmin version 1.0.14
> > > mSQL connection localhost via TCP/IP
> > > mSQL server version 1.0.14
> > > mSQL protocol version 6
> > > mSQL TCP socket 1112
> > > mSQL UNIX socket /dev/msql
> > > mSQL root user root
> > >
> > >I can do simple manipulations in shell to the ordinary user "connpro" i
nstal
> > >lation of msql by entering the dir where the msql exe's reside by typin
g "./
> > >***" at the command prompt (for instance "./relshow test") The same com
mand
> > >without the "./" calls on the "root" installation of msql and thus give
s an
> > >"Access to database denied". The access denied problem also occurs when
 usin
> > >g cgi scripts to access the db, as they seem to be calling on the root
intal
> > >lation rather than the user installation?? The particular scripts I am
using
> > > are WDB and w3-msql. I have the acl permissions set to allow anyone, a
nd th
> > >eir family, access the db.
> > >
> > >Is there anyway to check which installation WDB or w3-msql is calling?
Am I
> > >completely off track this problem? I have done just about everything I
can t
> > >hink of and haven't found a solution so far. Any point in the right dir
ectio
> > >n would be greatly appreciated.
> > >
> > >Bill Wilson
> >
> >
>

--------------------------------------------------------------------------
To remove yourself from the Mini SQL mailing list send a message containing
"unsubscribe" to "unsubscribe" to msql-list-request@bunyip.com. Send a message containing
"info msql-list" to majordomo@bunyip.com for info on monthly archives of
the list. For more help, mail owner-msql-list@bunyip.com NOT the msql-list!