questions: /var/tmp/airtime space requirement
  • Vote Up0Vote Down Ed PorrasEd Porras
    Posts: 37Member
    Hi,

    We ran into a problem today where Airtime would not allow logins and noticed the cause is due to the root partition being out of space. I noticed that /var/tmp/airtime was using over 4GB (thus, filling up / which was only 12G) so I was wondering if you have an idea of the minimum space required here? I can add a separate partition for /var but would like to know how big to make it.

    I do already have a separate (very large) partition for /srv.

    Thank you.
  • 9 Comments sorted by
  • Vote Up0Vote Down Paul BaranowskiPaul Baranowski
    Posts: 389Member, Administrator, Sourcefabric Team
    Can you please check if there are a lot of files in
    "/var/tmp/airtime/show-recorder"? I just checked and it looks like the temp
    files created there are not being deleted.


    Paul Baranowski
    CTO, Sourcefabric, http://sourcefabric.org

    +1 (416) 832-6436 (Cell)
    Skype: paulbaranowski
    720 Bathurst St. / Suite 203 / Toronto / ON / M5S 2R4 / Canada



    On Thu, Jul 7, 2011 at 11:38 AM, Ed Porras <
    airtime-support@lists.sourcefabric.org> wrote:

    > **
    > Hi,
    >
    > We ran into a problem today where Airtime would not allow logins and
    > noticed the cause is due to the root partition being out of space. I noticed
    > that /var/tmp/airtime was using over 4GB (thus, filling up / which was only
    > 12G) so I was wondering if you have an idea of the minimum space required
    > here? I can add a separate partition for /var but would like to know how big
    > to make it.
    >
    > I do already have a separate (very large) partition for /srv.
    >
    > Thank you.
    >
    >

  • Vote Up0Vote Down Ed PorrasEd Porras
    Posts: 37Member
    On Jul 7, 2011, at 3:09 PM, Paul Baranowski wrote:
    > Can you please check if there are a lot of files in
    > "/var/tmp/airtime/show-recorder"? I just checked and it looks like the temp
    > files created there are not being deleted.

    Hi Paul,

    There's nothing there. The vast content is in pypo/cache:

    58M	./pypo/cache/scheduler/2011-07-08-13-49-43
