Hi Steffen, Typically Scalr will only terminate running instances when autoscaling down, or when the cloud platform reports the instance as failed (or missing, in some cases). Take a look at the System Log tab in the Scalr UI and /opt/scalr-server/var/log/service/*.log for more details about the termination process related to the servers in question. This will give us more information about why Scalr is terminating the instance.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Friday, January 6, 2017 at 8:55:43 AM UTC-7, Steffen wrote: > > Hi, > > we are running a self hosted Scalr 5.11.22 with Openstack Mitaka and Ceph. > We had a ceph problem, but vms are running, but when we are rebooting them > they get removed due to a ceph problem. That is expected. > > The problem is that Scalr "terminated" the instance and thats not what I > expected, because we can restore the vm image in ceph. > > Is that an expected behavior from Scalr or can we configure this somehow? > > Many Thanks > > Steffen > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
