Recent content by SLM

Thanks!

thanks Max

In newly updated Flashphoner version v.2.0.252-5.2.2105-6617ffbcbbe717ba9a1328953a2287a92c1120cb the origin field is missing when retrieving all connections: https://(domain):8444/rest-api/connection/find_all It is still present In the streams list https://(domain):8444/rest-api/stream/find_all...

Thanks

08:09:26,538 ERROR MediaHandler - API-ASYNC-pool-7-thread-47 publishStream exception com.flashphoner.server.license.manager.exception.LicensePeriodIsExpired at com.flashphoner.server.license.manager.A.A.E.check(Unknown Source) at...

It's happened again now. No streams can be published.

It's working again now after fix and restart

We're getting this error on both our servers. The license method is pay as you go so how come we get this error? Please fix this ASAP because all Flashphoner servers on AWS are not working 15:15:00,781 ERROR MediaHandler - API-ASYNC-pool-7-thread-1 publishStream exception...

No more issues concerning unresponsiveness after update to version 1924, so that's great. Thanks. I'm still seeing the socketexceptions in the logs though and sometimes quite a lot: 21:00:00,029 WARN StunUdpSocket - STUN-UDP-pool-40-thread-1749 [id: 0x5935f9c6, /172.xx.xx.xxx:31618]...

Thanks. Current values after these rmem settings are now: net.core.rmem_default = 26214400 net.core.rmem_max = 26214400 net.ipv4.tcp_rmem = 4096 87380 6291456 net.ipv4.udp_rmem_min = 4096 I will monitor the situation the next 48 hours

Can I do this UDP socket buffer tuning while WCS is running and handling streams? Or do I need to stop the service first? Will it retain these values at server reboot ? Are there any downsides of this setting: ice_tcp_transport=true

Thank you Max. I've updated the server yesterday and it's running for 24 hours now. However, I'm seeing a few strange values in the WCS stats: core_java_totalPhysicalMemorySize = 16318554112 core_java_committedMemory = 426256351232 core_heap_memory_used = 526385152...

I've sent a second report. This time from the other server (with ZGC setting) on version v.2.0.240-5.2.1920 which saw the same issue after just 5 hours. CPU spiked to 100% and then Flashphoner refused all streaming connections even when CPU went back to 0.

I've sent the report. The ZGC was not yet configured on this server. Traffic is now on another server with that configuration.

Yes, I figured that out after I posted the edit. Complete result is too big to post in here. I see mostly RUNNABLE and TIMED_WAITING