after a minute from initializing client the client is removed
2022-04-12 15:12:44 EEST comment server INFO 200 - loadBalancer: Initializing new client: DST1 - - - 392.756 - - - - - - - - - - – - - - - - - - - - - - - -
2022-04-12 15:12:49 EEST comment server INFO 200 - loadBalancer: Initialization complete client: DST1 - - - 397.8 - - - - - - - - - – - - - - - - - - - - - - - -
2022-04-12 15:13:01 EEST comment server INFO 200 - loadBalancer: Remove client: Expire Timeout: DST1 - - - 409.603 - - - - - - - - - – - - - - - - - - - - - - - -
I set up a bunch of new WSE VMs and it looks the same on my side. any news on that?
Hello Kay,
check the version of load balancer module on your LB ‘Server’ and Edge ‘Client’ Wowzas.
The string in wowzastreamingengine_access.log looks like the below:
loadBalancer: onServerInit() Version: 4.5.0 Build 17275 Start
Build 17240 on the Server is not compatible with the build 17275 on the Edge for example. This will cause the same error you have observed.
I’ve installed on both (client and Server the “loadBalancer: onServerInit() Version: 4.5.0 Build 17275”) with wowza 4.8.18+1
I also upgraded to wowza 4.8.20+1 (latest) and still have the same error.
Right now I assume that the issue is still unfixed. I connected the Clients (with the newer wowza and plugin version) to an old origin 4.8.10 and plugin “Server version: 17275” - just for testing purpose - and it works as expected.
Does somebody know to which version I need to downgrade (and how to downgrade)?
If the same 17275 build of LB plugin is installed on all servers this should be fine. You should not downgrade the Wowza build. LB plugin works with Wowza 4.8.19 at least just fine… I would suggest to enable LB plugin debug then.
thats what I tested yesterday: all wowzas (server and client instances) 4.8.20 with the LB plugin build 17275. this dropped the timeout error and the server does not get the stream names and informations from the clients
A new version 17280 of the plugin was released during my support ticket was waiting for response. This version is working now and fixed the issue. (till now 
I’ll do some deeper testing the next days)
Some additional info that may be of interest for anyone using load balancer communication over SSL with Wowza version 4.8.18 and higher ( with included Java 11.0.2+9 ) and faced with “loadBalancer: Remove client: Expire Timeout” issue.
The issue exists even with the latest 4.8 load balancer build 17286. The edge may disconnect after 6-10 hours of running. Java update to 11.0.19 resolves the problem.