Results 1 to 6 of 6

Thread: Can't even play Flash HTTP stream

  1. #1
    Join Date
    Nov 2012
    Posts
    3

    Default Can't even play Flash HTTP stream

    Hi all,
    I have recently downloaded Wowza and could manage to set it up on a Mac quite happily, but I have installed it in my Suse and can't make it work. I have Apache2 with virtual hosts and root directories are pointing to different directories then Wowza original installation. Nevertheless, I followed the installation tutorials but I always come up with "Error #2048" when I hit "connect" button. Could you please help me with this?
    Best regards,
    Cesar Ona

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

    Default

    Cesar,

    What "connect" button are you referring to? Is it a Flash RTMP client?

    Run Wowza in stand-alone (/bin/startup.bat) mode so you can see log output in the console. What do you see on the Wowza side when you connect in the client?

    Richard

  3. #3
    Join Date
    Nov 2012
    Posts
    3

    Default

    Thanks Richard,
    I followed the "How to play your first video on demand stream (video tutorial) " tutorial. When I go to /usr/local/WowzaMediaServer/examples/VideoOnDemandStreaming/FlashHTTPPlayer/player.html is where I find the connect button and where I get the error.
    No errors on wowzamediaserver_error.log
    When I launch the server (./startup.sh) I get the following log:
    INFO server server-start Wowza Media Server 3 Trial Edition (Expires: dic 24, 2012) 3.5.0 build2989 -
    INFO server comment - Server License Key: SVRT3-XXXXX-XXXXX-XXXXX-XXXXX-PyjGA
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Transcoder Streams Available: Unlimited
    INFO server comment - Transcoder Watermark: Yes
    INFO server comment - nDVR Available: Yes
    INFO server comment - DRM Available: Yes
    INFO server comment - Hardware Available Processors: 2
    INFO server comment - Hardware Physical Memory: 400MB/3961MB
    INFO server comment - Hardware Swap Space: 2003MB/2053MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 46
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 3.1.0-1.2-desktop
    INFO server comment - OS Architecture: amd64
    INFO server comment - Java Name: OpenJDK 64-Bit Server VM
    INFO server comment - Java Vendor: Sun Microsystems Inc.
    INFO server comment - Java Version: 1.6.0_22
    INFO server comment - Java VM Version: 20.0-b11
    INFO server comment - Java Spec Version: 1.6
    INFO server comment - Java Home: /usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre
    INFO server comment - Java Max Heap Size: 1066MB
    INFO server comment - Java Architecture: 64
    INFO server comment - Java Locale[user.language]: es
    INFO server comment - Java Locale[user.country]: ES
    INFO server comment - Java Locale[file.encoding]: UTF-8
    INFO server comment - Java Timezone[user.timezone]: Europe/Madrid
    INFO server comment - Java Args[0]: -Xmx1200M
    INFO server comment - Java Args[1]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[2]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[3]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[4]: -Dcom.wowza.wms.native.base=linux
    INFO server comment - Java Args[5]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaMediaServer
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: linux
    INFO server comment - Server threads[h/t]: 10/10
    INFO server comment - JMX java.rmi.server.hostname: 10.31.48.71
    INFO server comment - JMX bind attempt service:jmx:rmi://10.31.48.71:8084/jndi/rmi://10.31.48.71:8085/jmxrmi
    INFO server comment - JMX password file: /usr/local/WowzaMediaServer/conf/jmxremote.password
    INFO server comment - JMX access file: /usr/local/WowzaMediaServer/conf/jmxremote.access
    INFO server comment - JMX bind successful
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:120/80 home:/usr/local/WowzaMediaServer
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:1)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - Wowza Media Server is started!

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

    Default

    The start-up log you show looks okay. What do you see when you click the "connect" button? There is nothing in that log snip that indicates a client tried to connect.

    Richard

  5. #5
    Join Date
    Nov 2012
    Posts
    3

    Default

    Ok, it was my fault. when I had to write the stream to connecto to in "/usr/local/WowzaMediaServer/examples/VideoOnDemandStreaming/FlashHTTPPlayer/player.html", I wrote http//localhost:1935/vod...instead of http://<woza-server-ip-address>/vod... Anyway, it is now working. We can close this thread. Thanks for the support.

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

    Default

    Great. Thanks for the update

    Richard

Similar Threads

  1. play method is not invoked in case of Flash HTTP
    By mahesh in forum Tutorials Discussion
    Replies: 7
    Last Post: 06-19-2013, 05:16 AM

Posting Permissions

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