Results 1 to 5 of 5

Thread: killUnidentifiedSessions after moving wms-stats.jar

  1. #1
    Join Date
    Jul 2015
    Posts
    3

    Exclamation killUnidentifiedSessions after moving wms-stats.jar

    Hoping someone can help with this. We were trying to move wms-stats.jar out of /lib and start wowza and now logs say connections are being killed and cpu usage is off the roof:

    2015-07-31 02:56:45 MDT comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/xxxxx:53871 - - - 872.706 - - - - - -- - - - - - - - - - - - - - - - - - -
    2015-07-31 02:56:45 MDT comment server INFO 200 - killUnidentifiedSessions: Killing unidentified session: address:/xxxxx:63056 - - - 872.707 - - - - - -

    We moved it back in place, but cpu is still high and connections are being refused.

    Any help is much appreciated.

  2. #2
    Join Date
    Jul 2015
    Posts
    3

    Default

    We managed to fix this. In case it helps anyone else, we had to set <UnidentifiedSessionTimeout> to 30000 and <ValidationFrequency> to 20000 from 0 to make this work. Though, still puzzled how this would be reset.

  3. #3
    Join Date
    Jan 2015
    Posts
    357

    Default

    Hi nithintou,

    Do you also see any "timecode jumped" errors in relation to stats database in your logs? Removing wms-stats.jar file may have interrupted the monitoring collection module, and prompted the service into a loop (hence the high CPU usage). You may have to archive and delete the files from /stats folder, restart Wowza services, and check you logs for errors again.

    Michelle

  4. #4
    Join Date
    Jul 2015
    Posts
    3

    Default

    Quote Originally Posted by michelle_b View Post
    Hi nithintou,

    Do you also see any "timecode jumped" errors in relation to stats database in your logs? Removing wms-stats.jar file may have interrupted the monitoring collection module, and prompted the service into a loop (hence the high CPU usage). You may have to archive and delete the files from /stats folder, restart Wowza services, and check you logs for errors again.

    Michelle
    You're probably right. We were seeing errors saying .wdb files were unwritable in logs when the cpu usage was high, but back then we checked on file permissions and couldn't fix it. We eventually did a reinstall of wowza, and compared the settings files from the old and new install, however i am guessing it could be that the stats files were recreated and that fixed our issue.

  5. #5
    Join Date
    Jan 2015
    Posts
    357

    Default

    Hi nithintou,

    Thank you for updating us. I'm glad it was fixed for you.

    Michelle

Similar Threads

  1. Seeing many "killUnidentifiedSessions" -- are viewers really being booted and why?
    By boyd.badten in forum Server Administration Discussion
    Replies: 5
    Last Post: 10-28-2014, 12:26 PM
  2. killUnidentifiedSessions
    By stefancaunter in forum Server-side Modules and Code Samples Discussion
    Replies: 1
    Last Post: 12-31-2013, 11:53 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
  •