You know something, I just realized it's on a VM that only has 1 gig. Let
me at least get up to the 2GB documented gitlab minimum. Will keep an eye
on it, but I bet you just nailed it.
Thanks much for the assist.
On Wed, Feb 17, 2016 at 3:09 PM, Stan Hu wrote:
> It looks to me the worker abrup
It looks to me the worker abruptly terminates due to lack of memory. How
much RAM does your machine have?
On Wed, Feb 17, 2016 at 11:42 AM, Michael Albert wrote:
> Not exactly sure what to look for in the sidekiq log, but the only thing
> standing out to me are a bunch of "Cannot allocate memor
Not exactly sure what to look for in the sidekiq log, but the only thing
standing out to me are a bunch of "Cannot allocate memory - ps" warnings.
Hopefully helpful?
2016-02-16_22:14:44.75819 2016-02-16T22:14:44.757Z 11097 TID-aznpw
ProjectServiceWorker JID-174ef3e92c00664ffe75439a INFO: start
201
Actually, I don't think that bug fixes this specific problem. It looks to
me that the Sidekiq task keeps re-running for some reason, perhaps because
it didn't get a 200 response from the endpoint in time. Can you check
/var/log/gitlab/sidekiq/current to see if there are errors?
On Wed, Feb 17, 20
On 02/16/2016 11:35 PM, m...@askkodiak.com wrote:
> Rocking GitLab community edition with Slack integration for
> issues/commits/etc. Have been using since last April or so. Recently
> started seeing duplicate updates trickle out of GitLab as shown in the
> attached screenshot. Am I alone? Anyone g
