Loading...
Loading...
The NWUI console shows: Failed to fetch latest counts for Dashboard monitoring.get.error Linux: The /nsr/authc/logs/nwui.log shows: Windows: The C:\Program Files\EMC NetWorker\nsr\authc-server\tomcat\logs\nwui.log shows: HH:MM:SS [https-jsse-nio-9090-exec-7] ERROR c.e.n.c.n.i.MonitoringApi - Error in fetching count of activities based on status from Monitoring Service. java.net.ConnectException: Connection refused: connect HH:MM:SS [https-jsse-nio-9090-exec-3] ERROR c.e.n.c.n.i.MonitoringApi - Error in fetching count of activities based on status from Monitoring Service. Linux: The /nsr/nwui/monitoring/app/logs/monitoring-app.log shows: Windows: The C:\Program Files\EMC NetWorker\nwui\monitoring\app\logs\monitoring-app.log shows: YYYY-MM-DD HH:MM:SS [StartupInfoLogger] [main] INFO com.dell.emc.nw.monitoring.NwMonitoringApplication - Started NwMonitoringApplication in 22.145 seconds (JVM running for 25.477) YYYY-MM-DD HH:MM:SS [DirectJDKLog] [https-jsse-nio-9095-exec-6] INFO org.apache.coyote.http11.Http11Processor - Error parsing HTTP request header Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Request header is too large at org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:614) ~[tomcat-embed-core-9.0.48.jar!/:?] at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:292) [tomcat-embed-core-9.0.48.jar!/:?] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.48.jar!/:?] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:893) [tomcat-embed-core-9.0.48.jar!/:?] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1723) [tomcat-embed-core-9.0.48.jar!/:?] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.48.jar!/:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_321] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_321] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.48.jar!/:?] at java.lang.Thread.run(Thread.java:750) [?:1.8.0_321]
The default monitoring-app.properties setting for the HTTP header size is 8 KB. The default HTTP header may not be sufficient to accommodate all headers with a large Active Directory user or group settings.
Increase the monitoring-app.properties HTTP header size setting on the NetWorker Server. Stop the "NetWorker Management Web UI Server" service: Linux: sudo systemctl stop nwui Windows: net stop nwui Open the monitoring-app.properties file in a text editor: Linux: sudo vi /nsr/nwui/monitoring/app/conf/monitoring-app.properties Windows: notepad C:\Program Files\EMC NetWorker\nwui\monitoring\app\conf\monitoring-app.properties Add a new line for the server.max-http-header-size option with value of 32 KB server.max-http-header-size=32KB Save the changes to the monitoring-app.properties file. Start the "NetWorker Management Web UI Server" service: Linux: sudo systemctl start nwui Windows: net start nwui
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.