May 6, 201511 yr I'm seeing this in my syslog. 192.168.1.9 is my PC. I do use telnet to access the unRAID server. Other options? Anything to be concerned about? May 5 19:18:52 HunterNAS-6 sshd[15919]: Did not receive identification string from 192.168.1.9 May 5 19:33:54 HunterNAS-6 sshd[25254]: Did not receive identification string from 192.168.1.9 May 5 19:48:56 HunterNAS-6 sshd[1195]: Did not receive identification string from 192.168.1.9 May 5 20:03:57 HunterNAS-6 sshd[8946]: Did not receive identification string from 192.168.1.9 May 5 20:18:59 HunterNAS-6 sshd[17713]: Did not receive identification string from 192.168.1.9 May 5 20:34:00 HunterNAS-6 sshd[25895]: Did not receive identification string from 192.168.1.9 May 5 20:49:02 HunterNAS-6 sshd[30634]: Did not receive identification string from 192.168.1.9 May 5 21:04:04 HunterNAS-6 sshd[2824]: Did not receive identification string from 192.168.1.9 May 5 21:19:06 HunterNAS-6 sshd[7196]: Did not receive identification string from 192.168.1.9 May 5 21:34:07 HunterNAS-6 sshd[11064]: Did not receive identification string from 192.168.1.9 May 5 21:49:09 HunterNAS-6 sshd[14708]: Did not receive identification string from 192.168.1.9 May 5 22:04:10 HunterNAS-6 sshd[18159]: Did not receive identification string from 192.168.1.9
May 6, 201511 yr This happens when a connection to SSH (port 22 typically) is made but not completed. For example just using telnet to port 22 and disconnecting will cause this message to appear. This is either the result of your SSH server listening on the wrong port and getting connections not meant for it or something else connecting in error. What is running of 192.168.1.9?
May 6, 201511 yr Author Its my workstation which I have MobaXterm running telnet sessions. I often have it just running, checking things from time to time. And... I often close it without logging out. Could that be the issue? As i look at the syslog, there are a lot of these, but no duplicate sessions. Is there a way to terminate these old sessions?
May 6, 201511 yr Author Did a who -a and who -d root@HunterNAS-6:/dev# who -a 2015-05-05 17:34 1031 id=si term=0 exit=0 system boot 2015-05-05 17:34 run-level 3 2015-05-05 17:34 last=S 2015-05-05 17:34 1306 id=rc term=0 exit=0 LOGIN tty2 2015-05-06 17:00 4796 id=c2 LOGIN tty5 2015-05-06 17:00 4834 id=c5 LOGIN tty6 2015-05-06 17:00 4880 id=c6 LOGIN tty4 2015-05-06 17:00 4924 id=c4 root + tty1 2015-05-05 17:37 00:03 4316 LOGIN tty3 2015-05-05 17:34 4318 id=c3 root + pts/0 2015-05-06 16:57 . 3052 (192.168.1.9) pts/1 2015-05-06 17:00 4643 id=/1 term=0 exit=0 root@HunterNAS-6:/dev# who -d 2015-05-05 17:34 1031 id=si term=0 exit=0 2015-05-05 17:34 1306 id=rc term=0 exit=0 pts/1 2015-05-06 17:00 4643 id=/1 term=0 exit=0 root@HunterNAS-6:/dev# Tried pkill -9 -t (session - i.e. tty2, tty5, etc), but nothing happened...
July 27, 20169 yr I'm seeing this same thing. All I did was add an hard drive. What I noticed was all my drive lights are usually blue ( idle ) and now the drive I added is looks like it is reading and writing. I just finished a pre-clear. Computer 192.168.1.104 I can even turn off and see what happens. Jul 27 04:54:56 SUN sshd[19970]: Did not receive identification string from 192.168.1.104 Jul 27 05:10:12 SUN sshd[11859]: Did not receive identification string from 192.168.1.104 Jul 27 05:25:29 SUN sshd[2932]: Did not receive identification string from 192.168.1.104 Jul 27 05:40:45 SUN sshd[26573]: Did not receive identification string from 192.168.1.104 Jul 27 05:56:14 SUN sshd[18537]: Did not receive identification string from 192.168.1.104 Jul 27 06:11:33 SUN sshd[9742]: Did not receive identification string from 192.168.1.104 Jul 27 06:26:48 SUN sshd[703]: Did not receive identification string from 192.168.1.104 Jul 27 06:42:03 SUN sshd[24388]: Did not receive identification string from 192.168.1.104 Jul 27 06:57:18 SUN sshd[15583]: Did not receive identification string from 192.168.1.104 Jul 27 07:12:33 SUN sshd[6469]: Did not receive identification string from 192.168.1.104 Jul 27 07:27:48 SUN sshd[30015]: Did not receive identification string from 192.168.1.104 Jul 27 07:43:03 SUN sshd[21061]: Did not receive identification string from 192.168.1.104 Jul 27 07:58:18 SUN sshd[12212]: Did not receive identification string from 192.168.1.104 Jul 27 08:13:33 SUN sshd[3337]: Did not receive identification string from 192.168.1.104 Jul 27 08:28:47 SUN sshd[27012]: Did not receive identification string from 192.168.1.104 Jul 27 08:44:02 SUN sshd[18060]: Did not receive identification string from 192.168.1.104 Jul 27 08:59:19 SUN sshd[8947]: Did not receive identification string from 192.168.1.104 Jul 27 09:14:36 SUN sshd[32395]: Did not receive identification string from 192.168.1.104
August 1, 20169 yr Author I've not had any further action on this topic. Still have the same problem... let me know if you figure it out...
August 1, 20169 yr I've not had any further action on this topic. Still have the same problem... let me know if you figure it out... Oddly all I did was change my computer from static configuration to DHCP. After that, not one line came back. Have no idea.
Archived
This topic is now archived and is closed to further replies.