# Instant crash on startup **URL:** \ **Category:** Elasticsearch\ **Created:** [January 3, 2012, 6:02pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273 "2012-01-03T18:02:06Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![mrblue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mrblue/32/23268_2.png) [@mrblue](https://discuss.elastic.co/u/mrblue)\ **Post date:** [January 3, 2012, 6:02pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/1 "2012-01-03T18:02:06Z")
Hi, when i try to start elasticsearch on my managed server, it goes like this: [2012-01-03 18:59:25,364][INFO][node] [Tom Thumb] {0.18.6}[23920]: initializing ... [2012-01-03 18:59:25,373][INFO][plugins] [Tom Thumb] loaded [], sites [] [2012-01-03 18:59:27,788][INFO][node] [Tom Thumb] {0.18.6}[23920]: initialized [2012-01-03 18:59:27,788][INFO][node] [Tom Thumb] {0.18.6}[23920]: starting ... Killed 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 ☹ Maybe someone has seen this before ? ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [January 3, 2012, 6:50pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/2 "2012-01-03T18:50:22Z")
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). On Tue, Jan 3, 2012 at 8:02 PM, mrblue [john.agricola.27@googlemail.com](mailto:john.agricola.27@googlemail.com)wrote: > Hi, > > when i try to start elasticsearch on my managed server, it goes like > this: > > [2012-01-03 18:59:25,364][INFO][node] [Tom > Thumb] {0.18.6}[23920]: initializing ... > [2012-01-03 18:59:25,373][INFO][plugins] [Tom > Thumb] loaded , sites > [2012-01-03 18:59:27,788][INFO][node] [Tom > Thumb] {0.18.6}[23920]: initialized > [2012-01-03 18:59:27,788][INFO][node] [Tom > Thumb] {0.18.6}[23920]: starting ... > Killed > > 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 ☹ > > Maybe someone has seen this before ? ---
**Author:** ![mrblue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mrblue/32/23268_2.png) [@mrblue](https://discuss.elastic.co/u/mrblue)\ **Post date:** [January 3, 2012, 7:11pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/3 "2012-01-03T19:11:43Z")
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 😉 On Jan 3, 7:50 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > 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). > > On Tue, Jan 3, 2012 at 8:02 PM, mrblue [john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com)wrote: > > > Hi, > > > when i try to start elasticsearch on my managed server, it goes like > > this: > > > [2012-01-03 18:59:25,364][INFO][node] [Tom > > Thumb] {0.18.6}[23920]: initializing ... > > [2012-01-03 18:59:25,373][INFO][plugins] [Tom > > Thumb] loaded , sites > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > Thumb] {0.18.6}[23920]: initialized > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > Thumb] {0.18.6}[23920]: starting ... > > Killed > > > 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 ☹ > > > Maybe someone has seen this before ? ---
**Author:** ![Tomasz\_Kloc](https://avatars.discourse-cdn.com/v4/letter/t/958977/32.png) [@Tomasz\_Kloc](https://discuss.elastic.co/u/Tomasz_Kloc)\ **Post date:** [January 3, 2012, 7:15pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/4 "2012-01-03T19:15:29Z")
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 😉 > > On Jan 3, 7:50 pm, Shay Banon[kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > 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). > > > > On Tue, Jan 3, 2012 at 8:02 PM, mrblue[john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com)wrote: > > > > > Hi, > > > > > when i try to start elasticsearch on my managed server, it goes like > > > this: > > > > > [2012-01-03 18:59:25,364][INFO][node] [Tom > > > Thumb] {0.18.6}[23920]: initializing ... > > > [2012-01-03 18:59:25,373][INFO][plugins] [Tom > > > Thumb] loaded , sites > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > Thumb] {0.18.6}[23920]: initialized > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > Thumb] {0.18.6}[23920]: starting ... > > > Killed > > > > > 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 ☹ > > > > > Maybe someone has seen this before ? ---
**Author:** ![mrblue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mrblue/32/23268_2.png) [@mrblue](https://discuss.elastic.co/u/mrblue)\ **Post date:** [January 3, 2012, 7:27pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/5 "2012-01-03T19:27:56Z")
Nah, nothing. Big managed Server.. Tried it on a similar machine from the same hoster, same problem. Will bother hoster tomorrow. Really sucks. On Jan 3, 8:15 pm, Tomasz Kloc [tomek.kloc....@gmail.com](mailto:tomek.kloc....@gmail.com) wrote: > 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 😉 > > > On Jan 3, 7:50 pm, Shay Banon[kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > 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). > > > > On Tue, Jan 3, 2012 at 8:02 PM, mrblue[john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com)wrote: > > > > > Hi, > > > > > when i try to start elasticsearch on my managed server, it goes like > > > > this: > > > > > [2012-01-03 18:59:25,364][INFO][node] [Tom > > > > Thumb] {0.18.6}[23920]: initializing ... > > > > [2012-01-03 18:59:25,373][INFO][plugins] [Tom > > > > Thumb] loaded , sites > > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > > Thumb] {0.18.6}[23920]: initialized > > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > > Thumb] {0.18.6}[23920]: starting ... > > > > Killed > > > > > 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 ☹ > > > > > Maybe someone has seen this before ? ---
**Author:** ![Tomasz\_Kloc](https://avatars.discourse-cdn.com/v4/letter/t/958977/32.png) [@Tomasz\_Kloc](https://discuss.elastic.co/u/Tomasz_Kloc)\ **Post date:** [January 3, 2012, 7:34pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/6 "2012-01-03T19:34:55Z")
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#6](http://www.hetzner.de/en/hosting/legal/system-policies-ws#6)Process 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](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. > > On Jan 3, 8:15 pm, Tomasz Kloc[tomek.kloc....@gmail.com](mailto:tomek.kloc....@gmail.com) wrote: > > > 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 😉 > > > > > On Jan 3, 7:50 pm, Shay Banon[kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > > 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). > > > > > > On Tue, Jan 3, 2012 at 8:02 PM, mrblue[john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com)wrote: > > > > > > > Hi, > > > > > > > when i try to start elasticsearch on my managed server, it goes like > > > > > this: > > > > > > > [2012-01-03 18:59:25,364][INFO][node] [Tom > > > > > Thumb] {0.18.6}[23920]: initializing ... > > > > > [2012-01-03 18:59:25,373][INFO][plugins] [Tom > > > > > Thumb] loaded , sites > > > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > > > Thumb] {0.18.6}[23920]: initialized > > > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > > > Thumb] {0.18.6}[23920]: starting ... > > > > > Killed > > > > > > > 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 ☹ > > > > > > > Maybe someone has seen this before ? ---
**Author:** ![mrblue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mrblue/32/23268_2.png) [@mrblue](https://discuss.elastic.co/u/mrblue)\ **Post date:** [January 3, 2012, 7:51pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/7 "2012-01-03T19:51:45Z")
I´ll have a look at this, thx. ..but i don´t have a shared server, it´s a managed server for 120€/ month ☹ On Jan 3, 8:34 pm, Tomasz Kloc [tomek.kloc....@gmail.com](mailto:tomek.kloc....@gmail.com) wrote: > 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#6](http://www.hetzner.de/en/hosting/legal/system-policies-ws#6)Process > 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](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. > > > On Jan 3, 8:15 pm, Tomasz Kloc[tomek.kloc....@gmail.com](mailto:tomek.kloc....@gmail.com) wrote: > > > > 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 😉 > > > > > On Jan 3, 7:50 pm, Shay Banon[kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > > > > 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). > > > > > > On Tue, Jan 3, 2012 at 8:02 PM, mrblue[john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com)wrote: > > > > > > > Hi, > > > > > > > when i try to start elasticsearch on my managed server, it goes like > > > > > > this: > > > > > > > [2012-01-03 18:59:25,364][INFO][node] [Tom > > > > > > Thumb] {0.18.6}[23920]: initializing ... > > > > > > [2012-01-03 18:59:25,373][INFO][plugins] [Tom > > > > > > Thumb] loaded , sites > > > > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > > > > Thumb] {0.18.6}[23920]: initialized > > > > > > [2012-01-03 18:59:27,788][INFO][node] [Tom > > > > > > Thumb] {0.18.6}[23920]: starting ... > > > > > > Killed > > > > > > > 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 ☹ > > > > > > > Maybe someone has seen this before ? ---
**Author:** ![drewr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewr/32/7803_2.png) [@drewr](https://discuss.elastic.co/u/drewr)\ **Post date:** [January 3, 2012, 8:35pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/8 "2012-01-03T20:35:41Z")
mrblue wrote: > I´ll have a look at this, thx. > ..but i don´t have a shared server, it´s a managed server for 120€/ > month ☹ It doesn't quite fit the behavior, but check if there are oom-killer messages in your kernel log (assuming this is Linux). You could also try strace/ktrace/dtrace-ing the JVM process to see if that reveals any clues. -Drew ---
**Author:** ![mrblue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mrblue/32/23268_2.png) [@mrblue](https://discuss.elastic.co/u/mrblue)\ **Post date:** [January 4, 2012, 5:22pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/9 "2012-01-04T17:22:14Z")
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 ? thx for your help, great community here On Jan 3, 9:35 pm, Drew Raines [aarai...@gmail.com](mailto:aarai...@gmail.com) wrote: > mrblue wrote: > > > I´ll have a look at this, thx. > > ..but i don´t have a shared server, it´s a managed server for 120€/ > > month ☹ > > It doesn't quite fit the behavior, but check if there are oom-killer > messages in your kernel log (assuming this is Linux). > > You could also try strace/ktrace/dtrace-ing the JVM process to see > if that reveals any clues. > > -Drew ---
**Author:** ![drewr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewr/32/7803_2.png) [@drewr](https://discuss.elastic.co/u/drewr)\ **Post date:** [January 4, 2012, 9:07pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/10 "2012-01-04T21:07:31Z")
mrblue wrote: > 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. -Drew ---
**Author:** ![James\_Chisholm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_chisholm/32/2539_2.png) [@James\_Chisholm](https://discuss.elastic.co/u/James_Chisholm)\ **Post date:** [January 5, 2012, 3:03am UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/11 "2012-01-05T03:03:22Z")
If it's not logging anything... does the user that elasticsearch is running at have write permissions to the log folder? On Jan 5, 8:07 am, Drew Raines [aarai...@gmail.com](mailto:aarai...@gmail.com) wrote: > mrblue wrote: > > > 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. > > -Drew ---
**Author:** ![mrblue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mrblue/32/23268_2.png) [@mrblue](https://discuss.elastic.co/u/mrblue)\ **Post date:** [January 5, 2012, 8:29am UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/12 "2012-01-05T08:29:05Z")
I can access /var/log but not every file there + there is no file that "looks" like the right one. On Jan 5, 4:03 am, James Chisholm [ja...@someones.com](mailto:ja...@someones.com) wrote: > If it's not logging anything... does the user that elasticsearch is > running at have write permissions to the log folder? > > On Jan 5, 8:07 am, Drew Raines [aarai...@gmail.com](mailto:aarai...@gmail.com) wrote: > > > mrblue wrote: > > > > > 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. > > > -Drew ---
**Author:** ![mrblue](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mrblue/32/23268_2.png) [@mrblue](https://discuss.elastic.co/u/mrblue)\ **Post date:** [January 5, 2012, 2:48pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/13 "2012-01-05T14:48:13Z")
Allowing the JVM to use more RAM did the trick 🙂 On Jan 5, 9:29 am, mrblue [john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com) wrote: > I can access /var/log but not every file there + there is no file that > "looks" like the right one. > > On Jan 5, 4:03 am, James Chisholm [ja...@someones.com](mailto:ja...@someones.com) wrote: > > > If it's not logging anything... does the user that elasticsearch is > > running at have write permissions to the log folder? > > > On Jan 5, 8:07 am, Drew Raines [aarai...@gmail.com](mailto:aarai...@gmail.com) wrote: > > > > mrblue wrote: > > > > > > > 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. > > > > -Drew ---
**Author:** ![hazzadous](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hazzadous/32/1654_2.png) [@hazzadous](https://discuss.elastic.co/u/hazzadous)\ **Post date:** [July 4, 2012, 5:26pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/14 "2012-07-04T17:26:09Z")
I'm having issues getting things running on Hetzner too. Although not exactly the same issues as you had (my symptoms are [https://groups.google.com/d/topic/elasticsearch/uqLCOYjit-o/discussion](https://groups.google.com/d/topic/elasticsearch/uqLCOYjit-o/discussion)) I'd be interested to know what setup you have. On Thursday, January 5, 2012 2:48:13 PM UTC, mrblue wrote: > Allowing the JVM to use more RAM did the trick 🙂 > > On Jan 5, 9:29 am, mrblue [john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com) wrote: > > > I can access /var/log but not every file there + there is no file that > > "looks" like the right one. > > > > On Jan 5, 4:03 am, James Chisholm [ja...@someones.com](mailto:ja...@someones.com) wrote: > > > > > If it's not logging anything... does the user that elasticsearch is > > > running at have write permissions to the log folder? > > > > > On Jan 5, 8:07 am, Drew Raines [aarai...@gmail.com](mailto:aarai...@gmail.com) wrote: > > > > > > mrblue wrote: > > > > > > > > > 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. > > > > > > -Drew ---
**Author:** ![hazzadous](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hazzadous/32/1654_2.png) [@hazzadous](https://discuss.elastic.co/u/hazzadous)\ **Post date:** [July 4, 2012, 6:15pm UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/15 "2012-07-04T18:15:33Z")
The issue for me was the dreaded leap second issue, all smiles now. On Wednesday, July 4, 2012 6:26:09 PM UTC+1, hazzadous wrote: > I'm having issues getting things running on Hetzner too. Although not > exactly the same issues as you had (my symptoms are > [https://groups.google.com/d/topic/elasticsearch/uqLCOYjit-o/discussion](https://groups.google.com/d/topic/elasticsearch/uqLCOYjit-o/discussion)) > I'd be interested to know what setup you have. > > On Thursday, January 5, 2012 2:48:13 PM UTC, mrblue wrote: > > > Allowing the JVM to use more RAM did the trick 🙂 > > > > On Jan 5, 9:29 am, mrblue [john.agricola...@googlemail.com](mailto:john.agricola...@googlemail.com) wrote: > > > > > I can access /var/log but not every file there + there is no file that > > > "looks" like the right one. > > > > > > On Jan 5, 4:03 am, James Chisholm [ja...@someones.com](mailto:ja...@someones.com) wrote: > > > > > > > If it's not logging anything... does the user that elasticsearch is > > > > running at have write permissions to the log folder? > > > > > > > On Jan 5, 8:07 am, Drew Raines [aarai...@gmail.com](mailto:aarai...@gmail.com) wrote: > > > > > > > > mrblue wrote: > > > > > > > > > > > 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. > > > > > > > > -Drew ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:21am UTC](https://discuss.elastic.co/t/instant-crash-on-startup/6273/16 "2017-07-06T03:21:30Z")