Hello,
I have fixed it.
Issue was instance private ip.
I have changed below variable :
listener.protobuf.internal = :8087
It fixed the issue.
--
View this message in context:
http://riak-users.197444.n3.nabble.com/cannot-start-solr-no-logs-tp4033816p4034123.html
Sent from the Riak Users
Hello,
I tried below steps but no luck.
#rm -rf /var/lib/riak/ring/*
#riak start
error.log
2016-04-05 08:03:11.845 [error] <0.538.0> gen_server yz_solr_proc terminated
with reason: {"solr OS process exited",1}
2016-04-05 08:03:11.845 [error] <0.538.0> CRASH REPORT Process yz_solr_proc
with 0 n
Hello,
Yes, I am trying with search = on and its not starting. (search = off
starting fine)
Os is debian 8 .
crash.log
** Generic server riak_core_capability terminating
** Last message in was
{register,{riak_core,vnode_routing},{capability,[proxy,legacy],legacy,{riak_core,legacy_vnode_routin
Hello,
I am trying to run Riak on single node.
java version :
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)
--
View this message in context:
http://riak-users.197444.n3.nabble.com/cannot-start-sol
Hello,
If I am not enabling search its starting successfully.
I am running m3.meedium ec2 instance(1vCPU,3.75GB RAM).
I changed values now : search.solr.jvm_options = -d64 -Xms1g -Xmx3g
-XX:+UseStringCache -XX:+UseCompressedOops
Please find below console.log
2016-04-05 06:01:37.502 [info] <
Hello,
Raik version : 2.1.3
error.log
016-04-05 04:28:30.666 [error] <0.533.0> Supervisor yz_solr_sup had child
yz_solr_proc started with yz_solr_proc:start_link("/var/lib/riak/yz",
"/var/lib/riak/yz_temp", 8093, 8985) at <0.534.0> exit with reason {"solr OS
process exited",1} in context child_
Hi Saran,
I have a 5 node AWS c3.2xlarge instance cluster running ubuntu
14.04lts and I have my solr set to the below (yeah I know, but -Xmx will
never get the full 16g's!) ;
search.solr.jvm_options = -d64 -Xms1g -Xmx16g -XX:+UseG1GC
-XX:+ParallelRefProcEnabled -XX:G1HeapRegionSize=8m
-XX
Hi Saran,
Just noticed the link at the bottom. You should have given the context in
your message.
In any case, I would check the total memory your machine has and how much
of it is utilized by other processes.
Try DECREASING the heap allocation for Solr, just to see it it starts - it
looks like
Hi,
Could you give some more details? Which version of Riak? Your subject line
suggests that you cannot start Solr, but what do you mean by this? Can you
start Riak successfully? Where are you looking for logs?
Do you have search enabled in riak.conf (search = on)?
Regards,
Vitaly
On Tue, Apr 5
Hello,
I have same problem.
I increased -d64 -Xms2.5g -Xmx2.5g still having same problem.
My ulimit is also good.
ulimit -Sn 4096
ulimit -Hn 65536
Please assist.
Thanks
--
View this message in context:
http://riak-users.197444.n3.nabble.com/cannot-start-solr-no-logs-tp4033816p4034114.htm
Hao,
The Solr process is crashing because the JVM cannot allocate enough heap
memory. You need to provide more RAM. The message is:
2015-12-28 16:34:41.735 [info] <0.573.0>@yz_solr_proc:handle_info:135solr
stdout/err: Error occurred during initialization of VM
Could not reserve enough space
11 matches
Mail list logo