Multiple "Session not accepted" messages with same session ids causing frequent restarts

[charles_ravindran]

Wowza logs are continuouslly throwing session not accepted messages with same session ids and this causes increase in cpu and memory usage and results in restart of wowza.

HTTPStreamerAdapterCupertinoStreamer.onPlaylist[live/_definst_/mystream/secure/live/chunklist_w1723004156_b512000.m3u8?e=1493811001&h=244d6640c52f71dd68cbdc7b596cee92&bgsecuredir=1&nc=1]: Session not accepted[1666004156]

HTTPStreamerAdapterCupertinoStreamer.onPlaylist[live/_definst_/mystream/secure/live/chunklist_w1723004156_b512000.m3u8?e=1493811001&h=244d6640c52f71dd68cbdc7b596cee92&bgsecuredir=1&nc=1]: Session not accepted[1666004156]

HTTPStreamerAdapterCupertinoStreamer.onPlaylist[live/_definst_/mystream/secure/live/chunklist_w1723004156_b512000.m3u8?e=1493811001&h=244d6640c52f71dd68cbdc7b596cee92&bgsecuredir=1&nc=1]: Session not accepted[1666004156]

This affects the customers in peak time. Frequent restarts causing problem with customer .I couldn’t find any solution for this problem. I assume that the rejected session is not properly closed.

What has to be done to solve this issue?. Need a quick solution

[Alex_C]

Hello @charles ravindran,

If you are securing your stream with Secure Tokens, the messages you are seeing in your logs could be there because someone is trying to view your stream and hash is failing.

You can enable the debug property securityDebugLogDetails to see these details logged.

After this you can see if the requests are coming from a single IP and then block it, or add additional security by using the RefererValidate module.

Regards,

Alex C.

[charles_ravindran]

Thanks @Alex C. But blocking an ip is not really an solution for my issue.

I believe this is an internal bug in wowza because after rejecting the session(calling rejectSession api), the session again tries to reconnect multiple times. So this implies there is an issue with wowza right ?

Is there any other way solve this issue?

[Christian_Punknown]

Same issue here. “Session not accepted”, if i click/stream again, second call will work…