This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to
Article Number 000385088 for more information about troubleshooting BMC products in containers.
To use chrome://net-export/
- Open the Chrome browser
- Open this URL "chrome://net-export/ ". Select "include raw bytes" and click "Start Logging to disk" (Chrome will ask you for the location of the file where log will be saved)
- Make sure the tab where net-export is open stays open, closing it will stop the logs too.
- Navigate the application causing the problem
- Once the problem replicates, go back to "chrome://net-export/" tab and click "Stop Logging"
This log can then be loaded by Chrome.
Some situations that have been found with this log
- Network cache (causing redirection from HTTP to HTTPS)
- DNS issues as OS DNS entries expire too fast (every few seconds)
- Network problem OS 10054 error
- Connection aborted OS error 10053
- Traffic shaper on the ISP providing Server connectivity to Mid-tier server capping bandwidth
- Firewall blocking transactions or packets
- Some chrome extensions like https://digitalguardian.com/ found to redirect from POST backchannel request to GET, but without the POST payload, therefore the request is invalid for Mid-tier purposes
- Proxy can avoid some files from being downloaded: net_error = -355 (ERR_INCOMPLETE_CHUNKED_ENCODING). In this case Excel password / encrypted protected files
Reference article:
How to read Chrome Internals logs