![]() Mar 6 22:17:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) Mar 6 22:09:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) Mar 6 21:39:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) Mar 6 21:17:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) Mar 6 21:09:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) Mar 6 20:39:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) Mar 6 20:17:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) Mar 6 20:09:01 tux CRON: pam_unix(cron:account): account root has expired (account expired) not sure why there is nothing in it before 3/6 20:17. Not sure if this will help, my auth.log seems really screwy. Sudo echo > /home/USERNAME/.ssh/known_hosts If you have special host keys, do not do this. (this will completely wipe it and make you have to confirm the first time you ssh again to your machines). To fix this, i find the simplest way is to clear my /home/USERNAME/.ssh/known_hosts file. This always happens to me when i reinstall ubuntu onto my server. This is because the key the local SSH system has on record for this machine is now different because the machine is sending out the new one you just generated. When prompted for a password, i find its easier to just leave it blank by hitting enter, so you don't have to enter it at boot time.Īlso, when you later try and ssh in from the client machine, it will probably complain about "HOST VERIFICATION CHANGED". Sudo ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key Sudo ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key * Starting OpenBSD Secure Shell server sshd Could not load host key: /etc/ssh/ssh_host_rsa_key ![]() Subsystem sftp /usr/lib/openssh/sftp-server # Allow client to pass locale environment variables # Change to no to disable tunnelled clear text passwords # Change to yes to enable challenge-response passwords (beware issues with # To enable empty passwords, change to yes (NOT RECOMMENDED) # Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication # For this to work you will also need host keys in /etc/ssh_known_hosts # Don't read the user's ~/.rhosts and ~/.shosts files #AuthorizedKeysFile %h/.ssh/authorized_keys # Lifetime and size of ephemeral version 1 server key #Privilege Separation is turned on for security # Use these options to restrict which interfaces/protocols sshd will bind to # What ports, IPs and protocols we listen for * Starting OpenBSD Secure Shell server sshdĬould not load host key: /etc/ssh/ssh_host_rsa_keyĬould not load host key: /etc/ssh/ssh_host_dsa_key Here is what happens when i start /etc/init.d/ssh start Any advice as to where I should be looking? I have rebooted the system since this start, and what I have described above is the very last thing I did before this issue started. I am using iptables, but every entry for that is empty now. I was running hostsdeny but that has been stopped for a while now. From work the session just times out in putty, from home I get a server unexpected closed session error. I purposefully killed the session I knew was my current ssh session and was booted, and now can not ssh in. So I say from the cmd above several sessions that from my perspective were open, so I did a kill -9 command on a few PIDs. ![]() So I did ps -aux | grep ssh to see what was open because I know since I have set up the system I have had putty sessions lock up on me and wanted to look into. I did some research on killing sessions and found something on checking sessions and killing them with a kill -9. This is the end of the tutorial.Today from work I was screwing around on my system in putty was looking for info on killing sessions. From here you can run dozens of commands to manage your server.ħ) To exit, simply type Exit here, then push. You can view what IP last logged in, and on what date. You are now logged into your server via SSH with PuTTY. Before you begin, you will need to log into the serverĦ) Next, type in your password, or right-click to paste it This tutorial will show how to enter your connection settings to connect via SSH with Port 22.Ģ) Enter the main server IP into the Host Name field. Now let's learn how to open PuTTY, configure the server connection settings for SSH, and launch the command lineġ) Double click the PuTTY icon to launch it This tutorial assumes you have already downloaded PuTTY and located it on your desktop Click here to see the article as a Video Tutorial!
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |