You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@asterixdb.apache.org by Ian Maxon <im...@uci.edu> on 2015/07/15 02:34:26 UTC

Re: Could you please help on this error: "Node xxx_node1 has no stores."

Hi Siripen,
managix's shutdown command actually doesn't shut down the instance-
stop does that. 'shutdown' stops the Zookeeper daemon that managix
starts up.

Did `my_asterix` and `my_asterix2` share the same iodevices in their
config? If they did, then the delete went ahead and just rm -rf'ed the
entire directory, hence the complaint about no stores (no metadata,
etc).

One resolution would be to delete my_asterix as well, and then create
an entirely new instance. If managix is giving you trouble though,
there's other, less tested but simpler ways to run AsterixDB on a
local instance that might be easier (especially if you're on a
recent-ish Linux version or OSX).

-Ian

On Tue, Jul 14, 2015 at 4:44 PM, Siripen Pongpaichet <sp...@gmail.com> wrote:
> Hi Ian,
>
> I got a following error when I tried to execute query on the web interface.
>
> Node my_asterix2_node1 has no stores. [AlgebricksException]
>
> I created two asterix instances on the same node, my_asterix and
> my_asterix2.
>
> After I deleted the my_asterix2, and ran only my_asterix. I received the
> above error.
>
> I stop the asterix_db, and ran the describe command. This is the output.
>
> INFO: Name:my_asterix
> Created:Thu Jul 09 18:42:45 PDT 2015
> Web-Url:http://127.0.0.1:19001
> State:INACTIVE (Tue Jul 14 16:36:56 PDT 2015)
>
> WARNING!:Following process still running
> NC at asterix [ 18715 ]
> CC at master [ 18594 ]
>
>
> I did ran the "shutdown" command. Does that cause the problem?
>
> How could I stop/restart the NC and CC? Could you please help me?
>
> (I attached the log files here as well)
>
> Best,
>
> Siripen

Re: Could you please help on this error: "Node xxx_node1 has no stores."

Posted by Ian Maxon <im...@uci.edu>.

We use maven 3- if you upgrade from maven 2 it should just work.

-Ian
On Jul 16, 2015 8:13 PM, "Siripen Pongpaichet" <sp...@gmail.com> wrote:

