Running Multiple Instances on Linux (Ubuntu)

[colinb4987]

Hi all,

First off, I'm really impressed with the work you've (simoncn) done pulling MinimServer together - it really is so much better than any other UPnP server I've encountered to date. Makes browsing Classical music a breeze. Such a pleasant experience has made me want to expand MS's use on my collection to the whole thing - but I think I need to run multiple instances to achieve what I would like.

Folder structure is:
root
--Popular
-----FLAC
-----mp3
--Jazz
-----FLAC
-----mp3
--Classical
-----FLAC
-----mp3

I'm only interested in serving up the FLAC folders (mp3s are lo-res shadows for portable devices).

I think what I'd like to do is have separate server instances running for each folder, so that controlpoints see initially three servers named "Popular", "Jazz", and "Classical" - thereafter, it's the standard MS behaviour/browsing.

Can anyone tell me how to do this on Ubuntu 13.04 (headless, accessible by ssh)?

[simoncn]

(24-07-2013 10:14)colinb4987 Wrote:  Hi all,

First off, I'm really impressed with the work you've (simoncn) done pulling MinimServer together - it really is so much better than any other UPnP server I've encountered to date. Makes browsing Classical music a breeze. Such a pleasant experience has made me want to expand MS's use on my collection to the whole thing - but I think I need to run multiple instances to achieve what I would like.

Folder structure is:
root
--Popular
-----FLAC
-----mp3
--Jazz
-----FLAC
-----mp3
--Classical
-----FLAC
-----mp3

I'm only interested in serving up the FLAC folders (mp3s are lo-res shadows for portable devices).

I think what I'd like to do is have separate server instances running for each folder, so that controlpoints see initially three servers named "Popular", "Jazz", and "Classical" - thereafter, it's the standard MS behaviour/browsing.

Can anyone tell me how to do this on Ubuntu 13.04 (headless, accessible by ssh)?

Thanks for the kind words. Because of the other common meaning for MS in the software context, I'm somewhat allergic to its use as an abbreviation for MinimServer.

Before starting this installation, you should install MinimWatch on another computer (PC, Mac or headful Linux).

Using ssh, you then need to perform the MinimServer installation steps three times in three separate directories and start MinimServer from each of these directories using the autostart.sh script. One instance of MinimServer should start correctly, and the other two should fail because of a conflict with port 9790. To resolve this, use MinimWatch to set the http.port property for the conflicting MinimServer instances to 9792 and 9793, then restart these instances by selecting Restart from their minim icons.

You can then use MinimWatch to set the displayName and contentDir properties to the values you want for the different instances.

On a headful Ubuntu, you can use the Startup Applications utility to start all three instances automatically when the machine is rebooted. I presume there is some equivalent on a headless Ubuntu, but I don't know what it is.

[colinb4987]

simoncn,

Thanks for the reply - and apologies for the inappropriate abbreviation. I get lazy and forget the broader context sometimes...

I've got the different instances untarred and running in the different folders (using the autostart.sh script). However, when I try to change the HTTP socket for the second and third instances, I get "HTTPService: error creating server socket: Address already in use". This seems to be persistent no matter the port specified. Stopping the instance running on HTTP 9790, and starting another using e.g. HTTP 9792 works.

Once I get these up and running I will tackle the autostart problem, and post whatever solution I concoct...

EDIT: additional info r.e. ports and running instances

[simoncn]

(24-07-2013 13:03)colinb4987 Wrote:  simoncn,

Thanks for the reply - and apologies for the inappropriate abbreviation. I get lazy and forget the broader context sometimes...

I've got the different instances untarred and running in the different folders (using the autostart.sh script). However, when I try to change the HTTP socket for the second and third instances, I get "HTTPService: error creating server socket: Address already in use". This seems to be persistent no matter the port specified. Stopping the instance running on HTTP 9790, and starting another using e.g. HTTP 9792 works.

Once I get these up and running I will tackle the autostart problem, and post whatever solution I concoct...

EDIT: additional info r.e. ports and running instances

To make this work, you need to select Close in MinimWatch to stop the MinimServer instance after changing the port number, then start the instance again using the autostart.sh script. Apologies for the previous misleading instructions.

[colinb4987]

(24-07-2013 14:40)simoncn Wrote:  

(24-07-2013 13:03)colinb4987 Wrote:  simoncn,

Thanks for the reply - and apologies for the inappropriate abbreviation. I get lazy and forget the broader context sometimes...

I've got the different instances untarred and running in the different folders (using the autostart.sh script). However, when I try to change the HTTP socket for the second and third instances, I get "HTTPService: error creating server socket: Address already in use". This seems to be persistent no matter the port specified. Stopping the instance running on HTTP 9790, and starting another using e.g. HTTP 9792 works.

Once I get these up and running I will tackle the autostart problem, and post whatever solution I concoct...

EDIT: additional info r.e. ports and running instances

To make this work, you need to select Close in MinimWatch to stop the MinimServer instance after changing the port number, then start the instance again using the autostart.sh script. Apologies for the previous misleading instructions.

Fantastic, thanks.