Closed onsails closed 11 years ago
The problem with service start on Ubuntu/Debian should be fixed here: https://github.com/example42/puppet-jboss/commit/9896b24f77fe0cac46c0f8daf9f9e954981544de (Please let me know if that solves the issue also for you).
Java is not installed because you may decide this install it with different modules and different versions, so I didn't want to force its installation in the module. A good for Example42's Jboss module usage is here: https://github.com/example42/puppet-playground/blob/master/toasters/example42-jboss/manifests/init.pp
Java is not installed because you may decide this install it with different modules and different versions, so I didn't want to force its installation in the module. A good for Example42's Jboss module usage is here: https://github.com/example42/puppet-playground/blob/master/toasters/example42-jboss/manifests/init.pp Got it, thanks.
(Please let me know if that solves the issue also for you). As I commented in Pull request the problem with debian/ubuntu init script solved, thanks
Puppet-jboss does not installs java on node (I used
install => puppet
option). After puppet-jboss installed puppet agent freezes on/etc/init.d/jboss start
command. Here is output I got after I ran launched the command manually:sudo /etc/init.d/jboss start Starting : /opt/jboss/bin/standalone.sh: 1: eval: java: not found /etc/init.d/jboss: 129: /etc/init.d/jboss: let: not found /etc/init.d/jboss: 129: /etc/init.d/jboss: let: not found /etc/init.d/jboss: 129: /etc/init.d/jboss: let: not found
... and so on.