[ejabberd] High filesystem usage

Kirk Bateman kirk.bateman at gmail.com
Wed Feb 10 20:25:46 MSK 2010


You are most welcome. Always nice to be of help to someone.

Cheers

Kirk

On 10 February 2010 17:10, Matias <matiassurdi at gmail.com> wrote:

> El 10/02/10 18:07, Kirk Bateman escribió:
>
>> Matias,
>>
>> If I remember properly, the general principle is:
>>
>> 1. Use logrotate or something to rotate the logfiles..
>> 2. Call ejabberdctl reopen-log
>>
>> Cheers
>>
>> Kirk
>>
>> On 10 February 2010 17:05, Matias <matiassurdi at gmail.com
>> <mailto:matiassurdi at gmail.com>> wrote:
>>
>>    El 10/02/10 16:51, Kirk Bateman escribió:
>>
>>        ejabberdctl reopen_log ?
>>
>>        Cheers
>>
>>        Kirk
>>
>>        On 10 February 2010 15:48, Matias <matiassurdi at gmail.com
>>        <mailto:matiassurdi at gmail.com>
>>        <mailto:matiassurdi at gmail.com <mailto:matiassurdi at gmail.com>>>
>>
>>        wrote:
>>
>>            El 10/02/10 15:05, Gerhard Schmidt escribió:
>>
>>                Matias schrieb:
>>
>>                    I'm runing ejabberd-2.1-2 on
>>
>>                    FreeBSD it05 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat
>>        Nov 21
>>                    15:02:08 UTC
>>                    2009
>>        root at mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
>>                    amd64
>>
>>                    Suddenly, my /var partition is running out of space.
>>
>>
>>                Do you rotate your logfiles with newsyslog or something
>>        similar
>>                without
>>                restarting the ejabberd? EJabberd might not reopen the
>>        logfile.
>>
>>                So ejabber will continue to write to the rotated file.
>>        When the
>>                logfile is
>>                finally deleted the Directory entry for this file goes
>>        away but
>>                the file still
>>                exists and grows on.
>>
>>                Had this problem with innd some times ago.
>>
>>                Regards
>>                     Estartu
>>
>>
>>            This seems to be the problem. Is there any signal I can send
>>        to the
>>            ejabbed process to restart the loggin system, without having to
>>            restart entirely the process and force all clients to go
>>        offline and
>>            reconnect?
>>
>>
>>            Thanks for your help!
>>
>>
>>
>>
>>
>>            _______________________________________________
>>            ejabberd mailing list
>>        ejabberd at jabber.ru <mailto:ejabberd at jabber.ru>
>>        <mailto:ejabberd at jabber.ru <mailto:ejabberd at jabber.ru>>
>>
>>
>>        http://lists.jabber.ru/mailman/listinfo/ejabberd
>>
>>
>>
>>
>>        _______________________________________________
>>        ejabberd mailing list
>>        ejabberd at jabber.ru <mailto:ejabberd at jabber.ru>
>>        http://lists.jabber.ru/mailman/listinfo/ejabberd
>>
>>
>>
>>    AWESOME!!!!!
>>
>>
>>    Thank you very much for your help.
>>
>>
>>
>>
>>
>>
>>    _______________________________________________
>>    ejabberd mailing list
>>    ejabberd at jabber.ru <mailto:ejabberd at jabber.ru>
>>    http://lists.jabber.ru/mailman/listinfo/ejabberd
>>
>>
>>
>>
>> _______________________________________________
>> ejabberd mailing list
>> ejabberd at jabber.ru
>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>
>
>
> Yes, as it seems that FreeBSD's newsyslog can't run commands after log
> rotation, I've setup a cron job one minute after the rotation to run that
> command.
>
> Thanks a lot!
>
>
>
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20100210/f854fdb4/attachment-0001.html>


More information about the ejabberd mailing list