> Dear Ian,
>
> Sorry for several emails. I follow the instruction on dev-setup page.
>
> cd $HOME/workspace/asterixdb/asterix-maven-plugins/
> mvn install -DskipTests
>
> I got the syntax error as shown below. What should I do to solve this?
>
> [INFO] [install:install {execution: default-install}]
> [INFO] Installing
> /home/siripen/tools/asterixdb-dev/asterixdb/asterix-maven-plugins/pom.xml
> to
> /home/siripen/.m2/repository/edu/uci/ics/asterix/asterix-maven-plugins/0.8.7-SNAPSHOT/asterix-maven-plugins-0.8.7-SNAPSHOT.pom
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building record-manager-generator-maven-plugin
> [INFO]    task-segment: [install]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [plugin:descriptor {execution: default-descriptor}]
> [INFO] Using 2 extractors.
> [INFO] Applying extractor for language: java
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] syntax error @[39,26] in
> file:/home/siripen/tools/asterixdb-dev/asterixdb/asterix-maven-plugins/record-manager-generator-maven-plugin/src/main/java/edu/uci/ics/asterix/recordmanagergenerator/Generator.java
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> com.thoughtworks.qdox.parser.ParseException: syntax error @[39,26] in
> file:/home/siripen/tools/asterixdb-dev/asterixdb/asterix-maven-plugins/record-manager-generator-maven-plugin/src/main/java/edu/uci/ics/asterix/recordmanagergenerator/Generator.java
>     at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:716)
>     at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:826)
>     at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:697)
>     at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:300)
>     at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:316)
>     at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
>     at
> com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:369)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
>     at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52)
>     at
> com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:366)
>     at
> org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.discoverClasses(JavaMojoDescriptorExtractor.java:605)
>     at
> org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:572)
>     at
> org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
>     at
> org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:146)
>     at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>     at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:606)
>     at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>     at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>     at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>     at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
>
>
> *This is the maven version on my computer*
>
> Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
> Java version: 1.7.0_79
> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "3.16.0-43-generic" arch: "amd64" Family: "unix"
> -----
>
>
> Best regards,
> Siripen
>
> On Thu, Jul 16, 2015 at 10:26 AM, Ian Maxon <im...@uci.edu> wrote:
>
>> I see, so there must be something wrong with one of the NC's settings.
>> Looking at the logs might lend insight into why that might be the
>> case.
>>
>> If you just want to "kick the tires", since you're on Linux, Docker
>> should work really well. Just apt-get install docker.io, then docker
>> pull parshimers/asterix-playground; docker run -p 19001:19001 -t
>> parshimers/asterix-playground . The web interface will be up at the
>> same address as you'd expect running it locally otherwise.
>>
>> As for importing the source into eclipse, have a look at
>> https://asterixdb.incubator.apache.org/dev-setup.html . It should
>> describe how to import the source into Eclipse. The tutorial for feeds
>> is only in the latest master, so the documentation for that is here:
>>
>> https://asterix-jenkins.ics.uci.edu/job/asterix-test-full/site/asterix-doc/feeds/tutorial.html
>> .
>>
>> Thanks,
>> - Ian
>>
>> On Tue, Jul 14, 2015 at 5:58 PM, Siripen Pongpaichet <sp...@gmail.com>
>> wrote:
>> > Dear Ian,
>> >
>> > Thank you for your reply. You are right. I was using the same
>> configuration
>> > file for both instances.
>> >
>> > I deleted and recreated the 'my_asterix' instance, but the problem still
>> > remains.
>> >
>> > siripen@sln:~/tools/asterixdb/bin$ ./managix start -n my_asterix
>> > INFO: Name:my_asterix
>> > Created:Tue Jul 14 17:44:19 PDT 2015
>> > Web-Url:http://127.0.0.1:19001
>> > State:ACTIVE (Tue Jul 14 17:48:23 PDT 2015)
>> >
>> > WARNING!:Node Controller not running at the following nodes
>> > 127.0.0.1
>> >
>> > I still got the same error on the Web interface.
>> >
>> > I am using Ubuntu 14.04 now. Could you please tell me an alternative to
>> > start asterixdb?
>> >
>> > Another question, what is the proper way to import
>> > "asterix-server-0.8.7-SNAPSHOT-binary-assembly.zip" into eclipse? I
>> need to
>> > look at the source code and make a new class for my own data feed
>> adapter.
>> >
>> > Best regards,
>> > Siripen
>> >
>> >
>> > On Tue, Jul 14, 2015 at 5:34 PM, Ian Maxon <im...@uci.edu> wrote:
>> >>
>> >> Hi Siripen,
>> >> managix's shutdown command actually doesn't shut down the instance-
>> >> stop does that. 'shutdown' stops the Zookeeper daemon that managix
>> >> starts up.
>> >>
>> >> Did `my_asterix` and `my_asterix2` share the same iodevices in their
>> >> config? If they did, then the delete went ahead and just rm -rf'ed the
>> >> entire directory, hence the complaint about no stores (no metadata,
>> >> etc).
>> >>
>> >> One resolution would be to delete my_asterix as well, and then create
>> >> an entirely new instance. If managix is giving you trouble though,
>> >> there's other, less tested but simpler ways to run AsterixDB on a
>> >> local instance that might be easier (especially if you're on a
>> >> recent-ish Linux version or OSX).
>> >>
>> >> -Ian
>> >>
>> >> On Tue, Jul 14, 2015 at 4:44 PM, Siripen Pongpaichet <
>> spongpai@gmail.com>
>> >> wrote:
>> >> > Hi Ian,
>> >> >
>> >> > I got a following error when I tried to execute query on the web
>> >> > interface.
>> >> >
>> >> > Node my_asterix2_node1 has no stores. [AlgebricksException]
>> >> >
>> >> > I created two asterix instances on the same node, my_asterix and
>> >> > my_asterix2.
>> >> >
>> >> > After I deleted the my_asterix2, and ran only my_asterix. I received
>> the
>> >> > above error.
>> >> >
>> >> > I stop the asterix_db, and ran the describe command. This is the
>> output.
>> >> >
>> >> > INFO: Name:my_asterix
>> >> > Created:Thu Jul 09 18:42:45 PDT 2015
>> >> > Web-Url:http://127.0.0.1:19001
>> >> > State:INACTIVE (Tue Jul 14 16:36:56 PDT 2015)
>> >> >
>> >> > WARNING!:Following process still running
>> >> > NC at asterix [ 18715 ]
>> >> > CC at master [ 18594 ]
>> >> >
>> >> >
>> >> > I did ran the "shutdown" command. Does that cause the problem?
>> >> >
>> >> > How could I stop/restart the NC and CC? Could you please help me?
>> >> >
>> >> > (I attached the log files here as well)
>> >> >
>> >> > Best,
>> >> >
>> >> > Siripen
>> >
>> >
>> >
>> >
>> > --
>> > Siripen Pongpaichet
>> > University of California, Irvine
>> >
>>
>
>
>
> --
> Siripen Pongpaichet
> University of California, Irvine
>
>

