On 04/12/2014 02:07 AM, Sebastian Silva wrote:
Here I just got home. Sorry for the inconvenience I might have caused.
Bernie, do you know which log was/is growing out of hand?
Both access.log and node.sugarlabs.org.log. I discarded the first and
compressed the second (it compresses very
Here I just got home. Sorry for the inconvenience I might have caused.
Bernie, do you know which log was/is growing out of hand?
Here's a report on everything I know about the issue.
We've been experiencing some performance degradation and also some
downtime in Sugar Network services (this is
I know nothing about our infraestructure but,
is possible run proyects in development,
like Sugar Network in a different server/vm
than critical services like git?
Gonzalo
On Sat, Apr 12, 2014 at 6:07 AM, Sebastian Silva
sebast...@fuentelibre.orgwrote:
Here I just got home. Sorry for the
If it is necessary it could be moved.
Sugar Network at this point is in production and we do have a process
for deployment (there is testing and devel instance).
Alsroot has had a pretty good track record of keeping git up and
running. I think it's a shame people are moving to github.
What we
I was notified that git.sugarlabs.org was showing errors.
After some head scraping I realized that the root filesystem on jita was
full. I looked around and found giant request logs containing millions
of requests apparently originating from XOs located in Peru.
We've been DDOSed by our own
Thanks Berni :)
On Sat, Apr 12, 2014 at 12:51 AM, Bernie Innocenti ber...@sugarlabs.orgwrote:
I was notified that git.sugarlabs.org was showing errors.
After some head scraping I realized that the root filesystem on jita was
full. I looked around and found giant request logs containing
6 matches
Mail list logo
