On 6/20/24 21:05, dan moylan wrote:
jbk at kjkelra.com wrote:

On 6/20/24 15:44, dan moylan wrote:
i have two computers running on my home asus router network:
cmp1, cmp2, both running fc40.  cmp2 had been sshed into
cmp1 since yesterday with no issues, but then cmp2's
terminal locked up; neither ctl-c nor ctl-z had any effect,
and eventually i closed the tab.  ifconfig gave normal
output on both cmp1 and cmp2.  both were able to ping each
other as well as mit.edu.

puzzled, i blanked out .ssh/known_hosts on cmp2 and tried:

ssh moylan at cmp1

asked if i really wanted to connect, i said yes, and then
was asked for  moylan's password.  an incorrect password
prompted a second request followed by a correct password.
the window then locked up.

any suggestions as to what i should do?
So you say this happened right after an update.
actually no, i never mentioned update.  it just happened,
out of the blue.
Yes, i agree you never mentioned updates, but I knew that was a factor with F40 since updates occur every other day. So do you have auto-updates enabled by choice? I have auto download enabled but not install because I want to read what's being updated just to hopefully be prepared that I might have to reboot.
Another thing you can do is see if the command:
systemctl daemon-reload
fixes things, doesn't always but may save an inconvenient reboot.


I might suggest you restore knownhosts and reboot. No you
don't have to reboot after all updates but when things don't
work soon after such I find reboots have solved the issue.
well i did reboot, and the problem went away.  should have
tried that without being prompted.

thanks,
ole dan

j. daniel moylan
84 harvard ave
brookline, ma 02446-6202
617-777-0207 (cel)
j...@moylan.us
www.moylan.us
[BLM]
_______________________________________________
Discuss mailing list
Discuss@driftwood.blu.org
https://driftwood.blu.org/mailman/listinfo/discuss


--
Jim KR
_______________________________________________
Discuss mailing list
Discuss@driftwood.blu.org
https://driftwood.blu.org/mailman/listinfo/discuss

Reply via email to