search

michelya / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

Tungsten replicator does not check ports availability at startup #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When the replicator starts, it does not check if the ports that it has been 
assigned in the configuration file are free.
It will start nonetheless, and the user need to check the log file to find what 
happened.
The replicator should not start when these conditions happen. It should check 
that everything that is needed is available, and fail if any of the resources 
are missing.

How to repeat:

(1) Install Tungsten replicator from any version.
The unpack a different version in a different directory, and install again. 
Tungsten will start, and then complain in the log file.

(2) install Tungsten in any directory, giving as logs dir a non-existing 
directory.
     Tungsten will start, but it will not work, as it will be unable of creating the service directory

Original issue reported on code.google.com by berkeley...@gmail.com on 14 Apr 2011 at 9:14

GoogleCodeExporter commented 9 years ago 
Migrated from http://forge.continuent.org/jira/browse/TUC-272.

Original comment by berkeley...@gmail.com on 14 Apr 2011 at 9:14

GoogleCodeExporter commented 9 years ago

Original comment by berkeley...@gmail.com on 3 Jun 2011 at 7:15

GoogleCodeExporter commented 9 years ago

Original comment by berkeley...@gmail.com on 3 Jun 2011 at 7:15

GoogleCodeExporter commented 9 years ago

Original comment by berkeley...@gmail.com on 3 Sep 2011 at 12:30

GoogleCodeExporter commented 9 years ago

Original comment by berkeley...@gmail.com on 3 Sep 2011 at 12:32

GoogleCodeExporter commented 9 years ago

Original comment by robert.h...@continuent.com on 23 Jan 2012 at 6:50

GoogleCodeExporter commented 9 years ago

Original comment by robert.h...@continuent.com on 1 Mar 2012 at 9:45

GoogleCodeExporter commented 9 years ago

Original comment by robert.h...@continuent.com on 1 Mar 2012 at 9:46

GoogleCodeExporter commented 9 years ago

Original comment by robert.h...@continuent.com on 19 Sep 2012 at 2:19

GoogleCodeExporter commented 9 years ago

Original comment by robert.h...@continuent.com on 19 Sep 2012 at 2:23

GoogleCodeExporter commented 9 years ago

Original comment by jeffm...@gmail.com on 30 Oct 2012 at 12:53

GoogleCodeExporter commented 9 years ago 
I'll handle this one.

Original comment by robert.h...@continuent.com on 18 Mar 2013 at 6:13

GoogleCodeExporter commented 9 years ago

Original comment by robert.h...@continuent.com on 18 Mar 2013 at 6:34

GoogleCodeExporter commented 9 years ago 
We'll use 2.1.0 instead of 2.0.8, hence moving the issues.

Original comment by linas.vi...@continuent.com on 27 Mar 2013 at 3:11

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 26 Aug 2013 at 1:54

GoogleCodeExporter commented 9 years ago 
There won't be a 2.1.3.

Original comment by linas.vi...@continuent.com on 17 Sep 2013 at 10:13

GoogleCodeExporter commented 9 years ago 
This type of problem occurs rarely now with the improvements to installations.  
I think we can close this as not to be fixed for the time being.

Original comment by robert.h...@continuent.com on 11 Dec 2013 at 4:24