No access ssh after the automatic update schedule

%3CLINGO-SUB%20id%3D%22lingo-sub-3256521%22%20slang%3D%22en-US%22%3ENo%20access%20ssh%20after%20the%20automatic%20update%20schedule%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3256521%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20guys!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20an%20automation%20account%20created%20by%20my%20client%20and%20have%20started%20scheduling%20automatic%20updates%20for%20a%20group%20of%20linux%20machines.%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20was%20successful%20except%20in%20one%20machine%2C%20I%20wanted%20to%20verify%20the%20problem%20by%20connecting%20with%20azure-cli%20(via%20powershell%20on%20my%20local%20pc)%20with%20the%20command%20%3CSTRONG%3Eaz%20ssh%20vm%20--ip%2010.xxx.xxx.xxx%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EBut%20nothing%20happens%2C%20I%20noticed%20that%20I%20can%20no%20longer%20connect%20to%20any%20of%20the%20linux%20machines%20to%20which%20I%20started%20the%20scheduling%20except%20two%20of%20them.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22azurecli_ssh.png%22%20style%3D%22width%3A%20798px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F355564iCB99CC86F8513016%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22azurecli_ssh.png%22%20alt%3D%22azurecli_ssh.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20tried%20to%20reset%20ssh%20with%20the%20command%20%3CSTRONG%3Eaz%20vm%20user%20reset-ssh%20--resource-group%20linux_test%20--ip%2010.xxx.xxx.xxx%3C%2FSTRONG%3E%2C%20rebooted%20the%20machine%20and%20now%20it%20asks%20me%20for%20the%20password%20that%20I%20don't%20know%20which%20one%20it%20refers%20to%20since%20mine%20does%20not%20accept%20it%20.%3C%2FP%3E%3CP%3EDid%20the%20update%20do%20something%20to%20the%20ssh%20service%3F%20How%20can%20I%20be%20able%20to%20connect%20to%20this%20group%20of%20linux%20machines%20again%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThank%20you%20and%20good%20day!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3256521%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAutomation%20%26amp%3B%20Control%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3264677%22%20slang%3D%22en-US%22%3ERe%3A%20No%20access%20ssh%20after%20the%20automatic%20update%20schedule%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3264677%22%20slang%3D%22en-US%22%3ECould%20it%20be%20the%20key%3F%20Like%20resetting%20the%20public%20key%20on%20that%20machine%20could%20solve%20the%20problem%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3264481%22%20slang%3D%22en-US%22%3ERe%3A%20No%20access%20ssh%20after%20the%20automatic%20update%20schedule%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3264481%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1320760%22%20target%3D%22_blank%22%3E%40pluc7%3C%2FA%3E%26nbsp%3BCan%20you%20connect%20to%20the%20Serial%20Console%20of%20the%20Linux%20VM%20through%20the%20Azure%20Portal%3F%20You'd%20still%20need%20to%20login%2C%20but%20if%20that%20works%20and%20SSH%20doesn't%20then%20you%20could%20use%20the%20console%20to%20check%20the%20sshd%20service%20is%20running.%20If%20the%20SSH%20service%20looks%20healthy%20it%20may%20indicate%20something%20has%20changed%20on%20the%20network.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222022-03-23_09-56-48.png%22%20style%3D%22width%3A%20292px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F357865i99B4A233B94FFA11%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222022-03-23_09-56-48.png%22%20alt%3D%222022-03-23_09-56-48.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi guys!

 

I have an automation account created by my client and have started scheduling automatic updates for a group of linux machines.

It was successful except in one machine, I wanted to verify the problem by connecting with azure-cli (via powershell on my local pc) with the command az ssh vm --ip 10.xxx.xxx.xxx

But nothing happens, I noticed that I can no longer connect to any of the linux machines to which I started the scheduling except two of them.

azurecli_ssh.png

I tried to reset ssh with the command az vm user reset-ssh --resource-group linux_test --ip 10.xxx.xxx.xxx, rebooted the machine and now it asks me for the password that I don't know which one it refers to since mine does not accept it .

Did the update do something to the ssh service? How can I be able to connect to this group of linux machines again?


Thank you and good day!

2 Replies

@pluc7 Can you connect to the Serial Console of the Linux VM through the Azure Portal? You'd still need to login, but if that works and SSH doesn't then you could use the console to check the sshd service is running. If the SSH service looks healthy it may indicate something has changed on the network.

2022-03-23_09-56-48.png

Could it be the key? Like resetting the public key on that machine could solve the problem?