Fix error logging to be less noisy for port scans

[mushorg]

Fix error logging to be less noisy for port scans

[glaslos]

You want to change this line: https://github.com/mushorg/glutton/blob/master/system.go#L34

[glaslos]

Did we confirm that you will get all ports when specifying the range?

[kung-foo]

might be worth making a system test via Docker

[david-watson]

Default nmap scans top 1000 ports, so no ports missed, but a lot of errors in the logs

[kung-foo]

probably comes from: https://github.com/kung-foo/freki/blob/master/userconnhandler_tcp.go#L45

[glaslos]

Updated title to reflect feedback

[t3chn0m4g3]

I have a comparable situation which I think might be related to new connections / drops in normal operation (no portscan). For every connection attempt I am getting a ...

{"level":"info","ts":1523885848.9937115,"caller":"glutton/system.go:34","msg":"[system  ] running Go routines: 16 and open files: 9","sensorID":"ce2600c6-62dd-47e8-b4cd-507e83081847"}

... even if debug is set to false.

Is there an easy way to tune that down or just log [log.tcp ]-related events?

[t3chn0m4g3]

@glaslos Thank you, just got rid of ...

			case <-ticker.C:
				openFiles := countOpenFiles()
				runningRoutines := countRunningRoutines()
				g.logger.Info(fmt.Sprintf("[system  ] running Go routines: %d and open files: %d",
					openFiles, runningRoutines))

... and the log file is finally quiet when nothing is going on.

[glaslos]

You could also change g.logger.Info to g.logger.Debug and set Gluttons log level to info.

[glaslos]

@t3chn0m4g3 do you want to try to reproduce this with the switch to TPROXY?