57M	./pypo/cache/scheduler/2011-07-08-15-31-09
150M	./pypo/cache/scheduler/2011-07-07-22-38-00
335M	./pypo/cache/scheduler/2011-07-07-02-59-46
58M	./pypo/cache/scheduler/2011-07-08-14-40-26
499M	./pypo/cache/scheduler/2011-07-07-00-01-23
499M	./pypo/cache/scheduler/2011-07-07-02-02-17
499M	./pypo/cache/scheduler/2011-07-07-00-59-34
58M	./pypo/cache/scheduler/2011-07-08-12-59-00
499M	./pypo/cache/scheduler/2011-07-06-22-59-14
2.7G	./pypo/cache/scheduler
2.7G	./pypo/cache
4.0K	./pypo/files
4.0K	./pypo/tmp
2.7G	./pypo
4.0K	./show-recorder


    Looks like old playlists are not cleaned up?

    -e
    --
    Ed Porras
    http://www.digressed.net/

  • Vote Up0Vote Down Paul BaranowskiPaul Baranowski
    Posts: 389Member, Administrator, Sourcefabric Team
    As a temporary solution, you can delete any of those directories that are
    older than today. We are looking into this to see if we can reproduce this
    problem.

    Paul Baranowski
    CTO, Sourcefabric, http://sourcefabric.org

    +1 (416) 832-6436 (Cell)
    Skype: paulbaranowski
    720 Bathurst St. / Suite 203 / Toronto / ON / M5S 2R4 / Canada



    On Thu, Jul 7, 2011 at 11:23 PM, Ed Porras <
    airtime-support@lists.sourcefabric.org> wrote:

    > **
    > On Jul 7, 2011, at 3:09 PM, Paul Baranowski wrote:
    > > Can you please check if there are a lot of files in
    > > "/var/tmp/airtime/show-recorder"? I just checked and it looks like the
    > temp
    > > files created there are not being deleted.
    >
    > Hi Paul,
    >
    > There's nothing there. The vast content is in pypo/cache:
    >
    > 58M ./pypo/cache/scheduler/2011-07-08-13-49-43
    > 57M ./pypo/cache/scheduler/2011-07-08-15-31-09
    > 150M ./pypo/cache/scheduler/2011-07-07-22-38-00
    > 335M ./pypo/cache/scheduler/2011-07-07-02-59-46
    > 58M ./pypo/cache/scheduler/2011-07-08-14-40-26
    > 499M ./pypo/cache/scheduler/2011-07-07-00-01-23
    > 499M ./pypo/cache/scheduler/2011-07-07-02-02-17
    > 499M ./pypo/cache/scheduler/2011-07-07-00-59-34
    > 58M ./pypo/cache/scheduler/2011-07-08-12-59-00
    > 499M ./pypo/cache/scheduler/2011-07-06-22-59-14
    > 2.7G ./pypo/cache/scheduler
    > 2.7G ./pypo/cache
    > 4.0K ./pypo/files
    > 4.0K ./pypo/tmp
    > 2.7G ./pypo
    > 4.0K ./show-recorder
    >
    > Looks like old playlists are not cleaned up?
    >
    > -e
    > --
    > Ed Porras
    > http://www.digressed.net/
    >
    >
    >

  • Vote Up0Vote Down Ed PorrasEd Porras
    Posts: 37Member
    Hi Paul,

    I've worked around it for now by creating a tmp directory under /srv (since it's a separate partition) and sym-linking it from /var but would like to revert things if it does get resolved.

    I can try to delete the older ones but do have a question: we're running some tests to train people, etc. while not on the air (we share our frequency with two other LP stations) and sometimes we just reuse some of the existing playlists. Do you know if this would affect that or will Airtime re-generate the playlist for the repeated instance?

    Does that make sense?

    Thanks.
  • Vote Up0Vote Down Paul BaranowskiPaul Baranowski
    Posts: 389Member, Administrator, Sourcefabric Team
    Every show is completely standalone, specifically:
    1) Adding a playlist to show and then delete the playlist --> the show still
    has the correct content (i.e. it has a copy of the playlist)
    2) pypo downloads a complete copy of the show for playout for every show,
    even if it is a repeat. The original audio files are kept separately. So
    you can delete the pypo cache for past shows and nothing bad will happen.


    Paul Baranowski
    CTO, Sourcefabric, http://sourcefabric.org

    +1 (416) 832-6436 (Cell)
    Skype: paulbaranowski
    720 Bathurst St. / Suite 203 / Toronto / ON / M5S 2R4 / Canada



    On Tue, Jul 12, 2011 at 2:48 PM, Ed Porras <
    airtime-support@lists.sourcefabric.org> wrote:

    > **
    > Hi Paul,
    >
    > I've worked around it for now by creating a tmp directory under /srv (since
    > it's a separate partition) and sym-linking it from /var but would like to
    > revert things if it does get resolved.
    >
    > I can try to delete the older ones but do have a question: we're running
    > some tests to train people, etc. while not on the air (we share our
    > frequency with two other LP stations) and sometimes we just reuse some of
    > the existing playlists. Do you know if this would affect that or will
    > Airtime re-generate the playlist for the repeated instance?
    >
    > Does that make sense?
    >
    > Thanks.
    >
    >

  • Vote Up0Vote Down Martin KonecnyMartin Konecny
    Posts: 1,860Member
    Hi Ed,

    Im having trouble recreating this bug. Do you still have the logs for pypo (/var/log/airtime/pypo/pypo.log)?

    Edit: Sorry for 1.8.2 the path is something similar to:

    /var/log/airtime/pypo/log/main/current
    Airtime Pro Hosting: http://airtime.pro
  • Vote Up0Vote Down Ed PorrasEd Porras
    Posts: 37Member
    Hi Paul,

    (Edit: Oops, I mean Martin. Sorry)

    The file seems to only be for today - perhaps why it's named 'current' :/ - but I'm attaching it anyway.

    Here is the current state of the folder:

    root@tower2:/srv/airtime-tmp# du
29M     ./pypo/cache/scheduler/2011-07-12-19-59-00
454M    ./pypo/cache/scheduler/2011-07-11-22-30-14
141M    ./pypo/cache/scheduler/2011-07-12-12-59-00
141M    ./pypo/cache/scheduler/2011-07-12-15-01-14
29M     ./pypo/cache/scheduler/2011-07-12-20-00-10
454M    ./pypo/cache/scheduler/2011-07-11-23-01-47
141M    ./pypo/cache/scheduler/2011-07-12-14-00-37
141M    ./pypo/cache/scheduler/2011-07-12-13-00-19
454M    ./pypo/cache/scheduler/2011-07-12-02-02-06
454M    ./pypo/cache/scheduler/2011-07-12-03-59-37
454M    ./pypo/cache/scheduler/2011-07-12-03-02-09
454M    ./pypo/cache/scheduler/2011-07-12-00-58-34
454M    ./pypo/cache/scheduler/2011-07-12-00-01-44
3.8G    ./pypo/cache/scheduler
3.8G    ./pypo/cache
4.0K    ./pypo/files
4.0K    ./pypo/tmp
3.8G    ./pypo
4.0K    ./show-recorder
3.8G    .


    I did a DB cleanup on Sunday and we've only been on the air for two days so I can't tell if there's some flushing going on yet. I'll keep and eye on it and let you know.
  • Vote Up0Vote Down Paul BaranowskiPaul Baranowski
    Posts: 389Member, Administrator, Sourcefabric Team
    Oh I see what is going on - I didnt bother to check your cache folder times
    earlier - all of those shows are within the past 24 hours, it's just that
    you seem to have really huge files. Out of curiosity, what bitrate are you
    using? The cache cleans up anything older that a day. If you want to
    delete shows in the past more aggressively, then edit your
    /etc/airtime/pypo.cfg file and change the value "cache_for" to something
    less than 24 hours - 6 hours for example. Just dont set it shorter than your
    longest show. Then restart pypo with "airtime-pypo-stop" and
    "airtime-pypo-start". Please let me know how it goes.

    Paul Baranowski
    CTO, Sourcefabric, http://sourcefabric.org

    +1 (416) 832-6436 (Cell)
    Skype: paulbaranowski
    720 Bathurst St. / Suite 203 / Toronto / ON / M5S 2R4 / Canada



    On Tue, Jul 12, 2011 at 10:37 PM, Ed Porras <
    airtime-support@lists.sourcefabric.org> wrote:

    > **
    > Hi Paul,
    >
    > The file seems to only be for today - perhaps why it's named 'current' :/ -
    > but I'm attaching it anyway.
    >
    > Here is the current state of the folder:
    >
    > root@tower2:/srv/airtime-tmp# du
    > 29M ./pypo/cache/scheduler/2011-07-12-19-59-00
    > 454M ./pypo/cache/scheduler/2011-07-11-22-30-14
    > 141M ./pypo/cache/scheduler/2011-07-12-12-59-00
    > 141M ./pypo/cache/scheduler/2011-07-12-15-01-14
    > 29M ./pypo/cache/scheduler/2011-07-12-20-00-10
    > 454M ./pypo/cache/scheduler/2011-07-11-23-01-47
    > 141M ./pypo/cache/scheduler/2011-07-12-14-00-37
    > 141M ./pypo/cache/scheduler/2011-07-12-13-00-19
    > 454M ./pypo/cache/scheduler/2011-07-12-02-02-06
    > 454M ./pypo/cache/scheduler/2011-07-12-03-59-37
    > 454M ./pypo/cache/scheduler/2011-07-12-03-02-09
    > 454M ./pypo/cache/scheduler/2011-07-12-00-58-34
    > 454M ./pypo/cache/scheduler/2011-07-12-00-01-44
    > 3.8G ./pypo/cache/scheduler
    > 3.8G ./pypo/cache
    > 4.0K ./pypo/files
    > 4.0K ./pypo/tmp
    > 3.8G ./pypo
    > 4.0K ./show-recorder
    > 3.8G .
    >
    >
    >
    > I did a DB cleanup on Sunday and we've only been on the air for two days so
    > I can't tell if there's some flushing going on yet. I'll keep and eye on it
    > and let you know.
    >
    > < http://forum.sourcefabric.org/index.php?t=getfile&id=175> Attachment:
    > pypo.current.log.bz2< http://forum.sourcefabric.org/index.php?t=getfile&id=175>
    > (Size: 6.71KB)
    >

  • Vote Up0Vote Down Ed PorrasEd Porras
    Posts: 37Member
    Our programs are all pre-recorded as 30-60 minute-long blocks thus, our "shows" are rather collections of these meaning each "show" is anywhere from 1-hour to 9-hours depending on when the frequency is available to us (yellow and blue blocks on http://www.wgot.org/calendar/).

    I'm going to create a 40GB /var partition and set it up this afternoon after we're back off-air.

    Thanks for the help.
Add a Comment