... maybe instead of using different program(-name) suffixes (--program-suffix='-dsh') --- I'n not sure we ever tested that --- you could better use different installtion prefixes, say

--prefix=/home/bruder/monetdb-root-1 and --prefix=/home/bruder/monetdb-root-2

for different version of MonetDB?

that's what I/we usually do ...

Best, Stefan

----- On Sep 29, 2016, at 9:03 PM, Stefan Manegold Stefan.Manegold@cwi.nl wrote:

Hi Moritz,

your log says: " 2016-09-29 17:06:11 MSG merovingian[21567]: starting database 'test', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0) 2016-09-29 17:06:11 MSG test[21607]: arguments: /home/bruder/monetdb-root/bin/monetdbd-dsh --dbpath=/home/bruder/monetdb-dbfarm/test --set merovingian_uri=mapi:monetdb://dbiron2:49999/test --set mapi_open=false --set mapi_port=0 --set mapi_usock=/home/bruder/monetdb-dbfarm/test/.mapi.sock --set monet_vault_key=/home/bruder/monetdb-dbfarm/test/.vaultkey --set gdk_nr_threads=16 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2016-09-29 17:06:11 MSG test[21607]: usage: monetdbd [ command [ command-options ] ] <dbfarm> 2016-09-29 17:06:11 MSG test[21607]: where command is one of: 2016-09-29 17:06:11 MSG test[21607]: create, start, stop, get, set, version or help 2016-09-29 17:06:11 MSG test[21607]: use the help command to get help for a particular command 2016-09-29 17:06:11 MSG test[21607]: The dbfarm to operate on must always be given to 2016-09-29 17:06:11 MSG test[21607]: monetdbd explicitly. 2016-09-29 17:06:11 ERR test[21607]: monetdbd: unknown command: --dbpath=/home/bruder/monetdb-dbfarm/test 2016-09-29 17:06:11 MSG merovingian[21567]: database 'test' (21607) has exited with exit status 1 2016-09-29 17:06:11 ERR control[21567]: (local): failed to fork mserver: database 'test' appears to shut itself down after starting, check monetdbd's logfile for possible hints "

somehow, monetdb seems to think that "mserver5" is called "/home/bruder/monetdb-root/bin/monetdbd-dsh" in your case, but that "/home/bruder/monetdb-root/bin/monetdbd-dsh" seems to be "monetdbd" !? This is also reflected/confirmed by your dbfarm properties: " mserver /home/bruder/monetdb-root/bin/monetdbd-dsh "

Well, your configure uses --program-suffix='-dsh', hence, the -dsh suffix for all your commands, but I have no idea why your dbfarm / monetdbd / monetdb "confuse" mserver5-dsh & monetdbd-dsh ?

How did you start your monetdbd? I.e., what was the exact command line?

Best, Stefan

----- On Sep 29, 2016, at 8:42 PM, Moritz Bruder moritz.bruder@student.uni-tuebingen.de wrote:

...

Hi,

so I read several times on the mailing-list, that it is indeed possible to run several MonetDB instances on the same server. I tried this myself with the following configuration:

System: Linux ... 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux MonetDB version: mercurial revision 324165f1d055 from branch default (also tested with the topmost version) Configure script parameters: --disable-geom --disable-fits --disable-netcdf --disable-lidar --disable-shp --disable-gsl --disable-rintegration --disable-pyintegration --disable-jdbc --prefix=/home/bruder/monetdb-root --disable-assert --disable-testing --enable-optimize --program-suffix='-dsh'

1. Another version is running with a different user on the default port

50000 2. With my user, I set up a local db-farm, using port 49999. (A prefix is used on binaries, to prevent any conflicts with the existing version.)

Creating a new database with *monetdbd* works, but once I try to start it with *monetdb*, it gives me the following error message:

starting database 'test'... FAILED
start: starting 'test' failed: database 'test' appears to shut

itself down after starting, check monetdbd's logfile for possible hints

Another thing I tried was starting mserver5 by hand: mserver5-dsh --dbpath=/home/bruder/monetdb-dbfarm/test --set merovingian_uri=mapi:monetdb://dbiron2:49999/test --set mapi_open=false --set mapi_port=0 --set mapi_usock=/home/bruder/monetdb-dbfarm/test/.mapi.sock --set monet_vault_key=/home/bruder/monetdb-dbfarm/test/.vaultkey --set gdk_nr_threads=16 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes This time it won't accept my password (I assume the default password is *monetdb*): mclient-dsh -p49999 -dtest -umonetdb InvalidCredentialsException:checkCredentials:invalid credentials for user 'monetdb'

I added the log file and the properties of the db-farm.

Regards,

Moritz

---

users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

-- | Stefan.Manegold@CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |

On 30/09/16 13:22, Moritz Bruder wrote:

Am 29.09.2016 um 21:06 schrieb Stefan Manegold:

...

... maybe instead of using different program(-name) suffixes (--program-suffix='-dsh') --- I'n not sure we ever tested that --- you could better use different installtion prefixes, say

--prefix=/home/bruder/monetdb-root-1 and --prefix=/home/bruder/monetdb-root-2

for different version of MonetDB?

that's what I/we usually do ...

Thanks for your help! The other version is installed as system package (with --prefx=/usr I guess), the arguments to monetdbd are exactly as in the tutorial. I removed the suffix and now it works (probably somehow related to the suffix), but I'm back at the credentials issue:

2016-09-30 13:14:52 ERR test[18989]: !FATAL: MALException:verifyPassword:Unknown backend hash algorithm: SHA512

Is there some way to manually set the password hashing algorithm? Which library provides that algorithm?

Which (exact) version are you using? You may have to update your sources since there were some bugs in the code that caused this behavior that should now be fixed.

Regards,

Moritz _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list