
YYYY/MM/DD HH:MM:SS ERROR:socket IOError args: (113, 'No route to host')Įrror 4 login: YYYY/MM/DD HH:MM:SS ERROR:timed out

usr/sbin/waagent:2275: DeprecationWarning: ssage has been deprecated as of Python 2.6Įrror('socket IOError ' + e.message + ' args: ' + repr(e.args)) Errors in the serial console log CentOS Linux distribution errors Error 1 Bringing up interface eth0:ĭevice eth0 does not seem to be present, delaying initialization.Įrror 2 Bringing up loopback interface: īringing up interface eth0: Device eth0 has different MAC address than expected, ignoring.Įrror 3 YYYY/MM/DD HH:MM:SS Discovered Windows Azure endpoint: #.#.#.# Specifically, you may see the following errors. The networking errors are typically logged in the serial console log. However, it ultimately cannot access the VM because of the network issue. When the issue occurs, the Secure Shell (SSH) connection that has correct permissions may start to connect to the VM. If eth0 isn't configured, the VM is not accessible over a network connection even when other tools indicate the VM is up. The primary interface on an Azure Linux virtual machine (VM) is eth0. Original product version: Virtual Machine running Linux Original KB number: 4010059 Symptoms Changed for anonymity.īy the way I am pretty much a newbie when it comes to this stuff.This article fixes an issue in which network errors prevent you from connecting to Azure Linux virtual machines. I don't know if this is relevant.Īlso "network" is not the name of my network. I have one ssh_config but no sshd_config. Now I can access the internet from this machine, but when I attempt to ssh to another machine in the network I get the message "Port 22 network is unreachable"Ĭhecking with google I found that there should be some ssh config files.

Nameserver (blah)same as in /etc/network/interfaces After struggling with Network Manager I went in and set up the files manually. I have recently installed 10.04 on an old box I have sitting around and wanted to include it in my home network.
