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: