Hey all,
thanks for exaplanation and solving this issue.
.tommy
On 19 September 2016 at 08:47, Daniel Carosone
wrote:
> That was definitely it - despite that it says it's *using* 0 swap :)
>
> Thanks again.
>
> On 19 September 2016 at 09:18, Daniel Carosone
> wrote:
>
>> On 18 Sep 2016 11:47, "
That was definitely it - despite that it says it's *using* 0 swap :)
Thanks again.
On 19 September 2016 at 09:18, Daniel Carosone
wrote:
> On 18 Sep 2016 11:47, "Joshua M. Clulow" wrote:
> >
> > Alignment issues are generally less common on x86 systems
>
> Yeah, I parked the project for lack o
On 18 Sep 2016 11:47, "Joshua M. Clulow" wrote:
>
> Alignment issues are generally less common on x86 systems
Yeah, I parked the project for lack of time, on the assumption it would be
a non-trivial debugging exercise.
I'm sure what you describe is the issue.
-
On 18 Sep 2016 09:30, "Joshua M. Clulow" wrote:
>
> We force the MAP_NORESERVE flag for some mmap() allocations made by LX
> branded processes[1]. If there is a subsequent run on the bank, we
> kill the process that would have overrun the swap cap in the zone with
> SIGBUS, rather than random oth
On 17 September 2016 at 16:39, Joe Landman
wrote:
> On 09/17/2016 07:30 PM, Joshua M. Clulow wrote:
>> The SIGBUS you're seeing is potentially the result of our attempt to
>> get _some_ of the way toward overcommit, so that Linux software can
>> work even when it mistakenly assumes memory is an in
If I'm not mistaken, the omnibus installation performs sizing based
upon apparent available memory. If the max_swap for you zone equals
the max_physical_memory, then the expectation of Linux overcommit
semantics is likely to cause problems. I would recommend cranking the
max_swap up for the insta
Should be redis
That sysctl vm.overcommit_memory is set to 0 is error message during redis
start.
.tommy
On 18 September 2016 at 01:39, Joe Landman
wrote:
>
>
> On 09/17/2016 07:30 PM, Joshua M. Clulow wrote:
>
>> On 17 September 2016 at 15:39, Daniel Carosone
>> wrote:
>>
>>> I tried this a co
On 09/17/2016 07:30 PM, Joshua M. Clulow wrote:
On 17 September 2016 at 15:39, Daniel Carosone
wrote:
I tried this a couple of weeks ago, with no luck either. I was getting some
(apparently random) SIGBUS backtraces from ruby in amongst the logs.
Linux allows for pretty flagrant memory over
On 17 September 2016 at 15:39, Daniel Carosone
wrote:
> I tried this a couple of weeks ago, with no luck either. I was getting some
> (apparently random) SIGBUS backtraces from ruby in amongst the logs.
Linux allows for pretty flagrant memory over-commit; that is, programs
may allocate a lot mor
Update:
I tried on newer Smartos - joyent_20160901T054050Z - and with 8G ram it
works just ok.
.tommy
On 18 September 2016 at 00:45, tom my wrote:
> There is missing Postgres extension pg_trgm.
> I tried it in native zone.
>
> On 18 September 2016 at 00:39, Daniel Carosone
> wrote:
>
>> I tried
There is missing Postgres extension pg_trgm.
I tried it in native zone.
On 18 September 2016 at 00:39, Daniel Carosone
wrote:
> I tried this a couple of weeks ago, with no luck either. I was getting
> some (apparently random) SIGBUS backtraces from ruby in amongst the logs.
>
> I had no chance t
I tried this a couple of weeks ago, with no luck either. I was getting some
(apparently random) SIGBUS backtraces from ruby in amongst the logs.
I had no chance to investigate further at the time, but I'd be very keen to
see this work - either the lazy omnibus LX way, or with as many as possible
o
Hi Jason
and thanks but didn't work for me. :)
I reconfigured memory settings for existing VM and than created fresh lx
zones (ubuntu 16 and debian 8) with 8g memory. No luck.
I'm running Smartos - SunOS xba1 5.11 joyent_20160609T010930Z i86pc i386
i86pc
Sorry, what do you mean by "retry with a bi
Hi Tommy,I just tried this in US-EAST-1
with….triton create debian-8 g4-general-8GThen….1 sudo apt-get install curl openssh-server ca-certificates postfix
2 curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
3 sudo apt-get install gi
Hey all,
just a try.
I installed Gitlab on LX zone (tested centos, ubuntu, debian) using
Gitlab's recommended Omnibus installation.
I configured lx-zone with 4GB memory.
Installation went ok, however I can't access Gitlab's web, receiving error
"Cannot allocate memory - fork(2) (Errno::ENOMEM)" ev
15 matches
Mail list logo
