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.
We managed to fix this. In case it helps anyone else, we had to set to 30000 and to 20000 from 0 to make this work. Though, still puzzled how this would be reset.
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
Hi nithintou,
Thank you for updating us. I’m glad it was fixed for you.
Michelle
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.