On 13-06-2008 13:56:30 -0700, Rt Ibmer wrote:
There should be a ".vaultkey" file as well when created with `monetdb`. Merovingian uses that file.
Thanks. I edited that file by deleting what was there, and replacing it simply with "monetdb" (without the quotes). Then I saved it off. Then I restart merovingian but it still says invalid credentials.
It's not a password. It's a vault "key". The best thing to do here is to destroy and create the database such that it gets a new key assigned.
My opinion is that you have to start merovingian at boot, as it is made exactly for doing what you want.
That is what I am planning to do. But for now I am starting it by typing into the command window, for testing purposes.
That should work fine.
1) create a db and schemas. I can do this successfully with mclient. 2) make monetdb start up at boot time and listen for connections using meroviangian. if there is another way please let me know. 3) use jdbc to access the db. I cannot do this because monetdb/monetdb gives an invalid credientials response using my jdbc as well as your jdbcclient.
I think you should switch 1) and 2). Do not manually start mserver5 yourself if you intend to use merovingian. Let monetdb and merovingian handle all interactions with the database server.
The first thing I do is run merovingian. Then I try my jdbc code as well as your jdbcclient.jar and it says "too many redirects. sorry".
Ok, that is a bug, we need to fix.
So then the only reason I am running mserver5 is as a diagnostic - just to see what it does when I try JDBC. And in that case it gives the invalid credientials. I am assuming merovingian ran into this too but instead of saying invalid credientials it says too may redirects as it tries.
That makes sense. We should fix the "too many redirects" thing, and then things will get easier for you.
I am quite certain there is a bug here because if I use the RELEASE build than everything works great with regards to this!!!
How do you explain that I do not have this problem running the RELEASE code, only with the nightly. I think something is broken since the release!
Quite a lot has changed. If you'd do the same "workaround" on the current release, the same problem should arise.
Use the latest "nightly stable" sources (monetdb-install.sh --nightly=stable ...) and help us to resolve bugs by carefully describing your steps such that we can replay them.
But I thought I have already done this? I already tried installing from scratch using --night=stable, and already laid out step by step what I am trying. Is there something else I can try?
I only read your mail afterwards.
If you were getting an invalid credientials when trying to connect via jdbc to meroviangian how would you go about troubleshooting this?
I would like to have a debug log when you get "too many redirects". Please run jdbcclient with -Xdebug and send me the monet_XXXXXXXXXXX.log file.