[MonetDB-users] problem after upgrading (probably)
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
greetings,
-- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/
Hi Gijs,
median() is a predefined aggregate function in SQL. You might have to quote it.
regards, Martin
On 05/03/2012 03:13 PM, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
greetings,
-- Gijs Molenaar http://www.astro.uva.nl/people/gijs-molenaar/
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On 05/03/2012 04:11 PM, Martin Kersten wrote:
Hi Gijs,
median() is a predefined aggregate function in SQL. You might have to quote it.
We don't define a median function anywhere. I think the problem is somewhere else. It happens when I alter some auth stuff and then login for the second time, as Bart described. Here is a simple bash script that can reproduce the problem (probably). This is with an empty ~/.monetdb file.
"""
DBNAME="trap" USER="trap" PASSWORD="trap"
monetdb stop ${DBNAME} monetdb destroy -f ${DBNAME} monetdb create ${DBNAME} monetdb start ${DBNAME}
echo "type: monetdb" mclient -d${DBNAME} -umonetdb <<-EOF ALTER USER "monetdb" RENAME TO "${USER}"; ALTER USER SET PASSWORD '${PASSWORD}' USING OLD PASSWORD 'monetdb'; CREATE SCHEMA "${DBNAME}" AUTHORIZATION "${USER}"; ALTER USER "${USER}" SET SCHEMA "${DBNAME}"; EOF
echo "type: trap" mclient -d${DBNAME} -u${USER} <<-EOF EOF
echo "type: trap" mclient -d${DBNAME} -u${USER} <<-EOF EOF
"""
On 2012-05-03 15:13, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
Apparently you already have a function median with a tinyint argument. When upgrading to the Apr2012 release, the server creates a bunch of missing functions, among which a median function with various different argument types. See the monetdbd log where it should tell you the upgrade query that the server attempts to do.
Hi all,
I could reproduce this. After upgrade from Dec2011-SP2 to Apr2012, the first mclient access goes well. I can execute queries and get results. Second attempt gives AGGR error. The database is in another schema than sys, with other than monetdb user/pw.
Cheers Bart
On 03-05-2012 17:39, Sjoerd Mullender wrote:
On 2012-05-03 15:13, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
Apparently you already have a function median with a tinyint argument. When upgrading to the Apr2012 release, the server creates a bunch of missing functions, among which a median function with various different argument types. See the monetdbd log where it should tell you the upgrade query that the server attempts to do.
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On 2012-05-03 21:57, Bart Scheers wrote:
Hi all,
I could reproduce this. After upgrade from Dec2011-SP2 to Apr2012, the first mclient access goes well. I can execute queries and get results. Second attempt gives AGGR error. The database is in another schema than sys, with other than monetdb user/pw.
What does the logfile (merovingian.log) say?
Cheers Bart
On 03-05-2012 17:39, Sjoerd Mullender wrote:
On 2012-05-03 15:13, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
Apparently you already have a function median with a tinyint argument. When upgrading to the Apr2012 release, the server creates a bunch of missing functions, among which a median function with various different argument types. See the monetdbd log where it should tell you the upgrade query that the server attempts to do.
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Attached are the last 50 lines
On 03-05-2012 22:16, Sjoerd Mullender wrote:
On 2012-05-03 21:57, Bart Scheers wrote:
Hi all,
I could reproduce this. After upgrade from Dec2011-SP2 to Apr2012, the first mclient access goes well. I can execute queries and get results. Second attempt gives AGGR error. The database is in another schema than sys, with other than monetdb user/pw.
What does the logfile (merovingian.log) say?
Cheers Bart
On 03-05-2012 17:39, Sjoerd Mullender wrote:
On 2012-05-03 15:13, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
Apparently you already have a function median with a tinyint argument. When upgrading to the Apr2012 release, the server creates a bunch of missing functions, among which a median function with various different argument types. See the monetdbd log where it should tell you the upgrade query that the server attempts to do.
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Sorry, the last 100 lines give a better view.
On 03-05-2012 22:16, Sjoerd Mullender wrote:
On 2012-05-03 21:57, Bart Scheers wrote:
Hi all,
I could reproduce this. After upgrade from Dec2011-SP2 to Apr2012, the first mclient access goes well. I can execute queries and get results. Second attempt gives AGGR error. The database is in another schema than sys, with other than monetdb user/pw.
What does the logfile (merovingian.log) say?
Cheers Bart
On 03-05-2012 17:39, Sjoerd Mullender wrote:
On 2012-05-03 15:13, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
Apparently you already have a function median with a tinyint argument. When upgrading to the Apr2012 release, the server creates a bunch of missing functions, among which a median function with various different argument types. See the monetdbd log where it should tell you the upgrade query that the server attempts to do.
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Hm, looks like a second client connection after an upgrade without restarting teh server tries to do the upgrade actions (e.g., adding new functions), again.
I did not test this with my upgrade tests, I only tested a second client connection after upgrading and restarting the server --- indeed a gap in my testing routine ...
Could you try to stop & restart your server and see whether the problem persists?
Stefan
On Thu, May 03, 2012 at 10:42:09PM +0200, Bart Scheers wrote:
Sorry, the last 100 lines give a better view.
On 03-05-2012 22:16, Sjoerd Mullender wrote:
On 2012-05-03 21:57, Bart Scheers wrote:
Hi all,
I could reproduce this. After upgrade from Dec2011-SP2 to Apr2012, the first mclient access goes well. I can execute queries and get results. Second attempt gives AGGR error. The database is in another schema than sys, with other than monetdb user/pw.
What does the logfile (merovingian.log) say?
Cheers Bart
On 03-05-2012 17:39, Sjoerd Mullender wrote:
On 2012-05-03 15:13, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
Apparently you already have a function median with a tinyint argument. When upgrading to the Apr2012 release, the server creates a bunch of missing functions, among which a median function with various different argument types. See the monetdbd log where it should tell you the upgrade query that the server attempts to do.
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
2012-05-03 21:54:20 MSG merovingian[21195]: monitoring dbfarm /export/scratch2/bscheers/databases/data/dbfarm/ 2012-05-03 21:54:20 MSG merovingian[21195]: accepting connections on TCP socket 0.0.0.0:60000 2012-05-03 21:54:20 MSG merovingian[21195]: accepting connections on UNIX domain socket /tmp/.s.monetdb.60000 2012-05-03 21:54:20 MSG discovery[21195]: listening for UDP messages on 0.0.0.0:60000 2012-05-03 21:54:20 MSG control[21195]: accepting connections on UNIX domain socket /tmp/.s.merovingian.60000 2012-05-03 21:54:20 MSG discovery[21195]: new neighbour napels.ins.cwi.nl (napels.ins.cwi.nl) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/node3db/lightcurve3 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sjoert (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/trap (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/bugs (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/gsm (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/grb2 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/node1db/lightcurve1 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/bell (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/tradb (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/flarestar (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sinterklaas (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sipfull (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/grb (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/testing (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/node2db/lightcurve2 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sip (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sip2full (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/test (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/simlofar (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/simlsst (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/fast (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: registered neighbour napels.ins.cwi.nl:60000 2012-05-03 21:54:30 MSG control[21195]: (local): served status list 2012-05-03 21:54:48 MSG merovingian[21195]: starting database 'bell', up min/avg/max: 27s/49m/2h, crash average: 0.00 0.10 0.03 (5-4=1) 2012-05-03 21:54:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:54:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:54:48 MSG bell[21211]: arguments: /export/scratch2/bscheers/databases/MonetDB-Apr2012/bin/mserver5 --set gdk_dbfarm=/export/scratch2/bscheers/databases/data/dbfarm --dbname=bell --set merovingian_uri=mapi:monetdb://napels.ins.cwi.nl:60000/bell --set mapi_open=false --set mapi_port=0 --set mapi_usock=/export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock --set monet_vault_key=/export/scratch2/bscheers/databases/data/dbfarm/bell/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2012-05-03 21:54:48 MSG bell[21211]: # MonetDB 5 server v11.9.1 "Apr2012" 2012-05-03 21:54:48 MSG bell[21211]: # Serving database 'bell', using 8 threads 2012-05-03 21:54:48 MSG bell[21211]: # Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked 2012-05-03 21:54:48 MSG bell[21211]: # Found 15.629 GiB available main-memory. 2012-05-03 21:54:48 MSG bell[21211]: # Copyright (c) 1993-July 2008 CWI. 2012-05-03 21:54:48 MSG bell[21211]: # Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved 2012-05-03 21:54:48 MSG bell[21211]: # Visit http://www.monetdb.org/ for further information 2012-05-03 21:54:48 MSG bell[21211]: # Listening for UNIX domain connection requests on mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock 2012-05-03 21:54:48 MSG bell[21211]: # MonetDB/GIS module loaded 2012-05-03 21:54:48 MSG bell[21211]: # MonetDB/SQL module loaded 2012-05-03 21:54:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:54:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:54:48 MSG bell[21211]: Running database upgrade commands: 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val TINYINT) returns TINYINT external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val SMALLINT) returns SMALLINT external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val INTEGER) returns INTEGER external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val BIGINT) returns BIGINT external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val REAL) returns REAL external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val DOUBLE) returns DOUBLE external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 TINYINT, e2 TINYINT) returns TINYINT external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 SMALLINT, e2 SMALLINT) returns SMALLINT external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 INTEGER, e2 INTEGER) returns INTEGER external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 BIGINT, e2 BIGINT) returns BIGINT external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 REAL, e2 REAL) returns REAL external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 DOUBLE, e2 DOUBLE) returns DOUBLE external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: insert into sys.systemfunctions (select f.id from sys.functions f, sys.schemas s where f.name in ('median', 'corr') and f.type = 3 and f.schema_id = s.id and s.name = 'sys'); 2012-05-03 21:54:48 MSG bell[21211]: 2012-05-03 21:55:00 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:00 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:00 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:00 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:00 MSG bell[21211]: Running database upgrade commands: 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val TINYINT) returns TINYINT external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val SMALLINT) returns SMALLINT external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val INTEGER) returns INTEGER external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val BIGINT) returns BIGINT external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val REAL) returns REAL external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val DOUBLE) returns DOUBLE external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 TINYINT, e2 TINYINT) returns TINYINT external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 SMALLINT, e2 SMALLINT) returns SMALLINT external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 INTEGER, e2 INTEGER) returns INTEGER external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 BIGINT, e2 BIGINT) returns BIGINT external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 REAL, e2 REAL) returns REAL external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 DOUBLE, e2 DOUBLE) returns DOUBLE external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: insert into sys.systemfunctions (select f.id from sys.functions f, sys.schemas s where f.name in ('median', 'corr') and f.type = 3 and f.schema_id = s.id and s.name = 'sys'); 2012-05-03 21:55:00 MSG bell[21211]: 2012-05-03 21:55:00 ERR bell[21211]: !ParseException:SQLparser:CREATE AGGREGATE: name 'median' (tinyint(8)) already in use 2012-05-03 21:55:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:48 MSG bell[21211]: Running database upgrade commands: 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val TINYINT) returns TINYINT external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val SMALLINT) returns SMALLINT external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val INTEGER) returns INTEGER external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val BIGINT) returns BIGINT external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val REAL) returns REAL external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val DOUBLE) returns DOUBLE external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 TINYINT, e2 TINYINT) returns TINYINT external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 SMALLINT, e2 SMALLINT) returns SMALLINT external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 INTEGER, e2 INTEGER) returns INTEGER external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 BIGINT, e2 BIGINT) returns BIGINT external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 REAL, e2 REAL) returns REAL external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 DOUBLE, e2 DOUBLE) returns DOUBLE external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: insert into sys.systemfunctions (select f.id from sys.functions f, sys.schemas s where f.name in ('median', 'corr') and f.type = 3 and f.schema_id = s.id and s.name = 'sys'); 2012-05-03 21:55:48 MSG bell[21211]: 2012-05-03 21:55:48 ERR bell[21211]: !ParseException:SQLparser:CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Yes, after restart of server it comes back with the same error and I can't get access.
Bart
On 04/05/12 01:12, Stefan Manegold wrote:
Hm, looks like a second client connection after an upgrade without restarting teh server tries to do the upgrade actions (e.g., adding new functions), again.
I did not test this with my upgrade tests, I only tested a second client connection after upgrading and restarting the server --- indeed a gap in my testing routine ...
Could you try to stop& restart your server and see whether the problem persists?
Stefan
On Thu, May 03, 2012 at 10:42:09PM +0200, Bart Scheers wrote:
Sorry, the last 100 lines give a better view.
On 03-05-2012 22:16, Sjoerd Mullender wrote:
On 2012-05-03 21:57, Bart Scheers wrote:
Hi all,
I could reproduce this. After upgrade from Dec2011-SP2 to Apr2012, the first mclient access goes well. I can execute queries and get results. Second attempt gives AGGR error. The database is in another schema than sys, with other than monetdb user/pw.
What does the logfile (merovingian.log) say?
Cheers Bart
On 03-05-2012 17:39, Sjoerd Mullender wrote:
On 2012-05-03 15:13, Gijs Molenaar wrote:
Hi MonetDB people,
greetings from the other side of the street. Long time no see.
I just upgraded my monetdb installation to the April release. I use the Ubuntu repo. my database is running, but when I try to connect with the Python API or mclient I get the error:
CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Any suggestion how to figure out how to solve this problem?
Apparently you already have a function median with a tinyint argument. When upgrading to the Apr2012 release, the server creates a bunch of missing functions, among which a median function with various different argument types. See the monetdbd log where it should tell you the upgrade query that the server attempts to do.
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
2012-05-03 21:54:20 MSG merovingian[21195]: monitoring dbfarm /export/scratch2/bscheers/databases/data/dbfarm/ 2012-05-03 21:54:20 MSG merovingian[21195]: accepting connections on TCP socket 0.0.0.0:60000 2012-05-03 21:54:20 MSG merovingian[21195]: accepting connections on UNIX domain socket /tmp/.s.monetdb.60000 2012-05-03 21:54:20 MSG discovery[21195]: listening for UDP messages on 0.0.0.0:60000 2012-05-03 21:54:20 MSG control[21195]: accepting connections on UNIX domain socket /tmp/.s.merovingian.60000 2012-05-03 21:54:20 MSG discovery[21195]: new neighbour napels.ins.cwi.nl (napels.ins.cwi.nl) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/node3db/lightcurve3 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sjoert (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/trap (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/bugs (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/gsm (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/grb2 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/node1db/lightcurve1 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/bell (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/tradb (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/flarestar (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sinterklaas (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sipfull (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/grb (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/testing (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/node2db/lightcurve2 (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sip (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/sip2full (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/test (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/simlofar (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/simlsst (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: new database mapi:monetdb://napels.ins.cwi.nl:60000/fast (ttl=660s) 2012-05-03 21:54:21 MSG discovery[21195]: registered neighbour napels.ins.cwi.nl:60000 2012-05-03 21:54:30 MSG control[21195]: (local): served status list 2012-05-03 21:54:48 MSG merovingian[21195]: starting database 'bell', up min/avg/max: 27s/49m/2h, crash average: 0.00 0.10 0.03 (5-4=1) 2012-05-03 21:54:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:54:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:54:48 MSG bell[21211]: arguments: /export/scratch2/bscheers/databases/MonetDB-Apr2012/bin/mserver5 --set gdk_dbfarm=/export/scratch2/bscheers/databases/data/dbfarm --dbname=bell --set merovingian_uri=mapi:monetdb://napels.ins.cwi.nl:60000/bell --set mapi_open=false --set mapi_port=0 --set mapi_usock=/export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock --set monet_vault_key=/export/scratch2/bscheers/databases/data/dbfarm/bell/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2012-05-03 21:54:48 MSG bell[21211]: # MonetDB 5 server v11.9.1 "Apr2012" 2012-05-03 21:54:48 MSG bell[21211]: # Serving database 'bell', using 8 threads 2012-05-03 21:54:48 MSG bell[21211]: # Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked 2012-05-03 21:54:48 MSG bell[21211]: # Found 15.629 GiB available main-memory. 2012-05-03 21:54:48 MSG bell[21211]: # Copyright (c) 1993-July 2008 CWI. 2012-05-03 21:54:48 MSG bell[21211]: # Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved 2012-05-03 21:54:48 MSG bell[21211]: # Visit http://www.monetdb.org/ for further information 2012-05-03 21:54:48 MSG bell[21211]: # Listening for UNIX domain connection requests on mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock 2012-05-03 21:54:48 MSG bell[21211]: # MonetDB/GIS module loaded 2012-05-03 21:54:48 MSG bell[21211]: # MonetDB/SQL module loaded 2012-05-03 21:54:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:54:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:54:48 MSG bell[21211]: Running database upgrade commands: 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val TINYINT) returns TINYINT external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val SMALLINT) returns SMALLINT external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val INTEGER) returns INTEGER external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val BIGINT) returns BIGINT external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val REAL) returns REAL external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate median(val DOUBLE) returns DOUBLE external name "aggr"."median"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 TINYINT, e2 TINYINT) returns TINYINT external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 SMALLINT, e2 SMALLINT) returns SMALLINT external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 INTEGER, e2 INTEGER) returns INTEGER external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 BIGINT, e2 BIGINT) returns BIGINT external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 REAL, e2 REAL) returns REAL external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: create aggregate corr(e1 DOUBLE, e2 DOUBLE) returns DOUBLE external name "aggr"."corr"; 2012-05-03 21:54:48 MSG bell[21211]: insert into sys.systemfunctions (select f.id from sys.functions f, sys.schemas s where f.name in ('median', 'corr') and f.type = 3 and f.schema_id = s.id and s.name = 'sys'); 2012-05-03 21:54:48 MSG bell[21211]: 2012-05-03 21:55:00 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:00 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:00 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:00 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:00 MSG bell[21211]: Running database upgrade commands: 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val TINYINT) returns TINYINT external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val SMALLINT) returns SMALLINT external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val INTEGER) returns INTEGER external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val BIGINT) returns BIGINT external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val REAL) returns REAL external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate median(val DOUBLE) returns DOUBLE external name "aggr"."median"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 TINYINT, e2 TINYINT) returns TINYINT external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 SMALLINT, e2 SMALLINT) returns SMALLINT external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 INTEGER, e2 INTEGER) returns INTEGER external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 BIGINT, e2 BIGINT) returns BIGINT external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 REAL, e2 REAL) returns REAL external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: create aggregate corr(e1 DOUBLE, e2 DOUBLE) returns DOUBLE external name "aggr"."corr"; 2012-05-03 21:55:00 MSG bell[21211]: insert into sys.systemfunctions (select f.id from sys.functions f, sys.schemas s where f.name in ('median', 'corr') and f.type = 3 and f.schema_id = s.id and s.name = 'sys'); 2012-05-03 21:55:00 MSG bell[21211]: 2012-05-03 21:55:00 ERR bell[21211]: !ParseException:SQLparser:CREATE AGGREGATE: name 'median' (tinyint(8)) already in use 2012-05-03 21:55:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:48 MSG merovingian[21195]: proxying client (local) for database 'bell' to mapi:monetdb:///export/scratch2/bscheers/databases/data/dbfarm/bell/.mapi.sock?database=bell 2012-05-03 21:55:48 MSG merovingian[21195]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2012-05-03 21:55:48 MSG bell[21211]: Running database upgrade commands: 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val TINYINT) returns TINYINT external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val SMALLINT) returns SMALLINT external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val INTEGER) returns INTEGER external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val BIGINT) returns BIGINT external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val REAL) returns REAL external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate median(val DOUBLE) returns DOUBLE external name "aggr"."median"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 TINYINT, e2 TINYINT) returns TINYINT external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 SMALLINT, e2 SMALLINT) returns SMALLINT external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 INTEGER, e2 INTEGER) returns INTEGER external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 BIGINT, e2 BIGINT) returns BIGINT external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 REAL, e2 REAL) returns REAL external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: create aggregate corr(e1 DOUBLE, e2 DOUBLE) returns DOUBLE external name "aggr"."corr"; 2012-05-03 21:55:48 MSG bell[21211]: insert into sys.systemfunctions (select f.id from sys.functions f, sys.schemas s where f.name in ('median', 'corr') and f.type = 3 and f.schema_id = s.id and s.name = 'sys'); 2012-05-03 21:55:48 MSG bell[21211]: 2012-05-03 21:55:48 ERR bell[21211]: !ParseException:SQLparser:CREATE AGGREGATE: name 'median' (tinyint(8)) already in use
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On 05/04/2012 01:12 AM, Stefan Manegold wrote:
Hm, looks like a second client connection after an upgrade without restarting teh server tries to do the upgrade actions (e.g., adding new functions), again.
I did not test this with my upgrade tests, I only tested a second client connection after upgrading and restarting the server --- indeed a gap in my testing routine ...
Could you try to stop & restart your server and see whether the problem persists?
After a stop & start with monetdbd I still get the same error message while connecting with a client.
- Gijs
See changeset bb296c17ead0 for the fix.
On 2012-05-04 11:40, Gijs Molenaar wrote:
On 05/04/2012 01:12 AM, Stefan Manegold wrote:
Hm, looks like a second client connection after an upgrade without restarting teh server tries to do the upgrade actions (e.g., adding new functions), again.
I did not test this with my upgrade tests, I only tested a second client connection after upgrading and restarting the server --- indeed a gap in my testing routine ...
Could you try to stop & restart your server and see whether the problem persists?
After a stop & start with monetdbd I still get the same error message while connecting with a client.
- Gijs
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Ok i'm going to have a look. So for now it is best to downgrade to the previous version of the monetdb packages, or will there be fixed packages released for this soon?
thanks,
- Gijs
On 05/04/2012 01:40 PM, Sjoerd Mullender wrote:
See changeset bb296c17ead0 for the fix.
On 2012-05-04 11:40, Gijs Molenaar wrote:
On 05/04/2012 01:12 AM, Stefan Manegold wrote:
Hm, looks like a second client connection after an upgrade without restarting teh server tries to do the upgrade actions (e.g., adding new functions), again.
I did not test this with my upgrade tests, I only tested a second client connection after upgrading and restarting the server --- indeed a gap in my testing routine ...
Could you try to stop & restart your server and see whether the problem persists?
After a stop & start with monetdbd I still get the same error message while connecting with a client.
On 05/04/2012 02:18 PM, Gijs Molenaar wrote:
Ok i'm going to have a look. So for now it is best to downgrade to the previous version of the monetdb packages, or will there be fixed packages released for this soon?
I've build packages myself from the apr2012 branch and I can confirm that this resolves the issue.
Thanks,
- Gijs
On 2012-05-04 14:18, Gijs Molenaar wrote:
Ok i'm going to have a look. So for now it is best to downgrade to the previous version of the monetdb packages, or will there be fixed packages released for this soon?
Just attach an mclient with user/password equal to monetdb (using default schema "sys"). You need to do this once.
thanks,
- Gijs
On 05/04/2012 01:40 PM, Sjoerd Mullender wrote:
See changeset bb296c17ead0 for the fix.
On 2012-05-04 11:40, Gijs Molenaar wrote:
On 05/04/2012 01:12 AM, Stefan Manegold wrote:
Hm, looks like a second client connection after an upgrade without restarting teh server tries to do the upgrade actions (e.g., adding new functions), again.
I did not test this with my upgrade tests, I only tested a second client connection after upgrading and restarting the server --- indeed a gap in my testing routine ...
Could you try to stop & restart your server and see whether the problem persists?
After a stop & start with monetdbd I still get the same error message while connecting with a client.
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
participants (5)
-
Bart Scheers -
Gijs Molenaar -
Martin Kersten -
Sjoerd Mullender -
Stefan Manegold