When clicking on items like Resource CPU/Memory Usage, Data Inputs Overview and the like gives the following error:
ERROR HttpListener - Exception while processing request from 192.168.xxx.xxx for /en-US/module/system/Splunk.Module.SimpleResultsTable/render?count=20&offset=0&maxlines=10&sid=1415262567.45&entityname=results&displayrownumbers=on&markinteractive=1&clientapp=sos&_=1415262570592: Connection closed by peer
and sometimes it is followed by:
WARN HttpListener - Socket error from 192.168.1.214 while accessing /en-US/module/system/Splunk.Module.SimpleResultsTable/render: Broken pipe
Just going to Deployment Topology (not clicking on any icon) gives:
WARN HandleJobsDataProvider - Requested argument count (100000) exceeds the maxresultrows limit specified under restapi stanza in limits.conf (50000)
This seems to be an IE 11 issue. It fails with IE 11 rather in compatibility mode or not. If I use Firefox (33.0.2) from the same machine, the failures are not seen. I am unsure rather it is an issue with SoS (3.2) or SideView Utils (3.3). Any thoughts???
I think it's a Splunk issue actually, something new in 6.2. Because I'm chasing another set of problems also caused by socket errors in HttpListener, also on Splunk 6.2. The ones I have seen are on windows so they present differently (Winsock errors for one thing), but they seem to represent new behavior as of 6.2. And as in this case the place where things are blowing up the worst is when the python controller in Splunk's own SimpleResultTable module tries to use the REST api to get its search results.
It is strange though that the errors go away if I use Firefox rather than IE 11. Splunk is running in a Linux virtual machine (like the previous versions) so you are correct that it is not Windows. I am connecting to Splunk from a Windows machine. I still am trying to get my head around Firefox working fine and IE 11 not. Going to mess around some more with IE settings to see if I can find something.