Hi Vihar and all, Thanks, managed to resolve this problem. After checking agent.log, I found out that the /var partition on the VR is full, due to verbose log I enabled when troubleshooting the DNS service issue on another thread.
I disabled back the debugging and delete the log file which is taking up lot of space, and the problem is resolved. Thank you. On Tue, Jul 22, 2014 at 11:40 AM, Vihar <vih1...@gmail.com> wrote: > Hi Indra, > > I would like to know if the VR is newly created or it was existing one? > > It seems that VM are not getting Username and password. Could you check if > you are able to access the VR from host with 3922 port and 8250. > > If not there is no communication between the host and the VR. > > Regards > Vihar K > On Jul 22, 2014 8:59 AM, "Indra Pramana" <in...@sg.or.id> wrote: > > > Dear all, > > > > Suddenly I am not able to create new VMs on my zone. The error message I > > found on management-server.log: > > > > 2014-07-22 11:25:51,632 INFO [cloud.vm.VirtualMachineManagerImpl] > > (Job-Executor-3:job-17146 = [ b780cd9c-2d0b-499f-b396-269064995e30 ]) > > Unable to contact resource. > > com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:6] > > is unreachable: Unable to apply userdata and password entry on router > > > > Looks like another issue with the VR? I have tried to stop and start > > dnsmasq service on the VR but problem still persists. > > > > Any advice is greatly appreciated. > > > > Thank you. > > >
