Menu
This is debug.log file:
[0110/160818:ERROR:tcp_listen_socket.cc(76)] Could not bind socket to 127.0.0.1:6004 [0110/160818:ERROR:node_debugger.cc(86)] Cannot start debugger server [0111/233417:ERROR:tcp_listen_socket.cc(76)] Could not bind socket to 127.0.0.1:6004 [0111/233417:ERROR:node_debugger.cc(86)] Cannot start debugger server [0113/120522:ERROR:tcp_listen_socket.cc(76)] Could not bind socket to 127.0.0.1:6004 [0113/120522:ERROR:node_debugger.cc(86)] Cannot start debugger server [0113/122245:ERROR:tcp_listen_socket.cc(76)] Could not bind socket to 127.0.0.1:6004 [0113/122245:ERROR:node_debugger.cc(86)] Cannot start debugger server [0120/171545:ERROR:tcp_listen_socket.cc(76)] Could not bind socket to 127.0.0.1:6004 [0120/171545:ERROR:node_debugger.cc(86)] Cannot start debugger server [0207/173408:ERROR:tcp_listen_socket.cc(76)] Could not bind socket to 127.0.0.1:6004 [0207/173408:ERROR:node_debugger.cc(86)] Cannot start debugger server
403
A debug log file contains status and error messages useful for debugging the license server. A license server always generates debug log output. Some of the debug log output describes events specific to lmgrd and some of the debug log output describes events specific to each vendor daemon.
Debug logs are stored in the user data directory as chrome_debug. log. The file is overwritten every time Chrome restarts. So, if you have an issue with the browser, check the log before you restart Chrome.
I have no idea why they are being created (In my case, they are everywhere!), but I found how to ignore them ;)
Add the following to your .gitignore file. Problem solved!
**/debug.log
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