Re: Could you please help on this error: "Node xxx_node1 has no stores."

Posted by Ian Maxon <im...@uci.edu>.

I see, so there must be something wrong with one of the NC's settings.
Looking at the logs might lend insight into why that might be the
case.

If you just want to "kick the tires", since you're on Linux, Docker
should work really well. Just apt-get install docker.io, then docker
pull parshimers/asterix-playground; docker run -p 19001:19001 -t
parshimers/asterix-playground . The web interface will be up at the
same address as you'd expect running it locally otherwise.

As for importing the source into eclipse, have a look at
https://asterixdb.incubator.apache.org/dev-setup.html . It should
describe how to import the source into Eclipse. The tutorial for feeds
is only in the latest master, so the documentation for that is here:
https://asterix-jenkins.ics.uci.edu/job/asterix-test-full/site/asterix-doc/feeds/tutorial.html
.

Thanks,
- Ian

On Tue, Jul 14, 2015 at 5:58 PM, Siripen Pongpaichet <sp...@gmail.com> wrote:
> Dear Ian,
>
> Thank you for your reply. You are right. I was using the same configuration
> file for both instances.
>
> I deleted and recreated the 'my_asterix' instance, but the problem still
> remains.
>
> siripen@sln:~/tools/asterixdb/bin$ ./managix start -n my_asterix
> INFO: Name:my_asterix
> Created:Tue Jul 14 17:44:19 PDT 2015
> Web-Url:http://127.0.0.1:19001
> State:ACTIVE (Tue Jul 14 17:48:23 PDT 2015)
>
> WARNING!:Node Controller not running at the following nodes
> 127.0.0.1
>
> I still got the same error on the Web interface.
>
> I am using Ubuntu 14.04 now. Could you please tell me an alternative to
> start asterixdb?
>
> Another question, what is the proper way to import
> "asterix-server-0.8.7-SNAPSHOT-binary-assembly.zip" into eclipse? I need to
> look at the source code and make a new class for my own data feed adapter.
>
> Best regards,
> Siripen
>
>
> On Tue, Jul 14, 2015 at 5:34 PM, Ian Maxon <im...@uci.edu> wrote:
>>
>> Hi Siripen,
>> managix's shutdown command actually doesn't shut down the instance-
>> stop does that. 'shutdown' stops the Zookeeper daemon that managix
>> starts up.
>>
>> Did `my_asterix` and `my_asterix2` share the same iodevices in their
>> config? If they did, then the delete went ahead and just rm -rf'ed the
>> entire directory, hence the complaint about no stores (no metadata,
>> etc).
>>
>> One resolution would be to delete my_asterix as well, and then create
>> an entirely new instance. If managix is giving you trouble though,
>> there's other, less tested but simpler ways to run AsterixDB on a
>> local instance that might be easier (especially if you're on a
>> recent-ish Linux version or OSX).
>>
>> -Ian
>>
>> On Tue, Jul 14, 2015 at 4:44 PM, Siripen Pongpaichet <sp...@gmail.com>
>> wrote:
>> > Hi Ian,
>> >
>> > I got a following error when I tried to execute query on the web
>> > interface.
>> >
>> > Node my_asterix2_node1 has no stores. [AlgebricksException]
>> >
>> > I created two asterix instances on the same node, my_asterix and
>> > my_asterix2.
>> >
>> > After I deleted the my_asterix2, and ran only my_asterix. I received the
>> > above error.
>> >
>> > I stop the asterix_db, and ran the describe command. This is the output.
>> >
>> > INFO: Name:my_asterix
>> > Created:Thu Jul 09 18:42:45 PDT 2015
>> > Web-Url:http://127.0.0.1:19001
>> > State:INACTIVE (Tue Jul 14 16:36:56 PDT 2015)
>> >
>> > WARNING!:Following process still running
>> > NC at asterix [ 18715 ]
>> > CC at master [ 18594 ]
>> >
>> >
>> > I did ran the "shutdown" command. Does that cause the problem?
>> >
>> > How could I stop/restart the NC and CC? Could you please help me?
>> >
>> > (I attached the log files here as well)
>> >
>> > Best,
>> >
>> > Siripen
>
>
>
>
> --
> Siripen Pongpaichet
> University of California, Irvine
>