Hi Bryan,

>From the logs, I could see some below (*VNI: integer expression
expectedError: argument "VNI" is wrong) * during network configuration.
Please check your network config.

*2023-12-22 19:09:21,543 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-68:ctx-79cd030e job-215/job-687 ctx-3820f5d5)
(logid:3f700e86) Seq 3-3746431940018831724: Received:  { Ans: , MgmtId:
90520732211830, via: 3(n2ncloudmy1cp04), Ver: v1, Flags: 10, { StartAnswer,
Answer } }*

Error here:
*2023-12-22 19:09:21,548 INFO  [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-68:ctx-79cd030e job-215/job-687 ctx-3820f5d5)
(logid:3f700e86) Unable to start VM on Host
{"id":3,"name":"n2ncloudmy1cp04","type":"Routing","uuid":"a627f179-865b-49da-98af-61c0b3ff62d4"}
due to Failed to create vnet VNI:
/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh: line
173: [: VNI: integer expression expectedError: argument "VNI" is wrong: id
is
invalid/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh:
line 37: /proc/sys/net/ipv6/conf/bond1.VNI/disable_ipv6: No such file or
directoryCannot find device "bond1.VNI"Failed to create vlan VNI on pif:
bond1.*

*2023-12-22 19:09:21,550 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-68:ctx-79cd030e job-215/job-687 ctx-3820f5d5)
(logid:3f700e86) Cleaning up resources for the vm VM instance
{"id":81,"instanceName":"v-81-VM","type":"ConsoleProxy","uuid":"819c6d02-99f0-4674-bf8f-daf8417eb5fc"}
in Starting state*

*2023-12-22 19:09:21,570 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-68:ctx-79cd030e job-215/job-687 ctx-3820f5d5)
(logid:3f700e86) Seq 3-3746431940018831725: Sending  { Cmd , MgmtId:
90520732211830, via: 3(n2ncloudmy1cp04), Ver: v1, Flags: 100011,
[{"com.cloud.agent.api.StopCommand":*


Regards,
Suresh


On Wed, Dec 27, 2023 at 12:47 PM Bryan Tiang <bryantian...@hotmail.com>
wrote:

> Hi Community,
>
> We tried re-installing cloudstack and now we can’t bring up the SystemVM
> Control Proxy and SSVM.
>
> Could someone tell us what we’re missing out? Ive attached our management
> log files.
>
> Regards,
> Bryan
>

Reply via email to