Skip to main content
July 8, 2008
Question

Problem using fmscheck

  • July 8, 2008
  • 2 replies
  • 778 views
Hello,
I´m trying to use fmscheck to do a performance stress-test for FMS3. The idea is to generate many VOD connections and check the performance of the server. The problem is that when I execute the fmscheck with the --play switch on a .flv file, the connection is established and disconnected in less than a second, no matter how long the .flv file is. So if I launch 100 sessions of a video, I can see on the monitor tool 100 connects and 100 disconnects within a second.
There are no errors on the log, I´ve check the .flv file with flvcheck and it passes. Here is the full command line:

./fmscheck --host 192.168.5.2 --app vod --play media/sample2.flv 0 all --timeout 3600

I will put this into a loop so I can emulate several connections.
    This topic has been closed for replies.

    2 replies

    Participant
    July 23, 2008
    I'm able to fmscheck other files than the defaults but also getting that issue where it's not feasible that the whole stream is being checked (returning too quickly).

    Has anyone worked out how to log to stdout rather than a log file?
    July 23, 2008
    Hello lucyvoloi.

    Make shure your media files are in the correct directory (check for "VOD_DIR =" on your /conf/fms.ini file)
    The fact that the prompt returns too quickly might not be a problem. Try checking on the fms_adminConsole.htm how many connected clients you have.
    You can also specify a --logfile at the end of the fmscheck to verify that the media stream was played. It should report something like "NetStream.Play.Start Started playing whateverfile"
    Remember do not include the .flv extension when using the fmscheck!

    Here is a small script that puts as many concurrent connections as you want:
    #!/bin/bash
    COUNTER=0
    echo *----------------------------------------------------------------*
    echo Usage: stress.sh Server_Name Media_Name Connection_Number
    echo Log:File: stress_log.txt
    echo *----------------------------------------------------------------*
    while [ $COUNTER -lt $3 ]; do
    echo Connection: $COUNTER of $3
    /opt/adobe/fms/tools/fmscheck --host $1 --app vod --play $2 0 all --timeout 36000 --logfile stress_log.txt &
    let COUNTER=COUNTER+1
    done

    Just run it like this: #./stress.sh 192.168.1.26 this_is_a_media_file2 180
    then look at the log file #cat stress_log.txt

    Hope this helps.

    Cheers!
    Sebas.
    July 8, 2008
    [UPDATE]
    It seems that part of the problem was that fmscheck can't manage file extension, so the command should be like:
    /fmscheck --host 192.168.5.2 --app vod --play media/sample 0 all --timeout 3600

    Now another problem I have is that if I use a different file (not the sample files) it can´t find the file:
    NetStream.Play.StreamNotFound "Failed to play"

    The file is in the same directory and I've check the file using flvcheck.