Hi Marcus, is it safe to destroy VR, on some troubleshooting guides it tells us to never destroy VR? one time i destroyed vr and it took new ip from guest ip network, so is it safe to destroy VR? whats your opinions ?
Thanks 2016-05-31 17:38 GMT+03:00 Marc-Andre Jutras <[email protected]>: > Hey ! > > personally, I would recommend to run everything on UTC but it's up to > you... > > If everything is in ntp-sync, maybe an old api call was waiting on the VR > to get consumed by ACS... Just to be sure, destroy / re-create the VR and > check if you're still seeing the same warning message... > > also, check on your kvma16 host if there's any errors there... just in > case ;) > > best way to destroy / re-create rapidly a VR : > > 1- delete / destroy / expunge the VR, > > 2- spin up a new VM on the same network > > 3- ACS will detect the missing VR and will re-create it right away... > > Marcus > > > > On 2016-05-31 2:35 AM, Semih Tolga DEMİR wrote: > >> Hi; >> >> All management servers and hypervizors are in ntp time sync. >> >> My management and hypervisor servers are using my local timezone(UTC+5) >> but >> they are synced with ntp but you know systemvm’s are using default UTC >> timezone, do i need to set management and hypervisors server to UTC for >> ACS >> to work successfully? >> >> Thanks >> >> Tolga >> >> >> 2016-05-30 21:49 GMT+03:00 Marc-Andre Jutras <[email protected]>: >> >> Make sure NTP is configured and in sync everywhere... ( that's include >>> your management server, hypervisor, etc... ) >>> >>> >>> >>> On 2016-05-30 7:51 AM, Semih Tolga DEMİR wrote: >>> >>> Hi, >>>> >>>> I see some different logs in my management server. I do not understand >>>> what >>>> is the meaning of this [ALERT] , is it bug? Can i ignore that? >>>> >>>> The [ALERT] logs are below. >>>> >>>> >>>> 2016-05-30 09:47:45,451 DEBUG [c.c.a.t.Request] >>>> (AgentManager-Handler-10:null) (logid:) Seq 10-1235393672783119940: >>>> Processing: { Ans: , MgmtId: 345050167520, via: 10, Ver: v1, Flags: 10, >>>> [{"com.cloud.agent.api.GetRouterAlertsAnswer":{"alerts":["2016-05-24 >>>> 17:06:03,446 [ALERT] [dnsmasq] The process detected as >>>> running"],"timeStamp":"2016-05-24 17:06:03","result":true,"wait":0}}] } >>>> >>>> 2016-05-30 09:47:45,451 DEBUG [c.c.a.t.Request] >>>> (RouterStatusMonitor-1:ctx-972488b8) (logid:0e7a028f) Seq >>>> 10-1235393672783119940: Received: { Ans: , MgmtId: 345050167520, via: >>>> 10(kvma16), Ver: v1, Flags: 10, { GetRouterAlertsAnswer } } >>>> >>>> 2016-05-30 09:47:45,451 WARN >>>> [c.c.n.r.VirtualNetworkApplianceManagerImpl] >>>> (RouterStatusMonitor-1:ctx-972488b8) (logid:0e7a028f) Invalid last alert >>>> timestamp received while collecting alerts from router: r-91-VM >>>> >>>> 2016-05-30 09:47:45,490 DEBUG [c.c.a.t.Request] >>>> (AgentManager-Handler-1:null) (logid:) Seq 10-1235393672783119941: >>>> Processing: { Ans: , MgmtId: 345050167520, via: 10, Ver: v1, Flags: 10, >>>> [{"com.cloud.agent.api.GetRouterAlertsAnswer":{"alerts":["2016-05-24 >>>> 17:06:03,446 [ALERT] [dnsmasq] The process detected as >>>> running"],"timeStamp":"2016-05-24 17:06:03","result":true,"wait":0}}] } >>>> >>>> 2016-05-30 09:47:45,490 DEBUG [c.c.a.t.Request] >>>> (RouterStatusMonitor-1:ctx-1ac9d1dd) (logid:b308a937) Seq >>>> 10-1235393672783119941: Received: { Ans: , MgmtId: 345050167520, via: >>>> 10(kvma16), Ver: v1, Flags: 10, { GetRouterAlertsAnswer } } >>>> >>>> >>>> Thanks, >>>> >>>> >>>> >
