lschiere at pidgin.im
Tue Jun 30 19:26:47 EDT 2009
-----BEGIN PGP SIGNED MESSAGE-----
However, the problem seems to have cleared up. I'm going to guess
that our providers increased or memory allocation.
On Jun 30, 2009, at 19:24 EDT, Luke Schierer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> The logcheck emails for about 3 consecutive hours around the time I
> sent the first email, showed a ton of processes, including postfix
> (which relays mail to rock, primarily for trac) and lighttpd,
> failing to allocate memory.
> On Jun 30, 2009, at 16:28 EDT, Mark Doliner wrote:
>> On Tue, Jun 30, 2009 at 9:25 AM, Ethan Blanton<elb at pidgin.im> wrote:
>>> Luke Schierer spake unto us the following wisdom:
>>>> If someone with access could take a look at imperial, I do not
>>>> have ssh
>>>> access right now. It seems to be having memory allocation issues.
>>> It's using a bit more than half of its RAM (although I notice that
>>> has no swap‽). The load average is pretty moderate (about 5).
>>> leads you to suspect this problem?
>> My nightly cronjob to generate l10n stats and doxygen emailed me
>> this result:
>> /home/markdoliner/bin/update_l10n_stats.sh: fork: Cannot allocate
>> Error: update_l10n_stats.sh failed. Exiting
>> I didn't investigate, but I ran the script again by hand and it
>> worked fine.
>> Devel mailing list
>> Devel at pidgin.im
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
> -----END PGP SIGNATURE-----
> Devel mailing list
> Devel at pidgin.im
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----
More information about the Devel