This is no longer an issue. I think I just had some cruft in my role. On Friday, June 1, 2012 12:37:52 PM UTC-7, Val wrote: > > Now, I am not able to create a snapshot from a running instance > > *Caller:* <https://vmtest-vm1.lbl.gov:44444/#/servers//view>/DBServer > > *Message:* Cannot deliver message 'Rebundle' (message_id: > 5e7887c3-bc65-42a7-bb7c-73607ce2609b) via REST to server '23.20.196.56' > (server_id: 940fffab-2f37-4168-935e-483b2a3e5f40). Error: 0 Couldn't > connect to server; couldn't connect to host ( > http://23.20.196.56:8013/control) > > On Friday, June 1, 2012 7:27:39 AM UTC-7, Marat wrote: >> >> Then restart scalr-upd-client daemon >> >> On Friday, June 1, 2012 5:27:08 PM UTC+3, Marat wrote: >>> >>> You can set repository = latest in /etc/scalr/updclient.ini to force >>> using latest repo until new Scalr OS release with controlling interface >>> will be published. >>> >>> On Friday, June 1, 2012 5:16:02 PM UTC+3, Val wrote: >>>> >>>> I am assuming the update doesn't happend automagically because on RHEL >>>> OSes the scalr-latest.repo is not enabled. I had to enable it and perform >>>> the update. The Scalr folks need to put the fix in the scalr-delay.repo >>>> in >>>> order for the automatic update to occur. At least, that has been my >>>> experience. >>>> >>>> On Friday, June 1, 2012 5:54:02 AM UTC-7, Dale-Kurt Murray wrote: >>>>> >>>>> Marat, How do we update to the latest version? Does the update happen >>>>> on rebooting the instance or by rebuilding the role? >>>>> >>>>
-- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/scalr-discuss/-/gUQj4QAc9swJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.
