Re: [MonetDB-users] Running multiple mserver5 processes, Merovingian
On 01-02-2008 10:08:17 -0500, McKennirey.Matthew wrote:
Thanks for your help, I admit I am getting a bit perplexed.
Using the approach you suggest, the merovingian daemon uses the default mapi port, if set, for the first database, then tries to start subsequent databses on the same port - with the expected result. I have shown the settings I am using in the monetdb5.conf file, the merovingian command (the one you provided) and the output from the merovingian log.
If I do not set a default mapi port, then the deamon tries to start all the databases on its default port (50000) and none start. ... # mapi port set to 50001, allow remote access mapi_port=50001 # default port to address a mserver mapi_open=true # should be set to 'true' to allow for remote access
Aha, I see! What happens here is that you explicitly disabled mserver5's port auto-sensing, which is vital for this to work. By the way, merovingian currently forces mapi_open to be true for each mserver5 it starts. You need the following setting: mapi_port=0 # default port to address a mserver That setting could have a different default to disable auto-sensing, and merovingian could explicitly turn it on, regardless the monetdb5.conf setting. The latter is in any case a good idea I guess. Would you please file a bug against merovingian for this issue?
On 03-02-2008 10:18:33 +0100, Fabian Groffen wrote:
That setting could have a different default to disable auto-sensing, and merovingian could explicitly turn it on, regardless the monetdb5.conf setting. The latter is in any case a good idea I guess.
Would you please file a bug against merovingian for this issue?
I just fixed this bug in stable.
participants (2)
-
Fabian Groffen
-
McKennirey.Matthew