Open neerajm17 opened 10 years ago
Can you provide a few more details:
Thanks so much for helping out!
The output is as follows: [root@local vagrant]# facter -p architecture => x86_64 augeasversion => 0.9.0 bios_release_date => 07/02/2012 bios_vendor => Phoenix Technologies LTD bios_version => 6.00 blockdevice_sda_model => VMware Virtual S blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => VMware, blockdevice_sr0_model => VMware IDE CDR10 blockdevice_sr0_size => 1073741312 blockdevice_sr0_vendor => NECVMWar blockdevices => sda,sr0 boardmanufacturer => Intel Corporation boardproductname => 440BX Desktop Reference Platform boardserialnumber => None domain => local.service.some.com facterversion => 1.7.0 filesystems => ext4,iso9660 fqdn => local.service.some.com hardwareisa => x86_64 hardwaremodel => x86_64 hostname => local id => root interfaces => eth0,eth1,lo ipaddress => 192.168.82.253 ipaddress_eth0 => 192.168.82.253 ipaddress_eth1 => 192.168.4.12 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.32-358.el6.x86_64 kernelversion => 2.6.32 macaddress => 00:0C:29:FE:12:7E macaddress_eth0 => 00:0C:29:FE:12:7E macaddress_eth1 => 00:0C:29:FE:12:88 manufacturer => VMware, Inc. memoryfree => 389.20 MB memoryfree_mb => 389.20 memorysize => 490.59 MB memorysize_mb => 490.59 memorytotal => 490.59 MB mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 192.168.82.0 network_eth1 => 192.168.4.0 network_lo => 127.0.0.0 operatingsystem => CentOS operatingsystemmajrelease => 6 operatingsystemrelease => 6.4 osfamily => RedHat path => /sbin:/bin:/usr/sbin:/usr/bin physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz processorcount => 1 productname => VMware Virtual Platform ps => ps -ef puppetversion => 3.1.1 rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.7 selinux => false serialnumber => VMware-56 4d 51 68 17 f4 b4 19-d2 d0 df 1e 07 fe 12 7e sshdsakey => AAAAB3N sshfp_dsa => SSHFP 2 1 6c19579c2d49f176e9ecdb365c68857e255ca8ba SSHFP 2 2 22d1cc6e4bb6d6ef4afe8c20a812eb26ce7b305d6ed7f3d6fd05dd3e24ca0e2c sshfp_rsa => SSHFP 1 1 7f6d2263fddcc33ee035ec8fcfbd4fb612a4f4fb SSHFP 1 2 6a3f04664c57668192542a4bf2674dc4c1d50d8e8ec03ceeeb0e33bd025e281a sshrsakey => AAAAB3N swapfree => 921.35 MB swapfree_mb => 921.35 swapsize => 927.99 MB swapsize_mb => 927.99 timezone => UTC type => Other uniqueid => 007f0100 uptime => 0:09 hours uptime_days => 0 uptime_hours => 0 uptime_seconds => 547 uuid => 564D5168-17F4-B419-D2D0-DF1E07FE127E virtual => vmware [root@local vagrant]#
I tired as follows but still jboss does not run on startup:
include jboss
class { "jboss":
version => '7',
bindaddr => '0.0.0.0',
require => Package['unzip', 'java'],
}
The debug message states that it did: Notice: /Stage[main]/Jboss::Service/File[jboss.init]/ensure: created Debug: /Stage[main]/Jboss::Service/File[jboss.init]: The container Class[Jboss::Service] will propagate my refresh event Debug: Executing '/sbin/service jboss status' Debug: Executing '/sbin/chkconfig jboss' Debug: Executing '/sbin/service jboss start' Debug: Executing '/sbin/chkconfig jboss' Debug: Executing '/sbin/chkconfig jboss on' Notice: /Stage[main]/Jboss::Service/Service[jboss]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Jboss::Service/Service[jboss]: The container Class[Jboss::Service] will propagate my refresh event
However, a ps -ef shows jboss not running:
[root@local vagrant]# ps -ef | grep jboss | grep -v grep [root@local vagrant]#
Hello, just checking if you had a chance to look into this issue? Thanks so much!
Hi, sorry, I really hadn't the time to look at this. Development and maintenance of these modules is mostly done on a job basis: when I have to develop or fix them for work needs I do that, otherwise everything is done following a best effort approach. Eventually consider the opportunity to sponsor the development / patch of the module.
During puppy apply, I do see the following message: Debug: Executing '/sbin/chkconfig jboss on' Notice: /Stage[main]/Jboss::Service/Service[jboss]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Jboss::Service/Service[jboss]: The container Class[Jboss::Service] will propagate my refresh event Debug: Class[Jboss::Service]: The container Stage[main] will propagate my refresh event
However, when I login to the instance and check for ps -ef | grep jboss, jboss is not running. I am able to do a service jboss start and that works.
This a centos 6 server. Any hints on what might be the issue?
Thanks so much for your help!