Skip to main content
Known Participant
October 19, 2011
Question

Disk filling

  • October 19, 2011
  • 2 replies
  • 2144 views

Hi all,

i'm testing hds and hls as well and i see my streams/livestream directory full of f4x and f4f files. I set into Event.xml the following value:

<DiskManagementDuration>1</DiskManagementDuration> that should delete all files over than 1 hour. Is there a value to set into this tag minus that 1 hour (es. 30 minutes)?.

Thanks

    This topic has been closed for replies.

    2 replies

    October 21, 2011

    I've set DiskManagementDuration to 1, but even after multiple hours the first f4f segment still exists. Why are chunks older than 1 hour not deleted? My Event.xml:

    <Event>

      <EventID>...ID...</EventID>

      <Recording>

        <FragmentDuration>4000</FragmentDuration>

        <SegmentDuration>100000</SegmentDuration>

        <DiskManagementDuration>1</DiskManagementDuration>

      </Recording>

    </Event>

    I am using the FMS 4.5 Streaming edition with a valid license (not the dev edition).

    Thanks!

    ZeromegaAuthor
    Known Participant
    October 21, 2011

    HI joafeldmann,

    maybe you should check the permissions no _definst_/livestream directory. FMS user process should write on that directory.

    bye

    October 21, 2011

    I've just checked the permissions of the _definst_/livestream folder: All f4* files are created as user:group fms:fms, so the fms should be able to delete files.

    Maybe the configuration in my httpd.conf file is wrong or not working wirh settings made in Events.xml?

    Event.xml

    ...

    <Event>

      <EventID>...ID...</EventID>

      <Recording>

        <FragmentDuration>4000</FragmentDuration>

        <SegmentDuration>8000</SegmentDuration>

        <DiskManagementDuration>0.25</DiskManagementDuration>

      </Recording>

    </Event>

    Manifest.xml

    <manifest xmlns="http://ns.adobe.com/f4m/1.0">

        <media streamId="...ID...1" bitrate="256" />

    </manifest>

    httpd.conf

    <Location /hds-live>

        HttpStreamingEnabled true

        HttpStreamingLiveEventPath "../applications"

        HttpStreamingContentPath "../applications"

        HttpStreamingF4MMaxAge 2

        HttpStreamingBootstrapMaxAge 2

        HttpStreamingFragMaxAge -1

        Options -Indexes FollowSymLinks

    </Location>

    </IfModule>

    LoadModule hlshttp_module modules/mod_hlshttp.so

    <IfModule hlshttp_module>

    <Location /hls-live>

        HLSHttpStreamingEnabled true

        HttpStreamingLiveEventPath "../applications"

        HttpStreamingContentPath "../applications"

        HLSMediaFileDuration 8000

        HLSSlidingWindowLength 6

        HLSFmsDirPath ".."

        HLSM3U8MaxAge 2

        HLSTSSegmentMaxAge -1

    # Uncomment the following directives to enable encryption

    # for this location.

    #    HLSEncryptionScope server

    #    HLSEncryptCipherKeyFile "../phls/liveeventkey.bin"

    #    HLSEncryptKeyURI        "https://<ServerName>/hls-key/liveeventkey.bin"

        Options -Indexes FollowSymLinks

    </Location>

    ...

    Adobe Employee
    October 19, 2011

    If you want to set it to say 30 minutes - you would have to set it like <DiskManagementDuration>0.5</DiskManagementDuration>

    ZeromegaAuthor
    Known Participant
    October 20, 2011

    Hi SE_0208,

    i'm using a time-based configuration into my Event.xml so i'm setting 4000 for FragmentDuration and 16000 for SegmentDuration. Setting a value for DiskManagementDuration the f4x anf f4f files are stored on disk for 1 hour but is there a way to auto delete the files when the live event is at the end? I mean the files still remain stored on disk and i need to delete them manually to avoid to see old streams.

    Just another advice... for live events is a better way to use a frame-based or a time-based configuration into Exent.xml?

    Thanks

    Adobe Employee
    October 21, 2011

    Use Framebased settings rather than time based settings.

    Secondly - the  files which would remain at end of publish - you can delete it using some server-side logic i.e. using Server-side action script. Once you get onUnpublish - you can set timer so that you can invoke function (when you feel safe to delete the files) - which would delete all remaining files.