Please help about intergation with wowza

Community Forums
1

I intergate kaltura with wowza follow github installation document.
In in fact I don’t know how to determine whether it is successful or not .I’m new about this.just a few days
this is my log:

[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Server License Key: ET2A4-XXXXX-XXXXX-XXXXX-XXXXX-77R43 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Maximum Connections: 10 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Maximum Incoming Streams: 3 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Transcoder Streams Available: 1 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Transcoder Watermark: Yes - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - nDVR Available: Yes - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - DRM Available: Yes - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - HTTP Origin Available: No - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Push Publish Available: Yes - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - REST API Available: Yes - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Hardware Available Processors: 4 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Hardware Physical Memory [free/total]: 954MB/4048MB - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Hardware Swap Space [free/total]: 1991MB/8095MB - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Max File Descriptor Count: Unlimited - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - OS Name: Windows 7 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - OS Version: 6.1 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - OS Architecture: amd64 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - OS CPU: amd64 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Name: Java HotSpot™ 64-Bit Server VM - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Vendor: Oracle Corporation - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Version: 1.8.0_77 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java VM Version: 25.77-b03 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Spec Version: 1.8 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Home: D:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.5.0\jre1.8.0_77 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Max Heap Size: 1620MB - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Architecture: 64 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Locale[user.language]: zh - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Locale[user.country]: CN - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Locale[user.variant]: - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Locale[file.encoding]: GBK - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Timezone[user.timezone]: Asia/Shanghai - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[0]: -Xmx1619M - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[1]: -XX:+UseG1GC - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[2]: -XX:MaxGCPauseMillis=100 - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[3]: -Djava.net.preferIPv4Stack=true - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[4]: -Dcom.sun.management.jmxremote=true - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[5]: -Dcom.wowza.wms.runmode=service - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[6]: -Dcom.wowza.wms.native.base=win - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Java Args[7]: -Dcom.wowza.wms.ConfigURL= - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Server runmode: service - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Server native.platform: win - (WMSLogger.java:203)
[2016-09-22 15:04:08][main][com.wowza.wms.logging.WMSLogger:log] INFO - Server threads[h/t]: 180/120 - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - RESTServer: Bind attempt ([any]:8087) - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - RESTServer: Bind successful ([any]:8087) - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - Wowza REST API started - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - RESTServer: Using configs from:D:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.5.0/ - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - RESTServer: SSL:No - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - RESTServer: BasicAuth:No - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - RESTServer: Digest:Yes - (WMSLogger.java:203)
[2016-09-22 15:04:12][main][com.wowza.wms.logging.WMSLogger:log] INFO - RESTServer: XML Viewer:No - (WMSLogger.java:203)
[2016-09-22 15:04:13][Thread-6][com.wowza.wms.logging.WMSLogger:log] INFO - REST API: ready - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - REST Documentation Server has been disabled. - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - CMDInterface now listening: [any]:8083 - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: Thread pool size: [writer/readahead]:6/3 - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: MAX Pending size: [writer/readahead]:160M/80M - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: Add store: path:D:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.5.0/mediacache maxSize:10737418240 - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: Add source[dvrorigin]: prefix:dvrorigin/ basePath:http:// - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: Flushing cache: start - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: Flushing cache: done - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: Start MediaCache GC - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - MediaCache[MediaCache]: Started - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - defaultVHost threads[h/t]:0/0 home:D:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.5.0 - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - Bind attempt ([any]:1935:6) - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - Bind successful ([any]:1935) - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - Bind attempt ([any]:8086:3) - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - Bind successful ([any]:8086) - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.wowza.wms.logging.WMSLogger:log] INFO - Server.startShutdownHook: Start server shutdown hook - (WMSLogger.java:203)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:] DEBUG - Initializing Kaltura server [3.0.8.1] - (KalturaServer.java:61)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:] DEBUG - Kaltura server host name: MASHAOYI - (KalturaServer.java:66)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:initClient] DEBUG - Initializing Kaltura client, URL: http://191.168.104.161 - (KalturaServer.java:129)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:generateClientSession] DEBUG - Kaltura client session id: NTE1OTQ4YmUzMGNjYzc5MTVhNTVhOTQ4NzBkNjUyM2QyY2MwNTFhNXwtNTstNTsxNDc0NjE0MjUzOzI7MjAxMDtNZWRpYVNlcnZlcjtkaXNhYmxlZW50aXRsZW1lbnQ= - (KalturaServer.java:168)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:] DEBUG - Initializing server managers: com.kaltura.media.server.wowza.StatusManager, com.kaltura.media.server.wowza.LiveStreamManager, com.kaltura.media.server.wowza.CuePointsManager, com.kaltura.media.server.wowza.PushPublishManager - (KalturaServer.java:79)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:initManagers] DEBUG - KalturaServer::initManagers Initializing Kaltura manager com.kaltura.media.server.wowza.StatusManager - (KalturaServer.java:201)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:initManagers] INFO - KalturaServer::initManagers Initialized Kaltura manager com.kaltura.media.server.wowza.StatusManager - (KalturaServer.java:214)
[2016-09-22 15:04:13][Timer-1][com.kaltura.media.server.managers.KalturaStatusManager:reportStatus] DEBUG - KalturaStatusManager::reportStatus Reporting server status [MASHAOYI] - (KalturaStatusManager.java:57)
[2016-09-22 15:04:13][Timer-1][com.kaltura.client.KalturaClientBase:doQueue] DEBUG - service url: [http://191.168.104.161] - (KalturaClientBase.java:253)
[2016-09-22 15:04:13][main][com.kaltura.media.server.KalturaServer:initManagers] DEBUG - KalturaServer::initManagers Initializing Kaltura manager com.kaltura.media.server.wowza.LiveStreamManager - (KalturaServer.java:201)
[2016-09-22 15:04:13][Timer-1][com.kaltura.client.KalturaClientBase:doQueue] DEBUG - full reqeust url: [http://191.168.104.161/api_v3/index.php?service=mediaserver&action=reportStatus?ignoreNull=1&hostname=MASHAOYI&mediaServerStatus:objectType=KalturaMediaServerStatus&apiVersion=3.1.6&format=2&ks=NTE1OTQ4YmUzMGNjYzc5MTVhNTVhOTQ4NzBkNjUyM2QyY2MwNTFhNXwtNTstNTsxNDc0NjE0MjUzOzI7MjAxMDtNZWRpYVNlcnZlcjtkaXNhYmxlZW50aXRsZW1lbnQ%3D&partnerId=-5&kalsig=a59b16b983e1e57bc72bf13ad7a55961&clientTag=MediaServer-MASHAOYI] - (KalturaClientBase.java:261)
[2016-09-22 15:04:13][main][com.kaltura.client.KalturaClientBase:doQueue] DEBUG - service url: [http://191.168.104.161] - (KalturaClientBase.java:253)
[2016-09-22 15:04:13][main][com.kaltura.client.KalturaClientBase:doQueue] DEBUG - full reqeust url: [http://191.168.104.161/api_v3/index.php?service=flavorparams&action=list?ignoreNull=1&apiVersion=3.1.6&format=2&ks=NTE1OTQ4YmUzMGNjYzc5MTVhNTVhOTQ4NzBkNjUyM2QyY2MwNTFhNXwtNTstNTsxNDc0NjE0MjUzOzI7MjAxMDtNZWRpYVNlcnZlcjtkaXNhYmxlZW50aXRsZW1lbnQ%3D&partnerId=-5&kalsig=b9203e9c94ceb54403413541164adfe0&clientTag=MediaServer-MASHAOYI] - (KalturaClientBase.java:261)
[2016-09-22 15:04:34][Timer-1][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect - (HttpMethodDirector.java:439)
[2016-09-22 15:04:34][main][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect - (HttpMethodDirector.java:439)
[2016-09-22 15:04:34][Timer-1][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - Retrying request - (HttpMethodDirector.java:445)
[2016-09-22 15:04:34][main][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - Retrying request - (HttpMethodDirector.java:445)
[2016-09-22 15:04:55][Timer-1][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect - (HttpMethodDirector.java:439)
[2016-09-22 15:04:55][main][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect - (HttpMethodDirector.java:439)
[2016-09-22 15:04:55][main][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - Retrying request - (HttpMethodDirector.java:445)
[2016-09-22 15:04:55][Timer-1][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - Retrying request - (HttpMethodDirector.java:445)
[2016-09-22 15:05:16][Timer-1][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect - (HttpMethodDirector.java:439)
[2016-09-22 15:05:16][Timer-1][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - Retrying request - (HttpMethodDirector.java:445)
[2016-09-22 15:05:16][main][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect - (HttpMethodDirector.java:439)
[2016-09-22 15:05:16][main][org.apache.commons.httpclient.HttpMethodDirector:executeWithRetry] INFO - Retrying request - (HttpMethodDirector.java:445)
[2016-09-22 15:05:37][Timer-1][com.kaltura.client.KalturaClientBase:executeMethod] ERROR - Fatal transport error: Connection timed out: connect - (KalturaClientBase.java:374)
java.net.ConnectException: Connection timed out: connect
at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:125)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at com.kaltura.client.KalturaClientBase.executeMethod(KalturaClientBase.java:307)
at com.kaltura.client.KalturaClientBase.doQueue(KalturaClientBase.java:267)
at com.kaltura.client.services.KalturaMediaServerService.reportStatus(KalturaMediaServerService.java:71)
at com.kaltura.media.server.managers.KalturaStatusManager.reportStatus(KalturaStatusManager.java:58)
at com.kaltura.media.server.managers.KalturaStatusManager$1.run(KalturaStatusManager.java:38)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
[2016-09-22 15:05:37][main][com.kaltura.client.KalturaClientBase:executeMethod] ERROR - Fatal transport error: Connection timed out: connect - (KalturaClientBase.java:374)
java.net.ConnectException: Connection timed out: connect
at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:125)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at com.kaltura.client.KalturaClientBase.executeMethod(KalturaClientBase.java:307)
at com.kaltura.client.KalturaClientBase.doQueue(KalturaClientBase.java:267)
at com.kaltura.client.services.KalturaFlavorParamsService.list(KalturaFlavorParamsService.java:114)
at com.kaltura.client.services.KalturaFlavorParamsService.list(KalturaFlavorParamsService.java:102)
at com.kaltura.client.services.KalturaFlavorParamsService.list(KalturaFlavorParamsService.java:98)
at com.kaltura.media.server.managers.KalturaLiveManager.loadLiveParams(KalturaLiveManager.java:623)
at com.kaltura.media.server.managers.KalturaLiveManager.init(KalturaLiveManager.java:569)
at com.kaltura.media.server.wowza.LiveStreamManager.init(LiveStreamManager.java:26)
at com.kaltura.media.server.KalturaServer.initManagers(KalturaServer.java:213)
at com.kaltura.media.server.KalturaServer.(KalturaServer.java:80)
at com.kaltura.media.server.KalturaServer.init(KalturaServer.java:240)
at com.kaltura.media.server.wowza.listeners.ServerListener.onServerInit(ServerListener.java:26)
at com.wowza.wms.server.Server.l(Server.java:4355)
at com.wowza.wms.server.Server.start(Server.java:1114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wowza.wms.bootstrap.Bootstrap.startServer(Bootstrap.java:650)
at com.wowza.wms.bootstrap.Bootstrap.main(Bootstrap.java:67)

2

Hello,

Please see my posts here:

We’re not actively supporting Wowza and Kaltura Live integration with CE in light of the work being done to release a new solution against Nginx’s RTMP module. Will let you know once that’s ready.

Thanks,

3

Hello,

As promised, with 12.4.0, one can now accomplish live streaming w/o the need for Wowza.
Please see:


For more info.

4

Hi,

I have installed kaltura ce 12 recently. i was looking for doing livestreaming with it. i have created a live stream entry in KMC, but on providing rtmp url in adobe flash live media encoder it says incorrect url . i am using below url to connect .
rtmp://$NGINX_HOST:1935/kLive/stream

5

Hello,

I’m a little confused… you wrote “wowza” in the subject but in your post you are referring to Nginx.
Which one is it?

Start by running:
# netstat -plnt |grep 1935

I assume you DO mean Nginx, which is provided by the kaltura-nginx package, which is fetched as a dependency when installing the kaltura-server package.

After making sure nginx is running and has a listener on port 1935 TCP, check if you can telnet to it from the machine you’re trying to stream to, this can be done with:
# telnet $NGINX_HOST 1935

we can take it from there, based on the current situation.

6

Hi Jess,

Yes you are assumption is correct . i mean Nginx only . Apology for posting the question in wrong subject line .

netstat -plnt |grep 1935 this command runs gave the below output.
tcp 0 0 0.0.0.0:1935 0.0.0.0:* LISTEN 36676/nginx

telnet $NGINX_HOST 1935

Trying $NGINX_HOST …
Connected to $NGINX_HOST.
Escape character is ‘^]’.
Connection closed by foreign host.

the rtmp url which the livestream entry has in KMC is like.
rtmp://$NGINX_HOST:1935/kLive/?t=a81a4003(Note : i have commented the queryParams = {p}.{e}.{i} in broadcasting.ini file as with queryparam also the rtmp url was not working in adobe FLME)

we have done below scenarios to test with nginx and Wowza both:
1)wowza up,nginx down

rtmp://$NGINX_HOST:1935/kLive/?t=a81a4003
connects and live streams fine to wowza but kaltura player doesnt show livestream

  1. nginx up
    url in KMC: rtmp://$NGINX_HOST:1935/kLive/?t=a81a4003

when used below url in FLME
rtmp://$NGINX_HOST:1935/kLive/
connects ,live streaming starts in adobe FLME but kaltura player doesnt show livestream

how can we trim the extra query parameter ‘t’ in rtmp url which gets generaeted while creating live entry in KMC.

Thanks for the quick reply.

7

Hi @jitender_sharma,

Please look at the instructions here:

Specifically:
To stream use:
rtmp://$NGINX_HOST:1935/kLive/stream

to get the HLS manifest for playback, use:
http://$NGINX_HOST:$NGINX_PORT/hlsme/stream.m3u8

To use this with the HTML5 Kaltura player, go to KMC->Upload->Live Stream Entry->under Live Stream Type select Manual Live Stream URLs, provide a name and then in the URL input http://$NGINX_HOST:$NGINX_PORT/hlsme/stream.m3u8 and uncheck “Akamai HD protocol…”

Make sure you’re using kaltura-html5lib of version 2.48.1 or above.

I suspect you did not choose “Manual Live Stream” under “Live Stream Type”…

8

Hi @jess,

i have looked into those instructions . i am using kaltura -html5lib of version 2.50.

i have tried by choosing manual livestream, In adobe FLME it only connects when i give fms url till rtmp://$NGINX_HOST:1935/kLive/ and creates the streaming files also in /var/tmp folder. but kaltura is not playing the stream. not sure why kaltura is not picking the files and showing live stream.

when i use this as fms url rtmp://$NGINX_HOST:1935/kLive/stream .it cant connect to primary server

9

Hi,

Please provide a URL where you embedded the player s I can take a look.
Also, what did you use for the manifest URL when creating the entry?

10

Hi @jess

We are not embedding the player in html page . We are just previewing the live stream in KMC only (using the kaltura default players).

The manifest url that we are using is “http://XXXX:1935/hlsme/stream.m3u8”. as mentioned by you earlier .
When i try to connect using this “rtmp://XXXX:1935/kLive/stream” , I am not able to connect to primary server in Adobe FMLE .

The url which connects successfully in FMLE is “rtmp://XXXX:1935/kLive/”.

Could you please suggest why I am not able to connect to this “rtmp://XXXX:1935/kLive/stream” ?

11

Hi @jitender_sharma,

Like I said, I need a sample URL I can look at to help you further.
Also, as mentioned before, make sure you’re using a HTML5 player [not the legacy Flash] of version 2.48.1 and above.

12

Hi @jess,

This is Aalekh. I am also working with Jitender on the same issue.
All the above issues have been resolved and live stream is now happening successfully.
But when embedding the player in an html page, the live stream is playing fine on the desktop browser but when emulating the browser to check if video is playing fine on android and apple devices, video is not playing.

When emulating for Android device, when I click on play button in the player, black screen remains and no video is played.
When checking the console using developer tool, I get below errors:-
Uncaught (in promise) DOMException: The element has no supported sources.
Uncaught (in promise) DOMException: Failed to load because no supported source was found.

When emulating for Apple device, alert appears in the player “Your browser does not support live stream playback”.
No error appears in the console of developer tools.

Please suggest what could be wrong.

13

Hi @mathuraalekh8,

Sorry to be repeating this but -