Reg magento in ubuntu13.04


#1

Hi,
WHen installing magento cookbook in ubuntu13.04 ,it shows repo expiry so change that and included that cookbook and also yum-fedora for fedora and yum-epel for centos image,When installing magento again it shows like this:
Current directory[/var/lib/mysql]: /var/chef-solo/cookbooks/mysql/recipes/_server_debian.rb:70:in `from_file’ INFO: Processing execute[apt-get-update-build-essentials] action run (build-essential::debian line 22) INFO: Processing package[autoconf] action install (build-essential::debian line 40) ERROR: Running exception handlersERROR: Exception handlers completeFATAL: Stacktrace dumped to /var/chef-solo/cache/chef-stacktrace.out FATAL: Chef::Exceptions::package: package[autoconf] (build-essential::debian line 40) had an error: Chef::Exceptions::package: autoconf has no candidate in the apt-cache Thanks,indra


#2

Hi Chefs,
Has anyone tried already updating old ChefDK to the one that has just been released 0.4.0? What is the appropriate process? Just install over old one or some tricks should be done afterwards? I am using workstation on windows platform.
Thank you all in advance for your valuable replies. Regards, Taras.


#3

On Tuesday 03 February 2015 11:39 AM, Indra k wrote:

Hi,

WHen installing magento cookbook in ubuntu13.04 ,it shows repo expiry
so change that and included that cookbook and also yum-fedora for
fedora and yum-epel for centos image,When installing magento again it
shows like this:

Current directory[/var/lib/mysql]:
/var/chef-solo/cookbooks/mysql/recipes/_server_debian.rb:70:in `from_file’
INFO: Processing execute[apt-get-update-build-essentials] action run
(build-essential::debian line 22)
INFO: Processing package[autoconf] action install
(build-essential::debian line 40)
ERROR: Running exception handlers
ERROR: Exception handlers complete
FATAL: Stacktrace dumped to /var/chef-solo/cache/chef-stacktrace.out
FATAL: Chef::Exceptions::package: package[autoconf]
(build-essential::debian line 40) had an error:
Chef::Exceptions::package: autoconf has no candidate in the apt-cache

I ve also tried in instance like this:

$apt-get update

Reading package lists… Done

root@vm:/etc/apt# apt-get install autoconf

Reading package lists… Done
Building dependency tree
Reading state information… Done
Package autoconf is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘autoconf’ has no installation candidate

Thanks,
indra


#4

I believe you should be able to install it over the old copy. But if this is causing issues you can follow https://docs.chef.io/install_dk.html#uninstall https://docs.chef.io/install_dk.html#uninstall for instructions to completely uninstall and then re-install.

-T

On Feb 3, 2015, at 2:46 AM, klum_tz@ukr.net wrote:

Hi Chefs,

Has anyone tried already updating old ChefDK to the one that has just been released 0.4.0?
What is the appropriate process? Just install over old one or some tricks should be done afterwards?
I am using workstation on windows platform.

Thank you all in advance for your valuable replies.
Regards,
Taras.


#5

You may need to rm -rf $HOME/.chefdk to clear out local gems - if you run
into oddball issues.

P.

On Tue, Feb 3, 2015 at 11:45 AM, Tyler Ball tball@chef.io wrote:

I believe you should be able to install it over the old copy. But if this
is causing issues you can follow
https://docs.chef.io/install_dk.html#uninstall for instructions to
completely uninstall and then re-install.

-T

On Feb 3, 2015, at 2:46 AM, klum_tz@ukr.net wrote:

Hi Chefs,

Has anyone tried already updating old ChefDK to the one that has just
been released 0.4.0?
What is the appropriate process? Just install over old one or some tricks
should be done afterwards?
I am using workstation on windows platform.

Thank you all in advance for your valuable replies.
Regards,
Taras.

Peter Burkholder — Customer Success Engineer

Availability: no travel/OOO scheduled

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef


#6

I would set it aside, not delete it, in order to preserve the list of previously activated gems. The “oddball issues” from deleting something that worked for six months, and not being able to recover it without trying to deduce what components you activated with what versions in what order can create configuration issues.

Nico Kadel-Garcia
Lead DevOps Engineer
nkadel@skyhookwireless.commailto:nkadel@skyhookwireless.com

From: Peter Burkholder [mailto:pburkholder@chef.io]
Sent: Tuesday, February 03, 2015 2:41 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Re: ChefDK 0.4.0. Updating from old ChefDK (0.3.6)

You may need to rm -rf $HOME/.chefdk to clear out local gems - if you run into oddball issues.

P.

On Tue, Feb 3, 2015 at 11:45 AM, Tyler Ball <tball@chef.iomailto:tball@chef.io> wrote:
I believe you should be able to install it over the old copy. But if this is causing issues you can follow https://docs.chef.io/install_dk.html#uninstall for instructions to completely uninstall and then re-install.

-T

On Feb 3, 2015, at 2:46 AM, klum_tz@ukr.netmailto:klum_tz@ukr.net wrote:

Hi Chefs,

Has anyone tried already updating old ChefDK to the one that has just been released 0.4.0?
What is the appropriate process? Just install over old one or some tricks should be done afterwards?
I am using workstation on windows platform.

Thank you all in advance for your valuable replies.
Regards,
Taras.

Peter Burkholder — Customer Success Engineer

Availability: no travel/OOO scheduled

301-204-5767tel:301-204-5767pburkholder@chef.iomailto:pburkholder@chef.io – my: Linkedinhttp://www.linkedin.com/in/pburkholder Twitterhttp://www.twitter.com/pburkholder Calhttps://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEKendar

CHEF

CHEF.IOhttp://www.chef.io/

TM

