That´s it. Nothing in the log file and i can´t find the java log.
I had to set discovery.zen.ping.multicast.enabled: false in order to
work earlier, after a server restart i´m lost
Do you run it with elasticsearch -f? Run it with it and see what happens.
Also, see if the JVM crashed for some reason, you should see, from the work
directory of the process (where you ran it from) an hs_err file (or
something similar).
That´s it. Nothing in the log file and i can´t find the java log.
I had to set discovery.zen.ping.multicast.enabled: false in order to
work earlier, after a server restart i´m lost
the above is the output from ./elasticsearch -f
No log file either in any elasticsearch dir, not under /tmp , nothing
in tha java dir
Hetzner server support will suffer tomorrow
Do you run it with elasticsearch -f? Run it with it and see what happens.
Also, see if the JVM crashed for some reason, you should see, from the work
directory of the process (where you ran it from) an hs_err file (or
something similar).
That´s it. Nothing in the log file and i can´t find the java log.
I had to set discovery.zen.ping.multicast.enabled: false in order to
work earlier, after a server restart i´m lost
out of memory? out of disk space? any useful information in dmesg?
(lucky guessing)
On 03.01.2012 20:11, mrblue wrote:
Hi,
the above is the output from ./elasticsearch -f
No log file either in any elasticsearch dir, not under /tmp , nothing
in tha java dir
Hetzner server support will suffer tomorrow
Do you run it with elasticsearch -f? Run it with it and see what happens.
Also, see if the JVM crashed for some reason, you should see, from the work
directory of the process (where you ran it from) an hs_err file (or
something similar).
That´s it. Nothing in the log file and i can´t find the java log.
I had to set discovery.zen.ping.multicast.enabled: false in order to
work earlier, after a server restart i´m lost
out of memory? out of disk space? any useful information in dmesg?
(lucky guessing)
On 03.01.2012 20:11, mrblue wrote:
Hi,
the above is the output from ./elasticsearch -f
No log file either in any elasticsearch dir, not under /tmp , nothing
in tha java dir
Hetzner server support will suffer tomorrow
Do you run it with elasticsearch -f? Run it with it and see what happens.
Also, see if the JVM crashed for some reason, you should see, from the work
directory of the process (where you ran it from) an hs_err file (or
something similar).
That�s it. Nothing in the log file and i can�t find the java log.
I had to set discovery.zen.ping.multicast.enabled: false in order to
work earlier, after a server restart i�m lost
So, my last guess is some watchdog-script kills all processes which
listen on 'blacklisted' port.
and update:
"""
http://www.hetzner.de/en/hosting/legal/system-policies-ws#6Process
Monitoring:*
To enable fair resource allocation there is a process monitoring system
on shared servers which stops processes with excessive running times
and/or RAM exploitation. For account types from Level 19 exceptions can
be made for specifically defined processes, after they are first tested
by the system administration. If the stability of the server or the
network is affected, Hetzner Online has the right to correct and/or
cancel these exceptions.
""" http://www.hetzner.de/en/hosting/legal/system-policies-ws
On 03.01.2012 20:27, mrblue wrote:
Nah, nothing. Big managed Server.. Tried it on a similar machine from
the same hoster, same problem. Will bother hoster tomorrow. Really
sucks.
out of memory? out of disk space? any useful information in dmesg?
(lucky guessing)
On 03.01.2012 20:11, mrblue wrote:
Hi,
the above is the output from ./elasticsearch -f
No log file either in any elasticsearch dir, not under /tmp , nothing
in tha java dir
Hetzner server support will suffer tomorrow
Do you run it with elasticsearch -f? Run it with it and see what happens.
Also, see if the JVM crashed for some reason, you should see, from the work
directory of the process (where you ran it from) an hs_err file (or
something similar).
That�s it. Nothing in the log file and i can�t find the java log.
I had to set discovery.zen.ping.multicast.enabled: false in order to
work earlier, after a server restart i�m lost
So, my last guess is some watchdog-script kills all processes which
listen on 'blacklisted' port.
and update:
"""
http://www.hetzner.de/en/hosting/legal/system-policies-ws#6Process
Monitoring:*
To enable fair resource allocation there is a process monitoring system
on shared servers which stops processes with excessive running times
and/or RAM exploitation. For account types from Level 19 exceptions can
be made for specifically defined processes, after they are first tested
by the system administration. If the stability of the server or the
network is affected, Hetzner Online has the right to correct and/or
cancel these exceptions.
"""http://www.hetzner.de/en/hosting/legal/system-policies-ws
On 03.01.2012 20:27, mrblue wrote:
Nah, nothing. Big managed Server.. Tried it on a similar machine from
the same hoster, same problem. Will bother hoster tomorrow. Really
sucks.
out of memory? out of disk space? any useful information in dmesg?
(lucky guessing)
On 03.01.2012 20:11, mrblue wrote:
Hi,
the above is the output from ./elasticsearch -f
No log file either in any elasticsearch dir, not under /tmp , nothing
in tha java dir
Hetzner server support will suffer tomorrow
Do you run it with elasticsearch -f? Run it with it and see what happens.
Also, see if the JVM crashed for some reason, you should see, from the work
directory of the process (where you ran it from) an hs_err file (or
something similar).
That�s it. Nothing in the log file and i can�t find the java log.
I had to set discovery.zen.ping.multicast.enabled: false in order to
work earlier, after a server restart i�m lost
Oh well.. Hetzner is limiting the RAM for java aplications to 120MB
default. They made it 300 for me, but that didn´t work too. (Seems
strange but nothing i can do..)
Does anyone know how much a small index (<10k entrys) would need ?
I probably will try a cheap root server, wondering if 8gig RAM are
enough ?
Oh well.. Hetzner is limiting the RAM for java aplications to 120MB
default. They made it 300 for me, but that didn´t work too. (Seems
strange but nothing i can do..)
Does anyone know how much a small index (<10k entrys) would need ?
Totally depends on your data. Best thing to do is profile exactly
what you want to do. It only takes a few seconds to index that many
docs.
Oh well.. Hetzner is limiting the RAM for java aplications to 120MB
default. They made it 300 for me, but that didn´t work too. (Seems
strange but nothing i can do..)
Does anyone know how much a small index (<10k entrys) would need ?
Totally depends on your data. Best thing to do is profile exactly
what you want to do. It only takes a few seconds to index that many
docs.
Oh well.. Hetzner is limiting the RAM for java aplications to 120MB
default. They made it 300 for me, but that didn´t work too. (Seems
strange but nothing i can do..)
Does anyone know how much a small index (<10k entrys) would need ?
Totally depends on your data. Best thing to do is profile exactly
what you want to do. It only takes a few seconds to index that many
docs.
Oh well.. Hetzner is limiting the RAM for java aplications to 120MB
default. They made it 300 for me, but that didn´t work too. (Seems
strange but nothing i can do..)
Does anyone know how much a small index (<10k entrys) would need ?
Totally depends on your data. Best thing to do is profile exactly
what you want to do. It only takes a few seconds to index that many
docs.
Oh well.. Hetzner is limiting the RAM for java aplications to
120MB
default. They made it 300 for me, but that didn´t work too. (Seems
strange but nothing i can do..)
Does anyone know how much a small index (<10k entrys) would need ?
Totally depends on your data. Best thing to do is profile exactly
what you want to do. It only takes a few seconds to index that many
docs.
Oh well.. Hetzner is limiting the RAM for java aplications to
120MB
default. They made it 300 for me, but that didn´t work too.
(Seems
strange but nothing i can do..)
Does anyone know how much a small index (<10k entrys) would need
?
Totally depends on your data. Best thing to do is profile exactly
what you want to do. It only takes a few seconds to index that
many
docs.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
