Gilu 0 Posted January 22, 2018 Share Posted January 22, 2018 Hi, im trying to create virtual machine om my xpenology installation but every time im running wizard i got something like "Cannot create the cluster" messag. In /var/log/messages i have following output: 2018-01-22T13:38:01+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create_SYNO.CCC.Cluster_1_create[31376]: ccc/host.cpp:1991 Start to create cluster 2018-01-22T13:38:01+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create_SYNO.CCC.Cluster_1_create[31376]: ccc/host.cpp:1775 Start check before host init or modify etcd ip 2018-01-22T13:38:01+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:2002 OVS is running, skip register OVS 2018-01-22T13:38:01+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:2014 Cluster init start 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:2688 ccc/host.cpp:CCCLocalhostCleanup:1366: Start to pause all services 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synovncrelayd ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synohostcmdd ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synohostcommd ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synocccd ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-libvirtd ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-etcd_hyper ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-etcd ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synocccstated ...[1] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synocccstated ...[0] 2018-01-22T13:38:02+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-etcd ...[0] 2018-01-22T13:38:02+01:00 Karmelita_NAS synocccstated: synocccstated.cpp:101 start with empty data 2018-01-22T13:38:04+01:00 Karmelita_NAS dhclient: send_packet6: Network is unreachable 2018-01-22T13:38:04+01:00 Karmelita_NAS dhclient: dhc6: send_packet6() sent -1 of 32 bytes 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/utils.cpp:190 Failed to get MyDS Account. 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:537 Start to init host with id: f1588327-af5e-4ee1-ad4b-110ba2d627da 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/utils.cpp:173 Failed to get first mac of DS. 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:568 Failed to get the first mac address. 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:2078 Failed to add host info to dashboard 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:2187 Rollback create cluster 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:2688 ccc/host.cpp:CCCDBClusterCreate:2192: Start to pause all services 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synovncrelayd ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synohostcmdd ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synohostcommd ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synocccd ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-libvirtd ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-etcd_hyper ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-etcd ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS [240351.908278] init: pkg-etcd main process (31415) killed by TERM signal 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/service.cpp:251 service pkg-synocccstated ...[1] 2018-01-22T13:38:11+01:00 Karmelita_NAS [240352.071895] init: pkg-synocccstated main process (31408) killed by TERM signal 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:1873 OVS is not enabled by virtualization, skip unregister 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: Cluster/cluster.cpp:291 Failed to create cluster, [401] 2018-01-22T13:38:11+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: Cluster/Cluster.cpp:64 Bad response [{"error":{"code":401},"httpd_restart":false,"success":false}]/ request [{"addr":"127.0.0.1","api":"SYNO.CCC.Cluster","method":"create","version":1,"volume_paths":["/volume1"]}] What could be the problem? The cluster creation stops just after this screen: And it appears no matter if i turn VSwitch on or off. Any ideas? Quote Link to post Share on other sites
korotkov 0 Posted January 28, 2018 Share Posted January 28, 2018 I got the same Quote Link to post Share on other sites
Polanskiman 399 Posted January 29, 2018 Share Posted January 29, 2018 On 1/22/2018 at 7:58 PM, Gilu said: 2018-01-22T13:38:04+01:00 Karmelita_NAS dhclient: send_packet6: Network is unreachable 2018-01-22T13:38:04+01:00 Karmelita_NAS dhclient: dhc6: send_packet6() sent -1 of 32 bytes 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/utils.cpp:190 Failed to get MyDS Account. 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:537 Start to init host with id: f1588327-af5e-4ee1-ad4b-110ba2d627da 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/utils.cpp:173 Failed to get first mac of DS. 2018-01-22T13:38:10+01:00 Karmelita_NAS synoscgi_SYNO.Virtualization.Cluster_1_create[31376]: ccc/host.cpp:568 Failed to get the first mac The above logs are the ones of interest I think. DSM seems to be checking if you have a DS Account (i.e. a valid Serial number) and also checks for a MAC address. I can't say for sure but this look like Synology is using serial and mac validity prior creating the cluster. Maybe I'm wrong so if anyone want to chime in please do so. Quote Link to post Share on other sites
Benoire 10 Posted March 31, 2018 Share Posted March 31, 2018 Did anyone resolve this? I'm moving from esxi hosted to baremetal but would like VMM to enable local hosting of certain VMs that are integral to the safe shutdown of my homelab... I'm just playing with this and I'm getting teh same outputs; that it fails to get the first MAC. I was using a generated MAC for the four NICs, but should I use the actual MAC of the quad 1GBe network card? Do I need a corresponding serial and if so, how do you generate it based on the MAC rather than the other way around? Thanks! Chris Quote Link to post Share on other sites
Benoire 10 Posted March 31, 2018 Share Posted March 31, 2018 So I changed the mac addresses to the real mac of the NICs and VMM now works fine. 1 Quote Link to post Share on other sites
esteban0506 1 Posted November 30, 2020 Share Posted November 30, 2020 where did you do that ? Quote Link to post Share on other sites
bearcat 79 Posted December 3, 2020 Share Posted December 3, 2020 @esteban0506 My first guess would be in the "grub.cfg" on the bootloader device. Quote Link to post Share on other sites
esteban0506 1 Posted December 3, 2020 Share Posted December 3, 2020 it works ! i create again my boot keys, with a new serial number and a new mac adresse Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.