[Monetdb-developers] sql.start() is not reconized anymore.....
Dear monetdb developers. After the last update in M5 from Martin I start to have the following problem: Starting program: /net/amelia/export/scratch1/goncalve/MonetDB/monetdb5/bin/mserver5 --dbname=demo --set mapi_port=50000 --dbinit=include\ sql\;\ clients.setTrace\(true\)\;\ sql.start\(\)\; [Thread debugging using libthread_db enabled] [New Thread 46912510627904 (LWP 3435)] !WARNING: GDKlockHome: created directory /ufs/goncalve/scratch/MonetDB/monetdb5/var/MonetDB5/dbfarm/demo/ !WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock. !WARNING: BBPdir: initializing BBP. [New Thread 1082132832 (LWP 3438)] # MonetDB Server v4.99.19 # Copyright (c) 1993-2006 CWI, all rights reserved # Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked # config:/ufs/goncalve/scratch/MonetDB/monetdb5/etc/MonetDB5.conf # dbfarm:/ufs/goncalve/scratch/MonetDB/monetdb5/var/MonetDB5/dbfarm # dbname:demo # Visit http://monetdb.cwi.nl/ for further information [New Thread 1090525536 (LWP 3439)] #MALexception:malInclude:could not open file: sql !ERROR: 'sql.start' undefined in user.main[2] _3:any := sql.start()
I am using M5 development trunk and the same for SQL. This changes related to sql.start() are to be applied in M4 and not in M5, right? Regards, Romulo
Romulo Goncalves wrote:
Dear monetdb developers.
After the last update in M5 from Martin I start to have the following problem: This problem is not (yet) confirmed. mserver5 --dbinit="include sql;sql.start();" seem to work in my setting. An independent confirmation is needed.
Starting program: /net/amelia/export/scratch1/goncalve/MonetDB/monetdb5/bin/mserver5 --dbname=demo --set mapi_port=50000 --dbinit=include\ sql\;\ clients.setTrace\(true\)\;\ sql.start\(\)\; [Thread debugging using libthread_db enabled] [New Thread 46912510627904 (LWP 3435)] !WARNING: GDKlockHome: created directory /ufs/goncalve/scratch/MonetDB/monetdb5/var/MonetDB5/dbfarm/demo/ !WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock. !WARNING: BBPdir: initializing BBP. [New Thread 1082132832 (LWP 3438)] # MonetDB Server v4.99.19 # Copyright (c) 1993-2006 CWI, all rights reserved # Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked # config:/ufs/goncalve/scratch/MonetDB/monetdb5/etc/MonetDB5.conf # dbfarm:/ufs/goncalve/scratch/MonetDB/monetdb5/var/MonetDB5/dbfarm # dbname:demo # Visit http://monetdb.cwi.nl/ for further information [New Thread 1090525536 (LWP 3439)] #MALexception:malInclude:could not open file: sql
!ERROR: 'sql.start' undefined in user.main[2] _3:any := sql.start()
I am using M5 development trunk and the same for SQL. This changes related to sql.start() are to be applied in M4 and not in M5, right?
Regards, Romulo
On 09-11-2006 20:52:18 +0100, Martin Kersten wrote:
Romulo Goncalves wrote:
Dear monetdb developers.
After the last update in M5 from Martin I start to have the following problem: This problem is not (yet) confirmed. mserver5 --dbinit="include sql;sql.start();" seem to work in my setting. An independent confirmation is needed.
Starting program: /net/amelia/export/scratch1/goncalve/MonetDB/monetdb5/bin/mserver5 --dbname=demo --set mapi_port=50000 --dbinit=include\ sql\;\ clients.setTrace\(true\)\;\ sql.start\(\)\; [Thread debugging using libthread_db enabled] [New Thread 46912510627904 (LWP 3435)] !WARNING: GDKlockHome: created directory /ufs/goncalve/scratch/MonetDB/monetdb5/var/MonetDB5/dbfarm/demo/ !WARNING: GDKlockHome: ignoring empty or invalid .gdk_lock. !WARNING: BBPdir: initializing BBP. [New Thread 1082132832 (LWP 3438)] # MonetDB Server v4.99.19 # Copyright (c) 1993-2006 CWI, all rights reserved # Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked # config:/ufs/goncalve/scratch/MonetDB/monetdb5/etc/MonetDB5.conf # dbfarm:/ufs/goncalve/scratch/MonetDB/monetdb5/var/MonetDB5/dbfarm # dbname:demo # Visit http://monetdb.cwi.nl/ for further information [New Thread 1090525536 (LWP 3439)] #MALexception:malInclude:could not open file: sql
This indicates something is wrong unrelated to sql.start(): "sql" can't be included at all. Are you sure SQL was installed properly and all (mod?) paths point into the right directions? I saw some changes recently related to monet_mod_path...
participants (3)
-
Fabian Groffen -
Martin Kersten -
Romulo Goncalves