Magento is not working on AWS-Linux templates getting error


#1

Ohai!

I tried to deploy magento [
https://supermarket.getchef.com/cookbooks/magento] on aws Linux template
getting following error.

Recipe: magento::default

  • user[magento] action create
    • create user user[magento]

Recipe: php-fpm::repository

  • yum_repository[remi] action addRecipe:

  • template[/etc/yum.repos.d/remi.repo] action create

    • create new file /etc/yum.repos.d/remi.repo
    • update content in file /etc/yum.repos.d/remi.repo from none to 455d89
      — /etc/yum.repos.d/remi.repo 2014-07-11 07:20:49.943908715
      +0000
      +++ /tmp/chef-rendered-template20140711-7615-181biix 2014-07-11
      07:20:49.947908716 +0000
      @@ -1 +1,12 @@
      +# This file was generated by Chef
      +# Do NOT modify this file by hand.
      +
      +[remi]
      +name=Remi
      +baseurl=
      http://rpms.famillecollet.com/enterprise/$releasever/remi/$basearch/
      +enabled=1
      +gpgcheck=1
      +gpgkey=http://rpms.famillecollet.com/RPM-GPG-KEY-remi
      +mirrorlist=
      http://rpms.famillecollet.com/enterprise/$releasever/remi/mirror
      +sslverify=1
    • change mode from ‘’ to ‘0644’
  • execute[yum-makecache-remi] action run
    ================================================================================
    Error executing action run on resource ‘execute[yum-makecache-remi]’
    ================================================================================

Mixlib::ShellOut::ShellCommandFailed

Expected process to exit with [0], but received ‘1’
---- Begin output of yum -q makecache --disablerepo=* --enablerepo=remi ----
STDOUT: Could not retrieve mirrorlist
http://rpms.famillecollet.com/enterprise/2014.03/remi/mirror error was
14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
STDERR:
http://rpms.famillecollet.com/enterprise/2014.03/remi/x86_64/repodata/repomd.xml:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found"
Trying other mirror.

One of the configured repositories failed (Remi),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the

problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a

working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will

then
just ignore the repository until you permanently enable it again or
use
–enablerepo for temporary usage:

        yum-config-manager --disable remi

 4. Configure the failing repository to be skipped, if it is

unavailable.
Note that yum will try to contact the repo. when it runs most
commands,
so will have to try and fail each time (and thus. yum will be be
much
slower). If it is a very temporary problem though, this is often a
nice
compromise:

        yum-config-manager --save --setopt=remi.skip_if_unavailable=true

failure: repodata/repomd.xml from remi: [Errno 256] No more mirrors to try.
---- End output of yum -q makecache --disablerepo=* --enablerepo=remi ----
Ran yum -q makecache --disablerepo=* --enablerepo=remi returned 1

Resource Declaration:

In /var/chef/cookbooks/yum/providers/repository.rb

53: execute “yum-makecache-#{new_resource.repositoryid}” do
54: command "yum -q makecache --disablerepo=*
–enablerepo=#{new_resource.repositoryid}"
55: action :nothing
56: end
57:

Compiled Resource:

Declared in /var/chef/cookbooks/yum/providers/repository.rb:53:in `block

in class_from_file’

execute(“yum-makecache-remi”) do
action [:nothing]
retries 0
retry_delay 2
guard_interpreter :default
command "yum -q makecache --disablerepo=* --enablerepo=remi"
backup 5
returns 0
cookbook_name :"php-fpm"
end

================================================================================
Error executing action add on resource ‘yum_repository[remi]’

Regards
Venky


#2

Magento is not working on Ubuntu-Trusty-14.04LTS templates getting error

Recipe: magento::default

  • package[php5-cli] action upgrade

    • upgrade package php5-cli from uninstalled to 5.5.9+dfsg-1ubuntu4.3
  • package[php5-common] action upgrade (up to date)

  • package[php5-curl] action upgrade

    • upgrade package php5-curl from uninstalled to 5.5.9+dfsg-1ubuntu4.3
  • package[php5-gd] action upgrade

    • upgrade package php5-gd from uninstalled to 5.5.9+dfsg-1ubuntu4.3
  • package[php5-mcrypt] action upgrade

    • upgrade package php5-mcrypt from uninstalled to 5.4.6-0ubuntu5
  • package[php5-mysql] action upgrade

    • upgrade package php5-mysql from uninstalled to 5.5.9+dfsg-1ubuntu4.3
  • package[php-pear] action upgrade

    • upgrade package php-pear from uninstalled to 5.5.9+dfsg-1ubuntu4.3
  • package[php-apc] action upgrade

    • upgrade package php-apc from uninstalled to 4.0.2-2build1
  • bash[Tweak CLI php.ini file] action run

    • execute “bash” “/tmp/chef-script20140711-11259-x7afi”
  • bash[Tweak apc.ini file] action run
    ================================================================================
    Error executing action run on resource ‘bash[Tweak apc.ini file]’
    ================================================================================

Mixlib::ShellOut::ShellCommandFailed

Expected process to exit with [0], but received ‘1’
---- Begin output of “bash” “/tmp/chef-script20140711-11259-1194mty” ----
STDOUT:
STDERR:
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout/unix.rb:147:in
chdir': No such file or directory - /etc/php5/conf.d (Errno::ENOENT) from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout/unix.rb:147:inset_cwd’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout/unix.rb:317:in
block in fork_subprocess' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout/unix.rb:300:infork’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout/unix.rb:300:in
fork_subprocess' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout/unix.rb:52:inrun_command’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout.rb:227:in
run_command' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/mixin/shell_out.rb:37:inshell_out’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/mixin/shell_out.rb:42:in
shell_out!' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/provider/execute.rb:60:inblock in action_run’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/mixin/why_run.rb:52:in
call' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/mixin/why_run.rb:52:inadd_action’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/provider.rb:155:in
converge_by' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/provider/execute.rb:59:inaction_run’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/provider/script.rb:38:in
action_run' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/provider.rb:120:inrun_action’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource.rb:637:in
run_action' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/runner.rb:49:inrun_action’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/runner.rb:81:in
block (2 levels) in converge' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/runner.rb:81:ineach’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/runner.rb:81:in
block in converge' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource_collection.rb:98:inblock in execute_each_resource’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource_collection/stepable_iterator.rb:116:in
call' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource_collection/stepable_iterator.rb:116:incall_iterator_block’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource_collection/stepable_iterator.rb:85:in
step' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource_collection/stepable_iterator.rb:104:initerate’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource_collection/stepable_iterator.rb:55:in
each_with_index' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/resource_collection.rb:96:inexecute_each_resource’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/runner.rb:80:in
converge' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/client.rb:345:inconverge’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/client.rb:431:in
do_run' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/client.rb:213:inblock in run’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/client.rb:207:in
fork' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/client.rb:207:inrun’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/application.rb:217:in
run_chef_client' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/application/solo.rb:221:inblock in run_application’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/application/solo.rb:213:in
loop' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/application/solo.rb:213:inrun_application’
from
/opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/lib/chef/application.rb:67:in
run' from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.8/bin/chef-solo:25:in<top (required)>'
from /usr/bin/chef-solo:23:in load' from /usr/bin/chef-solo:23:in'
---- End output of “bash” “/tmp/chef-script20140711-11259-1194mty” ----
Ran “bash” “/tmp/chef-script20140711-11259-1194mty” returned 1

Resource Declaration:

In /var/chef/cookbooks/magento/recipes/default.rb

58: bash ‘Tweak apc.ini file’ do
59: cwd php_conf[1] # module ini files
60: code <<-EOH
61: grep -q -e ‘apc.stat=0’ apc.ini || echo “apc.stat=0” >> apc.ini
62: EOH
63: end
64:

Compiled Resource:

Declared in /var/chef/cookbooks/magento/recipes/default.rb:58:in

`from_file’

bash(“Tweak apc.ini file”) do
action "run"
retries 0
retry_delay 2
guard_interpreter :default
command "“bash” “/tmp/chef-script20140711-11259-1194mty”"
backup 5
cwd "/etc/php5/conf.d"
returns 0
code " grep -q -e ‘apc.stat=0’ apc.ini || echo “apc.stat=0” >>
apc.ini\n"
interpreter "bash"
cookbook_name :magento
recipe_name "default"
end

Recipe: php-fpm::install

  • service[php-fpm] action restart
    • restart service service[php-fpm]

Running handlers:
[2014-07-11T07:55:18+00:00] ERROR: Running exception handlers
Running handlers complete

On Fri, Jul 11, 2014 at 1:02 PM, Venkatesh Ainalli venki.ain@gmail.com
wrote:

Ohai!

I tried to deploy magento [
https://supermarket.getchef.com/cookbooks/magento] on aws Linux template
getting following error.

Recipe: magento::default

  • user[magento] action create
    • create user user[magento]

Recipe: php-fpm::repository

  • yum_repository[remi] action addRecipe:

  • template[/etc/yum.repos.d/remi.repo] action create

    • create new file /etc/yum.repos.d/remi.repo
    • update content in file /etc/yum.repos.d/remi.repo from none to 455d89
      — /etc/yum.repos.d/remi.repo 2014-07-11 07:20:49.943908715
      +0000
      +++ /tmp/chef-rendered-template20140711-7615-181biix 2014-07-11
      07:20:49.947908716 +0000
      @@ -1 +1,12 @@
      +# This file was generated by Chef
      +# Do NOT modify this file by hand.
      +
      +[remi]
      +name=Remi
      +baseurl=
      http://rpms.famillecollet.com/enterprise/$releasever/remi/$basearch/
      +enabled=1
      +gpgcheck=1
      +gpgkey=http://rpms.famillecollet.com/RPM-GPG-KEY-remi
      +mirrorlist=
      http://rpms.famillecollet.com/enterprise/$releasever/remi/mirror
      +sslverify=1
    • change mode from ‘’ to ‘0644’
  • execute[yum-makecache-remi] action run

================================================================================
Error executing action run on resource ‘execute[yum-makecache-remi]’

================================================================================

Mixlib::ShellOut::ShellCommandFailed

Expected process to exit with [0], but received ‘1’
---- Begin output of yum -q makecache --disablerepo=* --enablerepo=remi

STDOUT: Could not retrieve mirrorlist
http://rpms.famillecollet.com/enterprise/2014.03/remi/mirror error was
14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
STDERR:
http://rpms.famillecollet.com/enterprise/2014.03/remi/x86_64/repodata/repomd.xml:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found"
Trying other mirror.

One of the configured repositories failed (Remi),
and yum doesn’t have enough cached data to continue. At this point the
only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the

problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a

working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will

then
just ignore the repository until you permanently enable it again
or use
–enablerepo for temporary usage:

        yum-config-manager --disable remi

 4. Configure the failing repository to be skipped, if it is

unavailable.
Note that yum will try to contact the repo. when it runs most
commands,
so will have to try and fail each time (and thus. yum will be be
much
slower). If it is a very temporary problem though, this is often a
nice
compromise:

        yum-config-manager --save

–setopt=remi.skip_if_unavailable=true

failure: repodata/repomd.xml from remi: [Errno 256] No more mirrors to try.
---- End output of yum -q makecache --disablerepo=* --enablerepo=remi ----
Ran yum -q makecache --disablerepo=* --enablerepo=remi returned 1

Resource Declaration:

In /var/chef/cookbooks/yum/providers/repository.rb

53: execute “yum-makecache-#{new_resource.repositoryid}” do
54: command "yum -q makecache --disablerepo=*
–enablerepo=#{new_resource.repositoryid}"
55: action :nothing
56: end
57:

Compiled Resource:

Declared in /var/chef/cookbooks/yum/providers/repository.rb:53:in `block

in class_from_file’

execute(“yum-makecache-remi”) do
action [:nothing]
retries 0
retry_delay 2
guard_interpreter :default
command "yum -q makecache --disablerepo=* --enablerepo=remi"
backup 5
returns 0
cookbook_name :"php-fpm"
end

================================================================================
Error executing action add on resource ‘yum_repository[remi]’

================================================================================

Regards
Venky