Hi Hanafi, Sorry to hear you're running into troubles getting started up. That error is unfortunately less specific than it might suggest. One of the most common reasons this happens is if you are using a shell besides bash or sh. There's a script in $MANAGIX_HOME/.installer/zookeeper/bin that is actually trying to start Zookeeper. One thing I usually try, when this step is being especially tempermental, is to just run that script with reasonable parameters by hand. After Zookeeper gets started up, everything else will proceed normally.
There's also other ways to start AsterixDB just for demo purposes (as a local process, in a Docker container, etc...), so if the above doesn't work, I can point you at some of those alternatives. Thanks, -Ian On Wed, Jul 1, 2015 at 3:24 PM, Hanifi GUNES <[email protected]> wrote: > I am following the instructions given at [1] to get Asterix up and running > on my Mac. For some reason, I cannot get managix to create an instance. I > already set the log level down to ALL and made sure java_home is exported > to shell as well as to conf/managix-conf.xml > > Can someone point me to right direction on how to debug this? > > > *> managix validate* > *INFO: Environment [OK]**INFO: Managix Configuration [OK]* > > > *> managix create -n mydb -c $MANAGIX_HOME/clusters/local/local.xml* > *DEBUG: Starting ZooKeeper at 127.0.0.1:2900 <http://127.0.0.1:2900>* > *ERROR: Unable to start Zookeeper Service. This could be because of the > following reasons.* > *1) Managix is incorrectly configured. Please run managix validate to run a > validation test and correct the errors reported.**2) If validation in (1) > is successful, ensure that java_home parameter is set correctly in Managix > configuration (conf/managix-conf.xml)* > > Thanks > -Hanifi > > > 1: https://asterixdb.ics.uci.edu/documentation/install.html
