[MonetDB-users] Trouble connecting
Hi everybody, I am completely new to MonetDB and have just compiled the latest SuperBall release on OS X. I set mapi_open to true in the config file /etc/monetdb5.conf because for some reason MonetDB would not use "localhost" but the machine name of my box as an address to listen on. I had to manually add that to /etc/hosts in order for it to refer to 127.0.0.1 at least. Maybe an OS X oddity. I start the merovingian process which seems to run fine. After that the only time I can connect successfully to a database using mclient (or any other client) is the first time I try to connect (if it works at all). For example ./mclient -lsql --database demo !InvalidCredentialsException:checkCredentials:Invalid credentials for user 'monetdb' Sometimes it would work just once but the second time with the same command line I would not be able to log in. The merovingian.log does not seem to contain any helpful messages. Any hints would be very helpful as currently I can not use MonetDB at all. Cheers, Richard
Hi Richard, On 14-03-2008 12:06:11 -0300, Richard Eckart wrote:
I start the merovingian process which seems to run fine. After that the only time I can connect successfully to a database using mclient (or any other client) is the first time I try to connect (if it works at all). For example
./mclient -lsql --database demo !InvalidCredentialsException:checkCredentials:Invalid credentials for user 'monetdb'
I've seen this too, and I'm out of clues as to why actually. It is the mserver5 process that denies you access, but it is inconsistent as in why, and our testing environment isn't affected by it either...
Hi, I am having more trouble here on OS X. Like when I try to run a the simple test.xq (1, 42.0, "Hello World", <node attr="value">test</node>) mclient -lx test.xq then the MServer will go into 100% CPU load and never come back. I compiled MonetDB on another machine under Debian and there it works fine. I am now in the process of recompiling MonetDB without optimization on OS X and without the SQL server just to see if that makes a difference. I can run the database test-wise on the Linux machine, but as it stands half a world a way and my internet connection is not really fast, I would prefer a local solution. Another question just to clear up my understanding: If I want to use XQuery, I need to run MServer and if I want to use SQL I need to run mserver5, right? That is I cannot have a single server instance (and single database) that servers SQL as well as XQuery - or am I misunderstanding? Cheers, Richard Am 14.03.2008 um 13:00 schrieb Fabian Groffen:
Hi Richard,
On 14-03-2008 12:06:11 -0300, Richard Eckart wrote:
I start the merovingian process which seems to run fine. After that the only time I can connect successfully to a database using mclient (or any other client) is the first time I try to connect (if it works at all). For example
./mclient -lsql --database demo !InvalidCredentialsException:checkCredentials:Invalid credentials for user 'monetdb'
I've seen this too, and I'm out of clues as to why actually. It is the mserver5 process that denies you access, but it is inconsistent as in why, and our testing environment isn't affected by it either...
---------------------------------------------------------------------- --- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On 14-03-2008 13:27:30 -0300, Richard Eckart wrote:
Hi,
I am having more trouble here on OS X. Like when I try to run a the simple test.xq
(1, 42.0, "Hello World", <node attr="value">test</node>)
mclient -lx test.xq
then the MServer will go into 100% CPU load and never come back. I compiled MonetDB on another machine under Debian and there it works fine. I am
Can you try just giving returns on the MonetDB> prompt while this happens?
now in the process of recompiling MonetDB without optimization on OS X and without the SQL server just to see if that makes a difference.
The SQL part /should/ not differ in any case.
I can run the database test-wise on the Linux machine, but as it stands half a world a way and my internet connection is not really fast, I would prefer a local solution.
Another question just to clear up my understanding: If I want to use XQuery, I need to run MServer and if I want to use SQL I need to run mserver5, right? That is I cannot have a single server instance (and single database) that servers SQL as well as XQuery - or am I misunderstanding?
For SQL connections, you best run merovingian (which in turn runs mserver5), XQuery indeed only runs on the old MonetDB 4 engine. Perhaps you could configure XQuery to use port 50001, such that 50000 is sql, and 50001 is xquery.
Hi, Thanks for the swift replies!
then the MServer will go into 100% CPU load and never come back. I compiled MonetDB on another machine under Debian and there it works fine. I am
Can you try just giving returns on the MonetDB> prompt while this happens?
I did try this and the prompt did still react. I even could enter commands like "clients()" or "threads()" to see the thing is still alive. For the "clients()" command I got a list of all open connections four of which seemed to be from MServer itself running under the user "adm" and one seemed to be from the connecting client. For this one the last column of the table was simply "" (empty). Unfortunately I now deleted the compiled MonetDB to have space to compile again without fear of running out of disk space. I can try again as soon as the compiling is done and it still does not work. Cheers, Richard
Hi again, so I recompiled without optimizations and SQL. The 100% CPU load got away, but still I do not get any results: I start up MServer: $ ./Mserver --dbinit="module(pathfinder);" !WARNING: GDKlockHome: created directory /Users/bluefire/MonetDB/var/ MonetDB4/dbfarm/demo/ !WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock. !WARNING: BBPdir: initializing BBP. # MonetDB Server v4.22.0 # based on GDK v1.22.0 # Copyright (c) 1993-2008, CWI. All rights reserved. # Compiled for powerpc-apple-darwin8.11.0/32bit with 32bit OIDs; dynamically linked. # Visit http://monetdb.cwi.nl/ for further information. # PF/Tijah module v0.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah # MonetDB/XQuery module v0.22.0 loaded # XRPC administrative console at http://127.0.0.1:50001/admin MonetDB> On another terminal I run a simple test: $ cat > test.xq (1, 42.0, "Hello World", <node attr="value">test</node>) $ ./mclient -lx test.xq _ (blink blink blink ...) and there it hangs. So I go back to the server to see what's up. I tried the "threads()" and "clients()" commands. Well, to me all looks fine except that the "monetdb" client does not seem to have actually sent any command (""). Funnily when I got back to the first terminal, the mclient command had completed. So I tried again. It seems that the mclient command will complete as soon as I hit "return" a couple of times on the MonetDB> prompt. The same goes for the mjclient command. Ah! A known problem - this is what you had asked me to do in the other mail! Do you have any idea how I can turn this off so it works without me hitting <return>? Cheers, Richard
On 14-03-2008 14:40:42 -0300, Richard Eckart wrote:
Hi again,
so I recompiled without optimizations and SQL. The 100% CPU load got away, but still I do not get any results:
Thanks. This actually is the reason why the monetdb-install script doesn't use optimisations by default. [snip]
It seems that the mclient command will complete as soon as I hit "return" a couple of times on the MonetDB> prompt. The same goes for the mjclient command.
Ah! A known problem - this is what you had asked me to do in the other mail!
Do you have any idea how I can turn this off so it works without me hitting <return>?
Unfortunately not, but it was identified on Leopard 10.5.2 as well recently, and for MonetDB4 alone. We are trying to find a fix for this. Would you please file a bug for this issue, so we can track it?
hello, I witnessed a similar problem yesterday on freebsd (with the Feb2008 release). It was not my computer, and I do not really have more details. somehow (when running Mserver in a shell) setting "deamon=yes" in the MonetDB.conf seemed to help. it doesn't solve the actual problem, but perhaps it might help finding it... ? my2cts, wouter -----Original Message----- From: monetdb-users-bounces@lists.sourceforge.net [mailto:monetdb-users-bounces@lists.sourceforge.net] On Behalf Of Fabian Groffen Sent: vrijdag 14 maart 2008 18:46 To: monetdb-users@lists.sourceforge.net Subject: Re: [MonetDB-users] Trouble connecting On 14-03-2008 14:40:42 -0300, Richard Eckart wrote:
Hi again,
so I recompiled without optimizations and SQL. The 100% CPU load got away, but still I do not get any results:
Thanks. This actually is the reason why the monetdb-install script doesn't use optimisations by default. [snip]
It seems that the mclient command will complete as soon as I hit "return" a couple of times on the MonetDB> prompt. The same goes for the mjclient command.
Ah! A known problem - this is what you had asked me to do in the other mail!
Do you have any idea how I can turn this off so it works without me hitting <return>?
Unfortunately not, but it was identified on Leopard 10.5.2 as well recently, and for MonetDB4 alone. We are trying to find a fix for this. Would you please file a bug for this issue, so we can track it? ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
participants (3)
-
Fabian Groffen -
Richard Eckart -
Wouter Alink