Hi all!
First, I would like to clarify that I'm new on VMware platform and sorry if I ask a question that has an easy resolution, but reading all threads and solutions I could not solve my issue.
I'm trying to convert a Linux centOS 7 physical machine to a virtual machine in a VMware Server Esxi 6.7.0. To perform this task I'm using vCenter Converter Standalone 6.2.0. I set all wizard options, job starts but at 3% it fails with error:
FAILED: A general system error occurred: connect (`10.240.107.11'): Network is unreachable connect (`10.240.107.11'): Network is unreachable connect (`10.240.107.11'): Network is unreachable connect (`10.240.107.11'):
Network is unreachable Network error. Host 10.240.107.11 key can't be retrieved. (return code 2)
I have performed some tips given in another discussions, such as:
– SSH configuration is allowing root to access the system remotely from port 22
# grep Root /etc/ssh/sshd_config
PermitRootLogin yes
# the setting of "PermitRootLogin without-password".
– IPtables allow connection on port 22
# iptables -L | grep ssh
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh ctstate NEW
– You are running Converter version 5.5.1 or greater (there is a known issue with older version that aren’t supporting DSA keys)
As I said before, I'm using vCenter Converter Standalone 6.2.0
– Add ALL:ALL parameter to “hosts.allow” parameter.
# cat /etc/hosts.allow
#
# hosts.allow This file contains access rules which are used to
# allow or deny connections to network services that
# either use the tcp_wrappers library or that have been
# started through a tcp_wrappers-enabled xinetd.
#
# See 'man 5 hosts_options' and 'man 5 hosts_access'
# for information on rule syntax.
# See 'man tcpd' for information on tcp_wrappers
ALL:ALL
– Check DNS suffix
I'm doing the process using ip addresses... I'm not using names.
- Check network configuration
Linux, VMware server and machine with Converter have the same ip range and same netmask
- I'm running Converter as Administrator
This is an excerpt vmware-converter-server-4.log:
2018-07-18T08:41:40.175-03:00 info vmware-converter-server[05156] [Originator@6876 sub=Default] [task,338] [task-16] -- BEGIN -- Convert
2018-07-18T08:41:40.191-03:00 info vmware-converter-server[05156] [Originator@6876 sub=Default] [taskSpec,620] [task-16] [TaskMap] task-16:task-13
2018-07-18T08:41:40.199-03:00 info vmware-converter-server[08704] [Originator@6876 sub=Default] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded
2018-07-18T08:44:18.908-03:00 error vmware-converter-server[05156] [Originator@6876 sub=Default] [task,350] [LRO] Unexpected Exception: vmodl.fault.SystemError
2018-07-18T08:44:18.909-03:00 info vmware-converter-server[05156] [Originator@6876 sub=Default] [task,379] [task-16] -- ERROR -- Convert: vmodl.fault.SystemError
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> reason = "connect (`10.240.107.11'): Network is unreachable
--> connect (`10.240.107.11'): Network is unreachable
--> connect (`10.240.107.11'): Network is unreachable
--> connect (`10.240.107.11'): Network is unreachable
--> Network error. Host 10.240.107.11 key can't be retrieved.
--> (return code 2)",
--> msg = ""
--> }
2018-07-18T08:44:18.909-03:00 info vmware-converter-server[05156] [Originator@6876 sub=Default] [diagnosticManager,265] Retrieved taskInfo for "converter.task.Task:task-16" mapping it to "converter.task.Task:task-16".
2018-07-18T08:44:18.909-03:00 info vmware-converter-server[05156] [Originator@6876 sub=Default] [diagnosticManager,305] The task with id = "task-16" was found to be a "recent" task.
2018-07-18T08:44:18.910-03:00 info vmware-converter-server[05156] [Originator@6876 sub=Default] [diagnosticManager,319] No existing log bundle found for task with id = "task-16". The task is still "recent" so a log bundle will now be generated for it.
2018-07-18T08:44:18.910-03:00 info vmware-converter-server[05156] [Originator@6876 sub=Default] [diagnosticManager,1097] Retrieving task related diagnostics for server task with id = "task-16".
2018-07-18T08:44:18.992-03:00 info vmware-converter-server[06108] [Originator@6876 sub=Default] Run 0 of job "job-16" finished with an error. -- struct Converter::Server::Job::JobExecutor::SchedulerUpdateSpec __thiscall Converter::Server::Conversion::ConversionJobExecutorImpl::UpdateJob(class Converter::Server::Job::InternalJob &,bool,const class Converter::Server::Scheduler::SchedulerItemStatistics &,const class Converter::Task::TaskInfo &) ("d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/conversion/conversionJobExecutorImpl.cpp:405")
2018-07-18T08:44:19.138-03:00 info vmware-converter-server[06108] [Originator@6876 sub=Default] Suspended 1 scheduler items for job (job-16) -- void __thiscall Converter::Server::Job::JobProcessorImpl::SuspendJobAux(const class Converter::Server::Job::InternalJob &,class Converter::VdbConnection &) ("d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:829")
Any clue with be apprecieated!
Thank you in advance
Best Regards
Hi
This error means the helper (running on the newly created destination VM) can not reach the source machine. Have a look at the diagrams here Remote Hot Cloning of Powered On Source Machines That Are Running Linux, it will give you an idea of the topology.
The connection needs to be done from the virtual network where the VM is created, not the ESXi management connection.
The error you mention should appear in the helper's log, not in the converter server's one. It being there too might mean random network dropouts (if there is just no connectivity from converter server, you wouldn't be able to start the conversion at all).
HTH,
Plamen
What IP is at 10.240.107.11? Is this your Linux server? Can you ping from your Linux server to the management interface of your ESXi host?
Hi, yes I can... 10.240.107.11 is the ip of Linux. My Esxi's manager interface has the ip 10.240.107.49, both with 255.255.0.0, and I can ping from linux to Esxi:
# ifconfig eno1
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.240.107.11 netmask 255.255.0.0 broadcast 10.240.255.255
...
#
# ping 10.240.107.49
PING 10.240.107.49 (10.240.107.49) 56(84) bytes of data.
64 bytes from 10.240.107.49: icmp_seq=1 ttl=64 time=0.280 ms
64 bytes from 10.240.107.49: icmp_seq=2 ttl=64 time=0.375 ms
64 bytes from 10.240.107.49: icmp_seq=3 ttl=64 time=0.264 ms
64 bytes from 10.240.107.49: icmp_seq=4 ttl=64 time=0.216 ms
64 bytes from 10.240.107.49: icmp_seq=5 ttl=64 time=0.260 ms
^C
--- 10.240.107.49 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.216/0.279/0.375/0.052 ms
#
Additionally, I have made a ping test from Esxi to Linux and it passed ok.
Best regards and thank you for take your time on this.
You have a /16 mask? Are you certain it's not supposed to be a /24 given your IP similarities?
Yes, it's ok because this Linux is the server of an application that serves in a big network /16.
And you can reach your Linux server from the workstation where you're launching Converter? From the error message, it appears you have basic network connectivity issues.
Hi
This error means the helper (running on the newly created destination VM) can not reach the source machine. Have a look at the diagrams here Remote Hot Cloning of Powered On Source Machines That Are Running Linux, it will give you an idea of the topology.
The connection needs to be done from the virtual network where the VM is created, not the ESXi management connection.
The error you mention should appear in the helper's log, not in the converter server's one. It being there too might mean random network dropouts (if there is just no connectivity from converter server, you wouldn't be able to start the conversion at all).
HTH,
Plamen
daphnissov, yes, I can reach them...
C:\Users\Fernando>ping 10.240.107.11
Haciendo ping a 10.240.107.11 con 32 bytes de datos:
Respuesta desde 10.240.107.11: bytes=32 tiempo<1m TTL=64
Respuesta desde 10.240.107.11: bytes=32 tiempo<1m TTL=64
Respuesta desde 10.240.107.11: bytes=32 tiempo<1m TTL=64
Respuesta desde 10.240.107.11: bytes=32 tiempo<1m TTL=64
Estadísticas de ping para 10.240.107.11:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 0ms, Máximo = 0ms, Media = 0ms
C:\Users\Fernando>ping 10.240.107.49
Haciendo ping a 10.240.107.49 con 32 bytes de datos:
Respuesta desde 10.240.107.49: bytes=32 tiempo<1m TTL=64
Respuesta desde 10.240.107.49: bytes=32 tiempo<1m TTL=64
Respuesta desde 10.240.107.49: bytes=32 tiempo<1m TTL=64
Respuesta desde 10.240.107.49: bytes=32 tiempo<1m TTL=64
Estadísticas de ping para 10.240.107.49:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 0ms, Máximo = 0ms, Media = 0ms
Plamen, thank you for your answer. I'll read the link and try to implement your recommendation...
I'll let you know if it worked.
Best regards!
Plamen, thank you for your answer. I didn't know about "Helper"... I assigned an IP address to the helper in the option's section of the conversor wizard and it worked perfectly.
Thank you again for the tip.
Best regards
You are welcome
