July 31, 20169 yr I know I mentions this in another thread, but since I added so many other things, it may have got over looked. This is filling up syslog. Doesn't seem to be causing a problem, but anything to do with SSHD bothers me. Line 2381: Jul 30 13:20:06 SUN sshd[18702]: Did not receive identification string from 192.168.1.232 Line 2384: Jul 30 13:20:08 SUN sshd[18711]: Did not receive identification string from 192.168.1.232 Line 2393: Jul 30 13:35:27 SUN sshd[20744]: Did not receive identification string from 192.168.1.232 Line 2396: Jul 30 13:50:38 SUN sshd[22729]: Did not receive identification string from 192.168.1.232 sun-diagnostics-20160731-1521.zip
July 31, 20169 yr I know I mentions this in another thread, but since I added so many other things, it may have got over looked. This is filling up syslog. Doesn't seem to be causing a problem, but anything to do with SSHD bothers me. Line 2381: Jul 30 13:20:06 SUN sshd[18702]: Did not receive identification string from 192.168.1.232 Line 2384: Jul 30 13:20:08 SUN sshd[18711]: Did not receive identification string from 192.168.1.232 Line 2393: Jul 30 13:35:27 SUN sshd[20744]: Did not receive identification string from 192.168.1.232 Line 2396: Jul 30 13:50:38 SUN sshd[22729]: Did not receive identification string from 192.168.1.232 Is 192.168.1.232 on your network your desktop/laptop? Some software or service on that machine is 'pinging' or doing a healthcheck against your unRAID's SSH port. Might be a sftp program doing a 'keepalive' or something...
August 1, 20169 yr Author I know I mentions this in another thread, but since I added so many other things, it may have got over looked. This is filling up syslog. Doesn't seem to be causing a problem, but anything to do with SSHD bothers me. Line 2381: Jul 30 13:20:06 SUN sshd[18702]: Did not receive identification string from 192.168.1.232 Line 2384: Jul 30 13:20:08 SUN sshd[18711]: Did not receive identification string from 192.168.1.232 Line 2393: Jul 30 13:35:27 SUN sshd[20744]: Did not receive identification string from 192.168.1.232 Line 2396: Jul 30 13:50:38 SUN sshd[22729]: Did not receive identification string from 192.168.1.232 Is 192.168.1.232 on your network your desktop/laptop? Some software or service on that machine is 'pinging' or doing a healthcheck against your unRAID's SSH port. Might be a sftp program doing a 'keepalive' or something... I changed the IP address on my computer and it stopped for a while and srarted again. I've always been good doing house cleaning on a PC, so I ran my utilities. Delete all TEMP user files for ALL users. Delete all TEMP Windows folders. Uninstall lots of uneeded programs, and pay close attention to what starts up with Windows using the Sysinternals Utilities. After I did that, rebooted, they finally went away. Can't think of what I could of put on this machine, but it's one of them I don't care about much and do a lot of testing on. Might be time for a reformat.
Archived
This topic is now archived and is closed to further replies.