cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hanumant borwandkar <hanumant.borwand...@gmail.com>
Subject Re: related to CLOUDSTACK-10310 Fix KVM reboot on storage issue need workaround
Date Sat, 02 Jun 2018 08:25:23 GMT
Hi,

We are using NFS as primary storage shared across 8 compute hosts

Will share agent log of affected computes

Is it possible to downgrade 4.9 to 4.8

Regards,
Hanumant

On 17-May-2018 11:17 am, "ilya musayev" <ilya.mailing.lists@gmail.com>
wrote:

> We maybe missing a bit of context here - are you using NFS as shared
> storage in the cluster?
>
> If so - are you certain you aren’t loosing connectivity to NFS primary
> storage?
>
> Please upload the agent.log to pastebin or similar site and share the link.
>
>
>
> On Tue, May 15, 2018 at 3:13 AM hanumant borwandkar <
> hanumant.borwandkar@gmail.com> wrote:
>
> > Hi,
> >
> > We are using cloudstack inhouse with the version
> >
> > cloudstack-common-4.9.2.0-1.el7.centos.x86_64
> > cloudstack-agent-4.9.2.0-1.el7.centos.x86_64
> >
> > But unfortunately sometime or after every few day compute host getting
> > rebooted by cloudstack-agent and all VM running on that compute get
> > affected.
> >
> > It seems that I m facing issue related to* CLOUDSTACK-10310 Fix KVM
> reboot
> > on storage issue.*
> >
> > I tried to modify
> > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh
> > as per github follows
> >
> > *  /usr/bin/logger -t heartbeat "kvmheartbeat.sh stopped cloudstack-agent
> > because it was unable to write the heartbeat to the storage."*
> > *  sync &*
> > *  sleep 5*
> > *  #echo b > /proc/sysrq-trigger*
> > * service cloudstack-agent stop*
> >
> > But no improvement still compute getting rebooted .
> >
> > Can someone able to provide workaround or fix for this issue
> >
> > Regards,
> > Hanumant Borwandkar
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message