Results 1 to 4 of 4

Thread: Recording has stopped having moved to 3.0.3 from 2.2.4

  1. #1
    Join Date
    Nov 2011
    Posts
    2

    Default Recording has stopped having moved to 3.0.3 from 2.2.4

    Hi there,
    I have been developing an application that records all the video data sent to it and saves the file in a particular place (/var/video/new) and with a filename which had been passed through on the address line. My small app worked fine on 2.2.4 but having upgraded to 3.0.3 for another project the recording has stopped.

    I can see that the server is receiving data from my flash application and the correct config file is being loaded.

    DEBUG server comment - Loading Application.xml: file:///usr/local/WowzaMediaServer/conf/videorecording/Application.xml
    DEBUG server comment - load module: name:base class:com.wowza.wms.module.ModuleCore
    DEBUG server comment - SharedObjectWriteAccess: *
    DEBUG server comment - StreamReadAccess: *
    DEBUG server comment - StreamWriteAccess: *
    DEBUG server comment - StreamAudioSampleAccess:
    DEBUG server comment - StreamVideoSampleAccess:
    DEBUG server comment - explodeStorageDir: /var/video/new/=/var/video/new/
    DEBUG server comment - validateStoragePath: start: /var/video/new
    DEBUG server comment - explodeStorageDir: ${com.wowza.wms.context.VHostConfigHome}/keys=/usr/local/WowzaMediaServer/keys
    DEBUG server comment - validateStoragePath: start: /usr/local/WowzaMediaServer/keys
    DEBUG server comment - explodeStorageDir: =
    DEBUG server comment - validateStoragePath: start:
    DEBUG server comment - parent: null
    INFO application app-start _definst_ videorecording/_definst_
    DEBUG server comment - cmd: publish
    INFO stream publish 8117-2011-11-30_15.22.08 -
    INFO stream record 8117-2011-11-30_15.22.08 -
    DEBUG server comment - cmd: setBufferTime
    DEBUG session setbuffertime [1910510668,1]: 20000 20000
    DEBUG server comment - cmd: deleteStream
    INFO stream recordstop 8117-2011-11-30_15.22.08 -
    INFO stream unpublish 8117-2011-11-30_15.22.08 -
    INFO stream destroy 8117-2011-11-30_15.22.08 -
    INFO server comment - ServerHandler.exceptionCaught[[any]:1935:*.*.*.*]: java.io.IOException: Connection reset by peer
    DEBUG server comment - sessionClosed: closeConnection: vhost:_defaultVHost_ clientId:1910510668
    INFO session disconnect 1910510668 -
    DEBUG server comment - ServerHandler.handleSessionIdle: isDidClose
    the *.*.*.* is the correct ip. The last quote above is what happens when the page sending video data is closed. The file isn't created anywhere on the server.

    in my Application.xml for my app I have the lines

    <StreamType>record</StreamType>
    <StorageDir>/var/video/new/</StorageDir>
    Thanks, Max

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Max,

    Did you copy Wowza 2 configuration files over Wowza 3 install? If so, try to undo or start over.

    DEBUG level logging is only helpful in certain situations, and is usually way too much info, just makes it very hard to see what is important, and increase overhead. Use INFO level logging, generally, including for most trouble-shooting

    Richard

  3. #3
    Join Date
    Nov 2011
    Posts
    2

    Default

    Hi richard,
    thanks for your answer. I found my problem, my video camera wasn't transmitting any packets. I just installed the configuration for the app rather than overwriting any files.

    Max

  4. #4
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Max,
    Thanks for the update,

    Richard

Similar Threads

  1. Close references to file so it can be moved
    By jweather in forum On-Demand Streaming
    Replies: 13
    Last Post: 11-07-2014, 04:35 AM
  2. iOS doesn't recognize DVR has stopped recording
    By ScottKell in forum AddOn: Wowza nDVR
    Replies: 6
    Last Post: 11-18-2011, 06:53 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •