RHEL 6.6, CentOS 6.6

This needs more information.

The process was called directly three times with the save configuration file. This should have resulted in only a single running maxscale process instead of three since the other two should have failed to bind to the same ports the first was already bound to. The configuration file listed a socket which is the probable cause for this.

stephane@skysql.com, stephanevaroqui Please attach the config file used when this happened.

Added functionality which checks if a MaxScale process is already running.

I'm wondering if this problem has been correctly diagnosed. It is intended that MaxScale should be capable of running more than once on a single machine, provided that each instance has its own configuration file and the use of ports does not conflict. Does the proposed solution retain the capability to run multiple instances of MaxScale?

With the changes in the development branch, you should be able to control the location of the PID directory and the configuration file you use. This way you should be able to run MaxScale on the same machine provided that nothing conflicts.

OK, great, thanks for the clarification.

markus makela Is this closed now ?