Results 1 to 3 of 3

Thread: 3.5.0 - 3.6.2 upgrade issue

  1. #1

    Default 3.5.0 - 3.6.2 upgrade issue

    I know I must have goofed somewhere in the config transfer, but I can't find it. This is a production server but only single bitrate live streams are working right now. Need to find a fix soon...


    We have a problem with a transcoder mountpoint - when I ran it under 3.5.0 everything was fine. When I tried it on 3.6.2, I got this problem at startup


    WARN server comment 2013-08-29 14:42:03 - - - - - 4.451 - - - - - - - - HTTPProviderMediaList.onHTTPRequest: MediaList not found: WPTlive/_definst_/ngrp:myStream_all
    WARN server comment 2013-08-29 14:42:03 - - - - - 4.512 - - - - - - - - HTTPProviderMediaList.onHTTPRequest: MediaList not found: WPTliveCC/_definst_/ngrp:myStream_all
    WARN server comment 2013-08-29 14:42:05 - - - - - 6.2 - - - - - - - - TranscoderSessionNative.loadLibrary: Error loading native libraries: transcoder.lib missing: C:/Program Files (x86)/Wowza Media Systems/Wowza Media Server 3.6.2/lib-native/win64
    WARN server comment 2013-08-29 14:42:08 - - - - - 9.667 - - - - - - - -


    then it gets even wilder after restarting the server:


    #Fields: x-severity x-category x-event date time c-client-id c-ip c-port cs-bytes sc-bytes x-duration x-sname x-stream-id x-spos sc-stream-bytes cs-stream-bytes x-file-size x-file-length x-ctx x-comment
    ERROR server comment 2013-08-29 14:48:53 - - - - - 1.656 - - - - - - - - JMXConfig: createRegistry: error: java.rmi.server.ExportException: Port already in use: 8085; nested exception is:
    java.net.BindException: Address already in use: JVM_Bind
    ERROR server comment 2013-08-29 14:48:53 - - - - - 1.661 - - - - - - - - JMXConfig: error: java.rmi.server.ExportException: Port already in use: 8084; nested exception is:
    java.net.BindException: Address already in use: JVM_Bind
    ERROR server comment 2013-08-29 14:48:53 - - - - - 1.708 - - - - - - - - server core failure: java.net.BindException: Address already in use: bind


    \So far so good. I decided to go back to 3.5.0 and see if I messed up any settings. However, after stopping the 3.6.2 service and starting the 3.5.0 service I now have the same problem, and from checking the stream list, it appears as if 3.6.2 is running, not 3.5.0, even though in the services tab, it clearly shows the 3.5.0 service as started an the 3.6.2 service as stopped. I


    going to my admin interface, I get "Wowza Media Server 3 Perpetual Edition 3.6.2.10 build6427"

    which isn't supposed to be running right now, but no streamlist is available or anything else. Basically, the server is running in what appears 3.6.2 while it should be 3.5.0, and I can't figure out why the transcoder is broken. License numbers are transferred, all the passwords are the same, the vhost file is fine, nothing much else is custom on the system.

    JConsole tells me I am running 3.62, I have two trancoder licenses, and none are in use.

    Something is messed up, but I can't tell what. Did the application.xml format for transcoded live streams change?

  2. #2

    Default

    things aren't getting better - I tried to send a stream to the mountpoint that's not working - a second later this crash


    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
    java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
    .java:603)
    at java.lang.Thread.run(Thread.java:722)
    INFO session comment 999494239 client connectionClosed [999494239] pingtimeout
    Exception in thread "IdleWorkerUtil-2" Exception in thread "serverWatchdog" Exce
    ption in thread "VHostHandler._defaultVHost_.65" WARN server comment - Unexpecte
    d exception.
    java.lang.OutOfMemoryError: Java heap space
    java.lang.OutOfMemoryError: Java heap space
    java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-903" java.lang.OutOfMemoryError: Java heap space
    INFO session comment 661140913 client connectionClosed [661140913] pingtimeout
    Exception in thread "Thread-901" WARN server comment - Unexpected exception.
    INFO session disconnect 15112066 -
    java.lang.OutOfMemoryError: Java heap space
    INFO session disconnect 661140913 -
    WARN server comment - Unexpected exception.
    java.lang.OutOfMemoryError: Java heap space
    WARN server comment - Unexpected exception.
    WARN server comment - Unexpected exception.
    java.lang.OutOfMemoryError: Java heap space
    WARN server comment - Unexpected exception.

    Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler i
    n thread "vhostWatchdog"
    Exception in thread "vhostWatchdog" Exception in thread "Thread-904" java.lang.O
    utOfMemoryError: Java heap space
    Exception in thread "Thread-62" Exception in thread "IdleWorkerUtil-3"
    Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler i
    n thread "Thread-62"
    java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-905" java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-906" java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-871" java.lang.OutOfMemoryError: Java heap space
    Exception in thread "Thread-4" java.lang.OutOfMemoryError: Java heap space

  3. #3

    Default

    never mind...

    Apparently the process of patching to 3.6.2.10 nuked all the files in the win64 lib-native folder, but didn't put the new files in. Amazing that the system even starts up with no files whatsoever in that folder!

Similar Threads

  1. UPGRADE 3.6 to 4.3
    By kenji24 in forum Tutorials
    Replies: 6
    Last Post: 10-08-2015, 08:04 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
  •