I wrote it just before: open a new terminal and do curl commands in it. You are fairly new to linux/unix stuff don't you?
That said, the -f option with bin/elasticsearch run elasticsearch in foreground. It's useful when you play with Elasticsearch as it's easy to stop it with a single CTRL+C
Another comment. You already launched an elasticsearch instance which is running on port 9200 and 9300.
I suggest that you kill it.
Or, you can run a shutdown command: See: Elasticsearch Platform — Find real-time answers at scale | Elastic
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs
Le 6 févr. 2013 à 15:58, Max B mbugyan@gmail.com a écrit :
That is what I have had in my terminal window:
root@ubuntu:/usr/local/elasticsearch/bin# ./elasticsearch -f
[2013-02-06 06:46:57,377][WARN ][bootstrap ] jvm uses the client vm, make sure to runjavawith the server vm for best performance by adding-serverto the command line
[2013-02-06 06:46:57,383][INFO ][node ] [Bushmaster] {0.20.4}[27142]: initializing ...
[2013-02-06 06:46:57,404][INFO ][plugins ] [Bushmaster] loaded [river-rss], sites
[2013-02-06 06:47:11,629][INFO ][node ] [Bushmaster] {0.20.4}[27142]: initialized
[2013-02-06 06:47:11,629][INFO ][node ] [Bushmaster] {0.20.4}[27142]: starting ...
[2013-02-06 06:47:12,178][INFO ][transport ] [Bushmaster] bound_address {inet[/0:0:0:0:0:0:0:0:9301]}, publish_address {inet[/192.168.44.143:9301]}
[2013-02-06 06:47:15,256][INFO ][cluster.service ] [Bushmaster] new_master [Bushmaster][MT1wmoVTShO7wFecmlJZ9w][inet[/192.168.44.143:9301]], reason: zen-disco-join (elected_as_master)
[2013-02-06 06:47:15,723][INFO ][discovery ] [Bushmaster] elasticsearch/MT1wmoVTShO7wFecmlJZ9w
[2013-02-06 06:47:20,202][INFO ][http ] [Bushmaster] bound_address {inet[/0:0:0:0:0:0:0:0:9201]}, publish_address {inet[/192.168.44.143:9201]}
[2013-02-06 06:47:20,202][INFO ][node ] [Bushmaster] {0.20.4}[27142]: started
[2013-02-06 06:47:20,431][INFO ][gateway ] [Bushmaster] recovered [0] indices into cluster_stateIt looks to be running correctly. But (there is always a "but"
) the cursor in my terminal window does not twinkle now, and I do not have root@ubuntu: anymore. Is it normal ?
Do I have to type my "curl" request now ? Except using Ctrl+C, how do I stop Elasticsearch running ?Thanks.
Le mercredi 6 février 2013 15:42:32 UTC+1, David Pilato a écrit :
No. You have to install plugins in plugins/ folder. I suppose it's in /usr/local/elasticsearch/plugins
Hit CTRL+C to stop Elasticsearch
Move rssriver dir to the right plugins dir and restart.You must see something like:
[2013-02-06 06:00:30,156][INFO ][plugins ] [Machine Teen] loaded [RSSRiver], sites
BTW, when ES is started (that was the case), open a new term and do:
curl localhost:9200
If you can get an answer, ES is ready to use. So you can create your river.
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocsLe 6 févr. 2013 à 15:37, Max B mbu...@gmail.com a écrit :
Ok. Following your instruction, that is what happen on my terminal window:
root@ubuntu:/usr/local/elasticsearch/bin# ./elasticsearch -f
[2013-02-06 06:00:30,061][WARN ][bootstrap ] jvm uses the client vm, make sure to runjavawith the server vm for best performance by adding-serverto the command line
[2013-02-06 06:00:30,119][INFO ][node ] [Machine Teen] {0.20.4}[26786]: initializing ...
[2013-02-06 06:00:30,156][INFO ][plugins ] [Machine Teen] loaded , sites
[2013-02-06 06:01:03,595][INFO ][node ] [Machine Teen] {0.20.4}[26786]: initialized
[2013-02-06 06:01:03,622][INFO ][node ] [Machine Teen] {0.20.4}[26786]: starting ...
[2013-02-06 06:01:09,720][INFO ][transport ] [Machine Teen] bound_address {inet[/0:0:0:0:0:0:0:0:9301]}, publish_address {inet[/192.168.44.143:9301]}
[2013-02-06 06:01:14,619][INFO ][cluster.service ] [Machine Teen] new_master [Machine Teen][dHJ9XvPnSNilWAI4qT_mGw][inet[/192.168.44.143:9301]], reason: zen-disco-join (elected_as_master)
[2013-02-06 06:01:14,732][INFO ][discovery ] [Machine Teen] elasticsearch/dHJ9XvPnSNilWAI4qT_mGw
[2013-02-06 06:01:15,063][INFO ][http ] [Machine Teen] bound_address {inet[/0:0:0:0:0:0:0:0:9201]}, publish_address {inet[/192.168.44.143:9201]}
[2013-02-06 06:01:15,064][INFO ][node ] [Machine Teen] {0.20.4}[26786]: started
[2013-02-06 06:01:16,981][INFO ][gateway ] [Machine Teen] recovered [0] indices into cluster_stateAnd then the cursor stay fixed and nothing happen after 10min processing, is it normal ?
I have noticed that there is a plugins folder in /usr/local/elasticsearch. I want you to certify that I do not had to create the rssriver in this folder, but in /usr/local/elasticsearch/bin/plugins/ (?)Thank you for your help.
Le mercredi 6 février 2013 14:58:46 UTC+1, David Pilato a écrit :
No. Just start Elasticsearch.bin/elasticsearch -f
You should see RSSRiver in logs.
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocsLe 6 févr. 2013 à 14:57, Max B mbu...@gmail.com a écrit :
Done. So now, do I have to "untar" the 4 new .jar packages ?
Le mercredi 6 février 2013 14:40:50 UTC+1, David Pilato a écrit :
Yes. Problem is now with github downloads.Download it manually from http://cloud.github.com/downloads/dadoonet/rssriver/rssriver-0.0.6.zip
Then, create a plugins folder then a rssriver inside.
Unzip rss river zip file in plugins/rssriver--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocsLe 6 févr. 2013 à 14:37, Max B mbu...@gmail.com a écrit :
Thank you so much.
I moved to the directory where I have unzipped Elasticsearch and the good bin directory was there actually.
So, I type ./plugin -install dadoonet/rssriver/0.0.6 and after few minutes got this result:-> Installing dadoonet/rssriver/0.0.6...
Trying http://download.elasticsearch.org/dadoonet/rssriver/rssriver-0.0.6.zip...
Trying http://search.maven.org/remotecontent?filepath=dadoonet/rssriver/0.0.6/rssriver-0.0.6.zip...
Trying https://oss.sonatype.org/service/local/repositories/releases/content/dadoonet/rssriver/0.0.6/rssriver-0.0.6.zip...
Trying https://github.com/dadoonet/rssriver/zipball/v0.0.6... (assuming site plugin)
Failed to install dadoonet/rssriver/0.0.6, reason: failed to download out of all possible locations..., use -verbose to get detailed informationAny ideas ?
Le mercredi 6 février 2013 14:21:00 UTC+1, David Pilato a écrit :
So, you are in /bin here.Just go to the dir where you downloaded elasticsearch and unzipped it.
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocsLe 6 févr. 2013 à 13:55, Max B mbu...@gmail.com a écrit :
Sorry I have forgot.
bash cat df fusermount lessfile mount ntfs-3g.usermap openvt run-parts tar zcat
bunzip2 chacl dir getfacl lesskey mountpoint ntfscat pidof sed tempfile zcmp
busybox chgrp dmesg grep lesspipe mt ntfsck ping setfacl touch zdiff
bzcat chmod dnsdomainname gunzip ln mt-gnu ntfscluster ping6 setfont true zegrep
bzcmp chown domainname gzexe loadkeys mv ntfscmp plymouth setupcon ulockmgr_server zfgrep
bzdiff chvt dumpkeys gzip login nano ntfsdump_logfile plymouth-upstart-bridge sh umount zforce
bzegrep cp echo hostname lowntfs-3g nc ntfsfix ps sh.distrib uname zgrep
bzexe cpio ed init-checkconf ls nc.openbsd ntfsinfo pwd sleep uncompress zless
bzfgrep dash egrep initctl2dot lsblk netcat ntfsls rbash ss unicode_start zmore
bzgrep date false ip lsmod netstat ntfsmftalloc readlink static-sh vdir znew
bzip2 dbus-cleanup-sockets fgconsole kbd_mode mkdir nisdomainname ntfsmove rm stty vmmouse_detect
bzip2recover dbus-daemon fgrep kill mknod ntfs-3g ntfstruncate rmdir su which
bzless dbus-uuidgen findmnt less mktemp ntfs-3g.probe ntfswipe rnano sync whiptail
bzmore dd fuser lessecho more ntfs-3g.secaudit open running-in-container tailf ypdomainnameLe mercredi 6 février 2013 13:50:25 UTC+1, David Pilato a écrit :
Lol! Can you paste the result here?--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocsLe 6 févr. 2013 à 13:49, Max B mbu...@gmail.com a écrit :
yes.
Le mercredi 6 février 2013 13:45:47 UTC+1, David Pilato a écrit :
Can you do a ls -l in the bin dir?--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocsLe 6 févr. 2013 à 13:39, Max B mbu...@gmail.com a écrit :
Thank you for your answer. I have tried what you suggest and changed directory to bin, but I have got the following problem:
bash: ./plugin: No such file or directoryDo I need to download a rssriver package before trying to install it ?
Le mercredi 6 février 2013 13:28:07 UTC+1, Shlomi a écrit :
bin is a directory, what you should do is go into bin "cd bin" and then enter "./plugin -install dadoonet/rssriver/0.0.6"On Wednesday, February 6, 2013 2:23:00 PM UTC+2, Max B wrote:
Hi,I have installed Elasticsearch on my Ubuntu Virtual Machine.
Now, I'd like to install the RSSRiver. I am identified as a root user. When I type: # bin\plugin -install dadoonet/rssriver/0.0.6 in my terminal window but I have been faced with the problem below:
bin: command not found
I also try: apt-get install dadoonet/rssriver/0.0.6 and get the following answer:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dadoonet/rssriverI am sure that it is not an important problem, so please could you help me resolve it.
Thanks
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.