I've fixed the famous "Max 1024 open files allowed" warning as per instructions in the documentation and it worked good for a while. Then I ran out of disk space in my ec2 instance so I increased the size of my volume. Now when I start neo4j I get the same warning again. However /etc/security/limits.conf and also ulimit -n seem to show me the right value:
root hard core 150000 ubuntu soft nofile 150000 ubuntu hard nofile 150000
On Sat, Oct 6, 2012 at 4:07 PM, Yaron Naveh <yaron...@gmail.com> wrote:
> I've fixed the famous "Max 1024 open files allowed" warning as per
> instructions in the documentation and it worked good for a while.
> Then I ran out of disk space in my ec2 instance so I increased the size of
> my volume.
> Now when I start neo4j I get the same warning again. However
> /etc/security/limits.conf and also ulimit -n seem to show me the right
> value:
> root hard core 150000
> ubuntu soft nofile 150000
> ubuntu hard nofile 150000
> On Sat, Oct 6, 2012 at 4:07 PM, Yaron Naveh <yaron...@gmail.com> wrote:
> > I've fixed the famous "Max 1024 open files allowed" warning as per
> > instructions in the documentation and it worked good for a while.
> > Then I ran out of disk space in my ec2 instance so I increased the size
> of
> > my volume.
> > Now when I start neo4j I get the same warning again. However
> > /etc/security/limits.conf and also ulimit -n seem to show me the right
> > value:
> > root hard core 150000
> > ubuntu soft nofile 150000
> > ubuntu hard nofile 150000
On Mon, Oct 8, 2012 at 6:39 PM, Yaron Naveh <yaron...@gmail.com> wrote:
> Thanks, turns out neo4j runs under a different user in the new volume, not
> sure why
> On Mon, Oct 8, 2012 at 11:39 AM, Peter Neubauer
> <peter.neuba...@neotechnology.com> wrote:
>> Yaron,
>> in that case, there might be something not working properly with
>> On Sat, Oct 6, 2012 at 4:07 PM, Yaron Naveh <yaron...@gmail.com> wrote:
>> > I've fixed the famous "Max 1024 open files allowed" warning as per
>> > instructions in the documentation and it worked good for a while.
>> > Then I ran out of disk space in my ec2 instance so I increased the size
>> > of
>> > my volume.
>> > Now when I start neo4j I get the same warning again. However
>> > /etc/security/limits.conf and also ulimit -n seem to show me the right
>> > value:
>> > root hard core 150000
>> > ubuntu soft nofile 150000
>> > ubuntu hard nofile 150000
peter.neuba...@neotechnology.com> wrote:
> That is strange. Could that be something with the Linux setup? Is the
> only difference the added volume causing this?
> On Mon, Oct 8, 2012 at 6:39 PM, Yaron Naveh <yaron...@gmail.com> wrote:
> > Thanks, turns out neo4j runs under a different user in the new volume,
> not
> > sure why
> > On Mon, Oct 8, 2012 at 11:39 AM, Peter Neubauer
> > <peter.neuba...@neotechnology.com> wrote:
> >> Yaron,
> >> in that case, there might be something not working properly with
> >> On Sat, Oct 6, 2012 at 4:07 PM, Yaron Naveh <yaron...@gmail.com> wrote:
> >> > I've fixed the famous "Max 1024 open files allowed" warning as per
> >> > instructions in the documentation and it worked good for a while.
> >> > Then I ran out of disk space in my ec2 instance so I increased the
> size
> >> > of
> >> > my volume.
> >> > Now when I start neo4j I get the same warning again. However
> >> > /etc/security/limits.conf and also ulimit -n seem to show me the right
> >> > value:
On Mon, Oct 8, 2012 at 7:57 PM, Yaron Naveh <yaron...@gmail.com> wrote:
> Not sure, I am checking. This does not seem to be related to neo4j but to
> the system.
> Thanks,
> Yaron
> On Mon, Oct 8, 2012 at 7:53 PM, Peter Neubauer
> <peter.neuba...@neotechnology.com> wrote:
>> That is strange. Could that be something with the Linux setup? Is the
>> only difference the added volume causing this?
>> On Mon, Oct 8, 2012 at 6:39 PM, Yaron Naveh <yaron...@gmail.com> wrote:
>> > Thanks, turns out neo4j runs under a different user in the new volume,
>> > not
>> > sure why
>> > On Mon, Oct 8, 2012 at 11:39 AM, Peter Neubauer
>> > <peter.neuba...@neotechnology.com> wrote:
>> >> Yaron,
>> >> in that case, there might be something not working properly with
>> >> On Sat, Oct 6, 2012 at 4:07 PM, Yaron Naveh <yaron...@gmail.com> wrote:
>> >> > I've fixed the famous "Max 1024 open files allowed" warning as per
>> >> > instructions in the documentation and it worked good for a while.
>> >> > Then I ran out of disk space in my ec2 instance so I increased the
>> >> > size
>> >> > of
>> >> > my volume.
>> >> > Now when I start neo4j I get the same warning again. However
>> >> > /etc/security/limits.conf and also ulimit -n seem to show me the
>> >> > right
>> >> > value:
