I’ve installed Wowza on Linux. Everything seems to be working fine.
When I try to use the manager, I get this error:
Wowza Streaming Engine Manager could not connect to the Wowza Steaming Engine (http://localhost/:8087). Verify that the Wowza Streaming Engine service has started and is running.
I have checked using the sudo service WowzaStreamingEngineManager status call and it says the manager is running.
Are there any other reasons I might get this message?
I am connecting remotely.
Under the login, where it lets you set the server, I have tried changing it from localhost/:8087 to {my IP}/:8087 with no luck.
Hi,
You could certainly follow the XML configuration section of the IP Camera setup guide.
It is far easier to use the manager though.
I’d say the server that you are running Wowza Streaming Engine on is insufficient (500MB of memory and one single core processor). We recommend at least 4GB of memory and a Quad core cpu.
Daren
Hi,
The instructions DO cover configuring the old way. The link provided points to the XML configuration section of the guide and using the ‘streammanager’ to start the stream.
When using the manager, ensure that the Wowza Streaming Engine Manager and Wowza Streaming Engine services are both running.
The first server specification you showed was certainly inadequate, so hopefully rectified now?
The manager logs are located in [install-dir]/manager/logs and might highlight the problems you are running into.
You can post the startup of the manager logs here if you like.
Daren
Everything is on the same server, so the first part should be the correct configuration, right?
TO be clear,
I am not physically on the server. I am connecting from a remote location. However, WMS and the manager are both on the same server.
On top of everything else, every time I try to connect, WMS shuts down.
Error Log:
#Version: 1.0
#Start-Date: 2015-03-24 07:24:38 EDT
#Software: Wowza Streaming Engine 4.1.0 build12602
#Date: 2015-03-24
#Fields: x-severity x-category x-event date time c-client-id c-ip c-port cs-bytes sc-bytes x-duration x-sname x-stream-id x-spos sc-stream-bytes cs-stream-bytes x-file-size x-file-length x-ctx x-comment
WARN server comment 2015-03-24 07:24:46 - - - - - 10.091 - - - - – - - REST Documentation Server has been disabled.
#Version: 1.0
#Start-Date: 2015-03-24 07:29:53 EDT
#Software: Wowza Streaming Engine 4.1.0 build12602
#Date: 2015-03-24
#Fields: x-severity x-category x-event date time c-client-id c-ip c-port cs-bytes sc-bytes x-duration x-sname x-stream-id x-spos sc-stream-bytes cs-stream-bytes x-file-size x-file-length x-ctx x-comment
WARN server comment 2015-03-24 07:30:03 - - - - - 11.339 - - - - – - - REST Documentation Server has been disabled.
#Version: 1.0
#Start-Date: 2015-03-24 07:30:38 EDT
#Software: Wowza Streaming Engine 4.1.0 build12602
#Date: 2015-03-24
#Fields: x-severity x-category x-event date time c-client-id c-ip c-port cs-bytes sc-bytes x-duration x-sname x-stream-id x-spos sc-stream-bytes cs-stream-bytes x-file-size x-file-length x-ctx x-comment
WARN server comment 2015-03-24 07:30:44 - - - - - 8.17 - - - - – - - REST Documentation Server has been disabled.
#Version: 1.0
#Start-Date: 2015-03-24 07:31:34 EDT
#Software: Wowza Streaming Engine 4.1.0 build12602
#Date: 2015-03-24
#Fields: x-severity x-category x-event date time c-client-id c-ip c-port cs-bytes sc-bytes x-duration x-sname x-stream-id x-spos sc-stream-bytes cs-stream-bytes x-file-size x-file-length x-ctx x-comment
WARN server comment 2015-03-24 07:31:40 - - - - - 7.576 - - - - – - - REST Documentation Server has been disabled.
#Version: 1.0
#Start-Date: 2015-03-24 07:33:31 EDT
#Software: Wowza Streaming Engine 4.1.0 build12602
#Date: 2015-03-24
#Fields: x-severity x-category x-event date time c-client-id c-ip c-port cs-bytes sc-bytes x-duration x-sname x-stream-id x-spos sc-stream-bytes cs-stream-bytes x-file-size x-file-length x-ctx x-comment
WARN server comment 2015-03-24 07:33:37 - - - - - 8.356 - - - - – - - REST Documentation Server has been disabled.
Access log:
#Version: 1.0
#Start-Date: 2015-03-24 07:33:30 EDT
#Software: Wowza Streaming Engine 4.1.0 build12602
#Date: 2015-03-24
#Fields: date time tz x-event x-category x-severity x-status x-ctx x-comment x-vhost x-app x-appinst x-duration s-ip s-port s-uri c-ip c-proto c-referrer c-user-agent c-client-id cs-bytes sc-bytes x-stream-id x-spos cs-stream-bytes sc-stream-bytes x-sname x-sname-query x-file-name x-file-ext x-file-size x-file-length x-suri x-suri-stem x-suri-query cs-uri-stem cs-uri-query
2015-03-24 07:33:34 EDT server-start server INFO 200 Wowza Streaming Engine 4 Trial Edition (Expires: Sep 21, 2015) 4.1.0 build12602 - - - - 4.507 - - - - - - - - – - - - - - - - - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Server License Key: ET1A4-XXXXX-XXXXX-XXXXX-XXXXX-awufN- - - 4.558 - - - - - - - - - - - - - – - - - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Maximum Connections: 10 - - - 4.558 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Maximum Incoming Streams: 3 - - - 4.559 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Transcoder Streams Available: 1 - - - 4.564 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Transcoder Watermark: Yes - - - 4.565 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - nDVR Available: Yes - - - 4.565 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - DRM Available: Yes - - - 4.566 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - HTTP Origin Available: No - - - 4.583 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Push Publish Available: Yes - - - 4.584 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - REST API Available: Yes - - - 4.585 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Hardware Available Processors: 1 - - -4.587 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Hardware Physical Memory: 35MB/490MB - - -4.588 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Max File Descriptor Count: 20000 - - -4.589 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Open File Descriptor Count: 62 - - - 4.59 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - OS Name: Linux - - - 4.591 - – - - - - - - - - - - - - - - - - – - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - OS Version: 3.10.0-123.8.1.el7.x86_64 - - -4.591 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - OS Architecture: amd64 - - - 4.592 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Name: OpenJDK 64-Bit Server VM - - -4.592 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Vendor: Oracle Corporation - - - 4.593 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Version: 1.7.0_75 - - - 4.642 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java VM Version: 24.75-b04 - - - 4.643 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Spec Version: 1.7 - - - 4.644 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.el7_0.x86_64/jre - - - 4.644 - - - - - - - - - - – - - - - - - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Max Heap Size: 183MB - - - 4.645 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Architecture: 64 - - - 4.645 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Locale[user.language]: en - - - 4.646 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Locale[user.country]: US - - - 4.646 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Locale[file.encoding]: UTF-8 - - -4.647 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Timezone[user.timezone]: America/New_York - – 4.648 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[0]: -Xmx196M - - - 4.649 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[1]: -XX:+UseConcMarkSweepGC - - -4.649 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[2]: -XX:+UseParNewGC - - - 4.65 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[3]: -XX:NewSize=128m - - - 4.65 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[4]: -Djava.net.preferIPv4Stack=true - – 4.651 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[5]: -Dcom.sun.management.jmxremote=true – - 4.651 - - - - - - - - - - - - - - – - - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[6]: -Dcom.wowza.wms.runmode=service - – 4.652 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[7]: -Dcom.wowza.wms.native.base=linux - – 4.704 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[8]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaStreamingEngine - - - 4.705 - - - - - - - - - - - – - - - - - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[9]: -Dcom.wowza.wms.ConfigURL= - – 4.706 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Java Args[10]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine - - - 4.706 - - - - - - - - - - – - - - - - - - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Server runmode: service - - - 4.707 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Server native.platform: linux - - - 4.707 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:34 EDT comment server INFO 200 - Server threads[h/t]: 120/80 - - - 4.708 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:35 EDT comment server INFO 200 - RESTServer: Bind attempt ([any]:8087) - - -5.915 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:36 EDT comment server INFO 200 - RESTServer: Bind successful ([any]:8087) - – 7.117 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:36 EDT comment server INFO 200 - Wowza REST API started - - - 7.118 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:36 EDT comment server INFO 200 - RESTServer: Using configs from:/usr/local/WowzaStreamingEngine/ - - - 7.13 - - - - - - - - - - - – - - - - - - - - - - - -
2015-03-24 07:33:36 EDT comment server INFO 200 - RESTServer: SSL:No - - - 7.131 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:36 EDT comment server INFO 200 - RESTServer: BasicAuth:No - - - 7.131 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:36 EDT comment server INFO 200 - RESTServer: Digest:Yes - - - 7.132 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:36 EDT comment server INFO 200 - RESTServer: XML Viewer:No - - - 7.132 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:37 EDT comment server WARN 200 - REST Documentation Server has been disabled. - – 8.356 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:38 EDT comment server INFO 200 - CMDInterface now listening: [any]:8083 - - -8.473 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:38 EDT comment server INFO 200 - MediaCache[MediaCache]: Thread pool size: [writer/readahead]:4/2 - - - 8.843 - - - - - - - - - - - – - - - - - - - - - - - -
2015-03-24 07:33:38 EDT comment server INFO 200 - MediaCache[MediaCache]: MAX Pending size: [writer/readahead]:500M/25M - - - 8.844 - - - - - - - - - - - – - - - - - - - - - - - -
2015-03-24 07:33:38 EDT comment server INFO 200 - MediaCache[MediaCache]: Add store: path:/usr/local/WowzaStreamingEngine/mediacache maxSize:10737418240 - - - 8.844 - - - - - - - – - - - - - - - - - - - - - - - -
2015-03-24 07:33:38 EDT comment server INFO 200 - MediaCache[MediaCache]: Add source[dvrorigin]: prefix:dvrorigin/ basePath:http:// - - - 9.185 - - - - - - - - - – - - - - - - - - - - - - - -
2015-03-24 07:33:38 EDT comment server INFO 200 - MediaCache[MediaCache]: Flushing cache: start - – 9.233 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:41 EDT comment server INFO 200 - REST API: ready - - - 11.597 - – - - - - - - - - - - - - - - - - – - - - -
2015-03-24 07:33:42 EDT comment server INFO 200 - MediaCache[MediaCache]: Flushing cache: done - – 13.366 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:42 EDT comment server INFO 200 - MediaCache[MediaCache]: Start MediaCache GC - – 13.366 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:42 EDT comment server INFO 200 - MediaCache[MediaCache]: Started - - - 13.39 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:47 EDT vhost-start vhost INFO 200 defaultVHost - - - - 17.62 – - - - - - - - - - - - - - - - - – - - - - -
2015-03-24 07:33:47 EDT comment server INFO 200 - defaultVHost threads[h/t]:0/0 home:/usr/local/WowzaStreamingEngine - - - 17.884 - - - - - - - - - - - – - - - - - - - - - - - -
2015-03-24 07:33:47 EDT comment vhost INFO 200 defaultVHost Bind attempt ([any]:1935:4) - - -17.887 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:47 EDT comment vhost INFO 200 defaultVHost Bind successful ([any]:1935) - - -17.923 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:47 EDT comment vhost INFO 200 defaultVHost Bind attempt ([any]:8086:2) - - -17.926 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:47 EDT comment vhost INFO 200 defaultVHost Bind successful ([any]:8086) - - -17.949 - - - - - - - - - - - - - - - - – - - - - - - -
2015-03-24 07:33:47 EDT comment server INFO 200 - Server.startShutdownHook: Start server shutdown hook – - 17.965 - - - - - - - - - - - - - - – - - - - - - - - -
2015-03-24 07:33:47 EDT comment server INFO 200 - StatsManager:startManager() Enabled=true - – 18.312 - - - - - - - - - - - - - - - – - - - - - - - -
2015-03-24 07:33:47 EDT comment server INFO 200 - Wowza Streaming Engine is started! - - -18.312 - - - - - - - - - - - - - - - - – - - - - - - -
[root@wowza logs]#
I’m not seeing anything in here.
Could the wya it was installed be causing this problem?
I followed instructions from some site. But then found the Wowza instructions that said to use ‘sudo’ in front of all the installations commands. I was logged in as root when I installed it.
Could someone from Wowza please help me here?
My client wants to switch from Red5 to Wowza but won’t bother if we can’t get this working.
I sold him on Wowza, so please help.
At the very least, please tell me how I can do IP camera streaming WITHOUT the manager application. The only link I found required it for both set-up options.
Thanks.
You might want to update that page. It gives the impression the streams can only be started with the manager. It took me a while to find some documentation that shows how to start the streams without the manager.
I’m sorry, but I’m really becoming disappointed in Wowza.
I’ve used it on and off for several years with little or no problem. But now, this Wowza Streaming Engine seems to be nothing but problems.
I’ve installed it on 2 different servers. And the manager features don’t work on either one.
All of your instructions push this manager and have not full back-up instructions for doing things manually.
Perhaps you guys should slow down a bit and make sure everything works as advertised or at least provide proper documentation to work around this manager.
Okie.
I admit perhaps I came on a little strong with my criticism, but try to look at it from my point of view.
I have been working with Wowza for several years now. I am used to manually configuring everything.
Now, with this ‘streaming engine’, many things have changed. Mainly, you guys are pushing this streaming engine manager software.
I can see this is an expected improvement to make things better for your clients. But you guys have made every ‘how-to’ article reliant on this manager. You seem to have forgotten that there are many out here who have supported your software from its infancy and are quite comfortable with configuring things manually.
As far as your claim about inadequate hardware I can only say that, like you, I am a software developer and don’t buy this ‘inadequate resources’ as an valid argument for running 2 pieces of software. I first started programming on C=64 and even it could run 2 pieces of ‘complex’ software with no problem.
At this point it is too late to resolve my issues. I tried to upsell Wowza to my client, it failed and he has decided to dump the idea.
At this point, I can only ask that you guys remember us ‘little guys’ who have helped your company reach the level it has and offer more adequate support for our needs.
Hello there.
Please take a look at this guide and see if it solves this issue for you:
How to connect to remote Streaming Engine installations (whitelist)
Kind regards,
Salvadore