search

example42 / puppet-jboss

Jboss Puppet Module
http://www.example42.com
Other
15 stars 25 forks source link

Errors while installting JBOSS #5

Closed rkathpal closed 8 years ago

rkathpal commented 11 years ago

Hi,

I am a big fan of example42 modules and using most of them, currently I am facing issues with the Jboss module

I ma using the latest jboss build from example42 and latest puppi modules as well.. but still getting the following errors

info: Caching catalog for ABC info: Applying configuration version '1358506111' notice: /Stage[main]/Jboss::User/User[jboss]/ensure: created notice: /Stage[main]/Jboss::Install/File[jboss_link]/ensure: created notice: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Retrieve http://download.jboss.org/jbossas/6.1/jboss-as-distribution-6.1.0.Final.zip]/returns: executed successfully notice: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Extract jboss-as-distribution-6.1.0.Final.zip]/returns: executed successfully info: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Extract jboss-as-distribution-6.1.0.Final.zip]: Scheduling refresh of Exec[PostExtract jboss-as-distribution-6.1.0.Final.zip] info: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Extract jboss-as-distribution-6.1.0.Final.zip]: Scheduling refresh of Exec[Chown jboss-as-distribution-6.1.0.Final.zip] err: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[PostExtract jboss-as-distribution-6.1.0.Final.zip]: Failed to call refresh: Working directory '/opt/jboss-as-distribution-6.1.0.Final' does not exist err: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Chown jboss-as-distribution-6.1.0.Final.zip]: Failed to call refresh: chown -R root:root /opt/jboss-as-distribution-6.1.0.Final returned 1 instead of one of [0] at /etc/puppet/modules/puppi/manifests/netinstall.pp:118 notice: /Stage[main]/Jboss::Service/File[jboss.init]/ensure: created notice: /Stage[main]/Jboss::Service/Service[jboss]/ensure: ensure changed 'stopped' to 'running'

notice: Finished catalog run in 49.37 seconds

my node manifest is

node 'ABC' { class { 'jboss':

}

Currently I am trying the module on centos but will need it immediately for suse/ubuntu and rhel as well....

please help..

Thanks in advance...

rkathpal commented 11 years ago

pasting the error again for your reference....

info: Applying configuration version '1358512433' notice: /Stage[main]/Jboss::User/User[jboss]/ensure: created notice: /Stage[main]/Jboss::Install/File[jboss_link]/ensure: created notice: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Extract jboss-as-distribution-6.1.0.Final.zip]/returns: executed successfully info: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Extract jboss-as-distribution-6.1.0.Final.zip]: Scheduling refresh of Exec[Chown jboss-as-distribution-6.1.0.Final.zip] info: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Extract jboss-as-distribution-6.1.0.Final.zip]: Scheduling refresh of Exec[PostExtract jboss-as-distribution-6.1.0.Final.zip] err: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[PostExtract jboss-as-distribution-6.1.0.Final.zip]: Failed to call refresh: Working directory '/opt/jboss-as-distribution-6.1.0.Final' does not exist err: /Stage[main]/Jboss::Install/Puppi::Netinstall[netinstall_jboss]/Exec[Chown jboss-as-distribution-6.1.0.Final.zip]: Failed to call refresh: chown -R root:root /opt/jboss-as-distribution-6.1.0.Final returned 1 instead of one of [0] at /etc/puppet/modules/puppi/manifests/netinstall.pp:135 notice: /Stage[main]/Jboss::Service/Service[jboss]/ensure: ensure changed 'stopped' to 'running' notice: Finished catalog run in 8.60 seconds

alvagante commented 11 years ago

Hi, just committed a quick fix to that. I think I still have some problems (jboss is installed, but its service doesn't start smoothly) but I've not right now too much time to explore it... if you can verify if the patch works and eventually figure out what's wrong with the service it would be great.

rkathpal commented 11 years ago

Thanks a ton mate...

All works like a charm other than the service restart for CENTOS atleast... will check on other distros and let you know later

After the module gets installed.. service gets started using the command below

cd /opt/jboss/bin; /opt/jboss/bin/run.sh -c default -b 127.0.0.1

Thanks a ton.. :)

On Fri, Jan 18, 2013 at 6:13 PM, Alessandro Franceschi < notifications@github.com> wrote:

i

rkathpal commented 11 years ago

Works perfectly for Ubuntu with the following nodes manifest

node 'ABC' { class {'java': } package { unzip: ensure => present; } class { 'jboss': bindaddr => "0.0.0.0", } }

even the service starts without any issues.. .

Thanks & Regards, Rakesh K.

On Fri, Jan 18, 2013 at 6:22 PM, Rakesh Kathpal rkathpal@gmail.com wrote:

Thanks a ton mate...

All works like a charm other than the service restart for CENTOS atleast... will check on other distros and let you know later

After the module gets installed.. service gets started using the command below

cd /opt/jboss/bin; /opt/jboss/bin/run.sh -c default -b 127.0.0.1

Thanks a ton.. :)

On Fri, Jan 18, 2013 at 6:13 PM, Alessandro Franceschi < notifications@github.com> wrote:

