Hi,
I have installed Wowza Streaming Engine 4.4.1 on a CentOS 64-bit machine. When I tried to login using Streaming Engine Manager, it is taking very long time (~30 seconds) before a successful login. Even subsequent operations through the manager takes very long time.
I have tried running Wowza as a Service as well as Standalone, but the problem persist in both the modes.
Could you please help me in resolving this issue?
Regards,
kspdixit
Take a look at the logs to see if there is anything suspicious there. Take a look at CPU/memory load as well.
It may also be a DNS issue - are you accessing wowza using a hostname? If so, try using IP address instead. If it works ok like that, check your DNS for problems.
Hello,
You may also want to check your [install-dir]/logs/wowzastreamingengine_access.log files to ensure that there’s no binding errors, as this could indicate another program on the server is currently using the port. Wowza Streaming Engine Manger used ports (TCP 8087, 8088).
Also, checking to make sure your Java version is updated would also be a good idea. You can find information on how to update Java in the following article:
Manually Install and Troubleshoot Java
Currently we recommend selecting Java version 8u77 or earlier due to a known issue with 8u78.
Best regards,
Andrew
When logging into the engine manager, click on the “+Server” button and verify the correct ip and port.
If there are no problems there, take a look at this post Wowza 4.3.0 Slow Web Performance
Take a look at the processes and make sure there is only one Wowza Streaming Engine and only one Wowza Streaming Engine Manager. I don’t really expect this to be the cause of such a problem, but doesn’t hurt to check just in case…
Yes, I recommend opening a ticket - Wowza support will be able to take a closer look at the configuration, logs, etc. and maybe find something we’ve missed.
Hi,
I am running on a Xeon E3 V4 processor and CPU load during login is very low (~1%).
I am accessing it through IP address (and not through hostname). Also, I do not see any problem with DNS queries.
However, I noticed some HTTP connection error in wmsmanager_access.log, could that be a reason for this?
#Version: 1.0
#Start-Date: 2016-07-05 09:33:14 PKT
#Software: Wowza Streaming Engine Manager 4.4.1 build17882
#Date: 2016-07-05
#Fields: date time tz x-server x-user x-severity x-category x-comment
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener OS Name: Linux:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener OS Version: 3.10.0-229.1.2.39163.MSSr4.el7.centos.x86_64:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener OS Architecture: amd64:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Name: Java HotSpot™ 64-Bit Server VM:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Vendor: Oracle Corporation:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Version: 1.8.0_60:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java VM Version: 25.60-b23:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Spec Version: 1.8:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Home: /usr/local/WowzaStreamingEngine-4.4.1/jre1.8.0_60:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Max Heap Size: 3291MB:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Architecture: 64:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Locale[user.language]: en:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Locale[user.country]: US:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Locale[file.encoding]: UTF-8:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Timezone[user.timezone]: Asia/Karachi:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Args[0]: -Dcom.wowza.wms.ConfigURL="":
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Args[1]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine/manager:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Args[2]: -Djava.io.tmpdir=/usr/local/WowzaStreamingEngine/manager/temp:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Args[3]: -Dlog4j.configuration=file:///usr/local/WowzaStreamingEngine/manager/conf/winstone.properties:
2016-07-05 09:33:14 PKT INFO com.wowza.wms.logging.Log4jStartupListener Java Args[4]: -Djava.net.preferIPv4Stack=true:
2016-07-05 09:33:14 PKT INFO org.hibernate.validator.util.Version Hibernate Validator null
2016-07-05 09:33:15 PKT INFO com.wowza.wms.server.ManagerConfiguration Loading configuration from /usr/local/WowzaStreamingEngine/manager/conf/Manager.xml:
2016-07-05 09:33:15 PKT INFO com.wowza.wms.server.ManagerConfiguration Loading configuration from /usr/local/WowzaStreamingEngine/manager/conf/Manager.xml:
2016-07-05 09:33:15 PKT INFO com.wowza.wms.webapp.RequestLoggingFilter RequestLoggingFilter disabled, no HTTP requests will be logged:
2016-07-05 09:33:58 PKT WARN org.restlet An error occurred during the communication with the remote HTTP server.: java.net.ConnectException: Connection refused|at java.net.PlainSocketImpl.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.SocksSocketImpl.connect(SocksSocketImpl.java:392)|
2016-07-05 09:35:12 PKT INFO rest REST API: Authentication: Successful login for:bms_sys:
Hi,
I checked the IP address and port and it is proper (I tried using localhost as well as IP address). I can access the link (http://localhost:8087) from other browser tab to get the Wowza Streaming Engine version number. Also, the problem is not about connecting, the problem is about slowness. It eventually logs in but takes very long time for each input including login.
I tried clearing the browser cache, tried from a different browser, from a different machine. Nothing helped.
Also, the link which you suggested does not provide any solution, it has recommended to open a service ticket. Do you recommend the same?
© 2007–2024 Wowza Media Systems™, LLC. All rights reserved. Security & Privacy PolicyLegalSystem Status