chef.iohttp://www.chef.io/ Bloghttp://www.chef.io/blog/ Facebookhttps://www.facebook.com/getchefdotcom Twitterhttps://twitter.com/chef Youtubehttps://www.youtube.com/getchef


#7

You are so right! I didn’t even delete mine, then l go off and 'recommend’
that action. Thanks for correcting that!

-Peter

On Wed, Feb 4, 2015 at 9:23 PM, Nico Kadel-Garcia <
nkadel@skyhookwireless.com> wrote:

I would set it aside, not delete it, in order to preserve the list of
previously activated gems. The “oddball issues” from deleting something
that worked for six months, and not being able to recover it without trying
to deduce what components you activated with what versions in what order
can create configuration issues.

Nico Kadel-Garcia

Lead DevOps Engineer

nkadel@skyhookwireless.com

From: Peter Burkholder [mailto:pburkholder@chef.io]
Sent: Tuesday, February 03, 2015 2:41 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Re: ChefDK 0.4.0. Updating from old ChefDK (0.3.6)

You may need to rm -rf $HOME/.chefdk to clear out local gems - if you run
into oddball issues.

P.

On Tue, Feb 3, 2015 at 11:45 AM, Tyler Ball tball@chef.io wrote:

I believe you should be able to install it over the old copy. But if this
is causing issues you can follow
https://docs.chef.io/install_dk.html#uninstall for instructions to
completely uninstall and then re-install.

-T

On Feb 3, 2015, at 2:46 AM, klum_tz@ukr.net wrote:

Hi Chefs,

Has anyone tried already updating old ChefDK to the one that has just been
released 0.4.0?

What is the appropriate process? Just install over old one or some tricks
should be done afterwards?

I am using workstation on windows platform.

Thank you all in advance for your valuable replies.

Regards,

Taras.

Peter Burkholder — Customer Success Engineer

Availability: no travel/OOO scheduled

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/
Facebook https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

Peter Burkholder — Customer Success Engineer

Availability: no travel/OOO scheduled

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef


#8

In general you should not need to delete gems from ~/.chefdk/gem, though there was one upstream bug that made this necessary. For more information see this mailing list post: http://lists.opscode.com/sympa/arc/chef/2014-08/msg00414.html and this bug report https://github.com/chef/chef-dk/issues/146 (and other bugs linked from there).

So if you’re upgrading from ChefDK 0.2.1 or later to latest, and you experience “wonkiness” that requires you to nuke ~/.chefdk/gem, please file a bug report so we can figure out what it is and improve the experience for everyone in the future.

Thanks,


Daniel DeLeo

On Thursday, February 5, 2015 at 10:18 AM, Peter Burkholder wrote:

You are so right! I didn’t even delete mine, then l go off and ‘recommend’ that action. Thanks for correcting that!

-Peter

On Wed, Feb 4, 2015 at 9:23 PM, Nico Kadel-Garcia <nkadel@skyhookwireless.com (mailto:nkadel@skyhookwireless.com)> wrote:

I would set it aside, not delete it, in order to preserve the list of previously activated gems. The “oddball issues” from deleting something that worked for six months, and not being able to recover it without trying to deduce what components you activated with what versions in what order can create configuration issues.

Nico Kadel-Garcia
Lead DevOps Engineer
nkadel@skyhookwireless.com (mailto:nkadel@skyhookwireless.com)

From: Peter Burkholder [mailto:pburkholder@chef.io]
Sent: Tuesday, February 03, 2015 2:41 PM
To: chef@lists.opscode.com (mailto:chef@lists.opscode.com)
Subject: [chef] Re: Re: ChefDK 0.4.0. Updating from old ChefDK (0.3.6)

You may need to rm -rf $HOME/.chefdk to clear out local gems - if you run into oddball issues.

P.

On Tue, Feb 3, 2015 at 11:45 AM, Tyler Ball <tball@chef.io (mailto:tball@chef.io)> wrote:

I believe you should be able to install it over the old copy. But if this is causing issues you can follow https://docs.chef.io/install_dk.html#uninstall for instructions to completely uninstall and then re-install.

-T

On Feb 3, 2015, at 2:46 AM, klum_tz@ukr.net (mailto:klum_tz@ukr.net) wrote:

Hi Chefs,

Has anyone tried already updating old ChefDK to the one that has just been released 0.4.0?

What is the appropriate process? Just install over old one or some tricks should be done afterwards?

I am using workstation on windows platform.

Thank you all in advance for your valuable replies.

Regards,

Taras.

Peter Burkholder — Customer Success Engineer

Availability: no travel/OOO scheduled

301-204-5767 (tel:301-204-5767) – pburkholder@chef.io (mailto:pburkholder@chef.io) – my: Linkedin (http://www.linkedin.com/in/pburkholder) Twitter (http://www.twitter.com/pburkholder) Cal (https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK)endar

CHEF

CHEF.IO (http://www.chef.io/)

TM

chef.io (http://www.chef.io/) Blog (http://www.chef.io/blog/) Facebook (https://www.facebook.com/getchefdotcom) Twitter (https://twitter.com/chef) Youtube (https://www.youtube.com/getchef)

Peter Burkholder — Customer Success Engineer

Availability: no travel/OOO scheduled

301-204-5767 – pburkholder@chef.io (mailto:pburkholder@chef.io) – my: Linkedin (http://www.linkedin.com/in/pburkholder) Twitter (http://www.twitter.com/pburkholder) Cal (https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK)endar

CHEF

CHEF.IO (http://www.chef.io/)

TM

chef.io (http://www.chef.io/) Blog (http://www.chef.io/blog/) Facebook (https://www.facebook.com/getchefdotcom) Twitter (https://twitter.com/chef) Youtube (https://www.youtube.com/getchef)