i

rkathpal commented 11 years ago

Dear Alessandro,

I have verified the module on all distros and other than ubuntu all distros have the issue with starting up of the service. The installation part works without any issues.

Please let me know if you plan to fix the service part anytime sooner.

And I would like you to know that I really appreciate your work and your help in this matter.

Thanks & Regards,

Rakesh K.

On Fri, Jan 18, 2013 at 7:16 PM, Rakesh Kathpal rkathpal@gmail.com wrote:

Works perfectly for Ubuntu with the following nodes manifest

node 'ABC' { class {'java': } package { unzip: ensure => present; } class { 'jboss': bindaddr => "0.0.0.0", } }

even the service starts without any issues.. .

Thanks & Regards, Rakesh K.

On Fri, Jan 18, 2013 at 6:22 PM, Rakesh Kathpal rkathpal@gmail.comwrote:

Thanks a ton mate...

All works like a charm other than the service restart for CENTOS atleast... will check on other distros and let you know later

After the module gets installed.. service gets started using the command below

cd /opt/jboss/bin; /opt/jboss/bin/run.sh -c default -b 127.0.0.1

Thanks a ton.. :)

On Fri, Jan 18, 2013 at 6:13 PM, Alessandro Franceschi < notifications@github.com> wrote:

i

alvagante commented 11 years ago

Hei Rakesh, thank you for your tests. Currently I really do not have the time to explore better the issue and find a solution. If you have some ideas of where is the problem, please write it here (a git pull request with the fix would be great, but also any help that can help me in finding a quick solution). Ciao Al

alvagante commented 11 years ago

Hei @rkathpal this commit should fix the problem with service start: https://github.com/example42/puppet-jboss/commit/9896b24f77fe0cac46c0f8daf9f9e954981544de Please, let me know if that's true (and eventually close the issue)

rkathpal commented 11 years ago

Hi,

I reinstalled the jboss module and then tried to apply it on one of my centos client... but still the same issue with startup script..

Though the error goes for starting up the script but jboss doesn't startup actually.

Thanks & Regards,

Rakesh K.

On Sun, Jan 27, 2013 at 4:13 AM, Alessandro Franceschi < notifications@github.com> wrote:

Hei @rkathpal https://github.com/rkathpal thei commit should fix the proble with service start: 9896b24https://github.com/example42/puppet-jboss/commit/9896b24f77fe0cac46c0f8daf9f9e954981544de Please, let me know if that's true (and eventually close the issue)

— Reply to this email directly or view it on GitHubhttps://github.com/example42/puppet-jboss/issues/5#issuecomment-12743865.

parvesh262 commented 8 years ago

Hi All , I am trying to install Jboss on RHEL 7.x , using puppet enterprise version > 4.x .

Getting cyclic dependency error ..

Stage[main]/Puppet_enterprise::Profile::Mcollective::Peadmin/Puppet_enterprise::Mcollective::Client[peadmin]/Puppet_enterprise::Mcollective::Client::User[peadmin]/Pe_accounts::User[peadmin]/Pe_accounts::Home_dir[/var/lib/peadmin]/File[/var/lib/peadmin/.ssh/authorized_keys]: Adding autorequire relationship with Group[peadmin] Debug: Storing state Debug: Stored state in 0.14 seconds Error: Failed to apply catalog: Found 1 dependency cycle: (File[jboss.conf] => Service[jboss] => Class[Jboss::Service] => Class[Jboss] => File[jboss.conf]) Cycle graph written to /opt/puppetlabs/puppet/cache/state/graphs/cycles.dot. /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/simple_graph.rb:242:in report_cycles_in_graph' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:106:intraverse' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:142:in evaluate' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:inblock in apply' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in with_destination' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:118:inas_logging_destination' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:220:in apply' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:inblock in apply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in block in benchmark' /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:inrealtime' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:222:in benchmark' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:inapply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:315:in `run_internal' /opt/puppetlabs/puppet/l

Dot file looks like : digraph Resource_Cycles { label = "Resource Cycles" "File[jboss.conf]" -> "Service[jboss]" -> "Class[Jboss::Service]" -> "Class[Jboss]" -> "File[jboss.conf]" "File[jboss.conf]" -> "Service[jboss]" -> "Class[Jboss::Service]" -> "Class[Jboss]" -> "File[jboss.dir]" -> "File[jboss.conf]" "File[jboss.conf]" -> "Service[jboss]" -> "Class[Jboss::Service]" -> "Class[Jboss]" -> "File[jboss.dir]" -> "Service[jboss]" }

Could you please let me how to resolve this .As i am new to this .

alvagante commented 8 years ago

Wheere do you declare/include the jboss class? In a manifest? If so, please copy here the code. In PE node classifier? If so you do pass any further parameter (either via the web interface of via hiera) to the class? Also do you refer to the Jboss class somewhere in your code?

alvagante commented 8 years ago

This commit should fix the issue: https://github.com/example42/puppet-jboss/commit/93962fa49b7311752874f81742f60dc019ce1776