Thanks for the strace suggestion, this is what my trace returns. I'm looking into what futex is now.
[root@localhost elasticsearch]# sudo service elasticsearch start Starting elasticsearch: [ OK ] [root@localhost elasticsearch]# sudo service elasticsearch status elasticsearch (pid 16887) is running... [root@localhost elasticsearch]# strace -p 16887 \Process 16887 attached - interrupt to quit futex(0x7f97ed4279d0, FUTEX_WAIT, 16889, NUL <unfinished ...> +++ killed by SIGKILL +++ [root@localhost elasticsearch]# sudo service elasticsearch start Starting elasticsearch: [ OK ] [root@localhost elasticsearch]# sudo service elasticsearch status elasticsearch (pid 16958) is running... [root@localhost elasticsearch]# strace -p 16958 Process 16958 attached - interrupt to quit futex(0x7f0a7e8089d0, FUTEX_WAIT, 16960, NULL <unfinished ...> +++ killed by SIGKILL +++ *-Jef Statham* Without vices there would be no virtues. It’s a magical world, Hobbes, ol’ buddy…Let’s go exploring! On Mon, Nov 3, 2014 at 2:01 PM, Alexandre Rafalovitch <[email protected]> wrote: > Lack of permissions on filesystem access? Unexpected directory. > > Something like dtrace/truss/strace might be useful here. > On 03/11/2014 1:19 pm, "Jef Statham" <[email protected]> wrote: > >> I'm running elasticsearch on Centos using the *serivce elasticsearch >> start. *The service happily stays running until it receives its first >> request causing it to die. >> *service elasticsearch status* returns >> >> elasticsearch dead but pid file exists >> >> This same problem doesn't exist when I run elasticsearch with >> *./bin/elasticsearch* >> >> With logging set to trace I see no stacktrace in the logs or any >> indication the service went down. >> >> >> Where else can I look to find why elasticsearch will not accept request >> running as a service? >> >> >> More info: >> Elasticsearch >> version:{ >> number: "1.3.4", >> build_hash: "a70f3ccb52200f8f2c87e9c370c6597448eb3e45", >> build_timestamp: "2014-09-30T09:07:17Z", >> build_snapshot: false, >> lucene_version: "4.9" >> >> CentOS 6.5 >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/f71b44e6-540c-4213-a8bb-e1de5b2f6257%40googlegroups.com >> <https://groups.google.com/d/msgid/elasticsearch/f71b44e6-540c-4213-a8bb-e1de5b2f6257%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elasticsearch/2tIe5i2b-TA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAEFAe-G463EttK_d0uS4w-9fxAxter0gDx-M3ppHWhEuSB4L6g%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAEFAe-G463EttK_d0uS4w-9fxAxter0gDx-M3ppHWhEuSB4L6g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CABj%3DZj8sWJPb2ATE8o%2Bpf36GNSF%3Dws7%3DkBo4pR%2BJmfjiXZ8rjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
