Hi Steffen, Can you provide some more context about this issue? You updated Scalr to 5.11.22 from an earlier version and are now seeing a new Chef error on your Scalr deployed instances? Are these from farms that were previously configured and working without issue, or is this a new farm? Did you change your local Scalarizr agent repo version, or are you using our public Latest/Stable agent repo? A full copy of the agent logs from an impacted instance along with a full description of steps taken before encountering the reported error will be helpful.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Monday, November 28, 2016 at 7:43:03 AM UTC-7, Steffen wrote: > > Hi, > > we just installed Scalr 5.11 and scalarizr daemon is not finding chef > anymore. > > Chef version manifest is not found in following locations: > ['/opt/chef/version-manifest.json', '/opt/chef/version-manifest.txt']. Is > Chef installed? > > > chef-client: > > # dpkg -l chef > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name > Version Architecture > Description > > +++-=========================================================================-=========================================-=========================================-======================================================================================================================================================== > ii chef > 12.3.0-3ubuntu1 all > systems integration framework - clients > > > Yes this is not the chef package from chef.io, but the chef package in > Ubuntu 16.04. > Anyway around this or do we need to use the chef package from chef.io? > > 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.
