Skip to main content

Install RHQ agent on linux

Installing RHQ agent is simple. Only thing you have to do is just download plugin jar save it and run the installation command like java -jar <agent-download.jar> --install=<agent directory>. But i want to explain how we can install the agent as a service.

With the following script rhq enterprise agent 4.2.0 can be installed as a service on redhat linux.
#!/bin/bash
script_dir=$PWD
jb_home=~jboss
echo $jb_home
export JAVA_HOME=<your jvm>
echo <your server ip>       <your server name>  >> /etc/hosts
cp -fr rhqagent-init-script /etc/init.d/rhqagent
chmod 755 /etc/init.d/rhqagent


mkdir $jb_home/rhqagent
chown -R jboss:jboss $jb_home/rhqagent
chmod 755 $jb_home/rhqagent
java -jar rhq-enterprise-agent-4.2.0.jar --install=$jb_home/rhqagent
$jb_home/rhqagent/rhq-agent/bin/rhq-agent.sh


Remember: RHQ agent will be installed to the jboss user's home path. So if you want to use different path change the path accordingly. And also you can change the jvm path to yours. Service name is rhqagent

Comments

  1. Question on this Line :
    cp -fr rhqagent-init-script /etc/init.d/rhqagent

    As i understood, your script above (the whole) is named rhqagent-init-script.
    but with this line, your script is copied to init.d But then it always runs through the whole setup again ? or what is meant by "rhqagent-init-script" ?

    ReplyDelete
  2. hmm. When i first install rhqagent manually with " java -jar --install=" command, rhq-init-script came from there. so the above script (let's call it rhq-agent-install.sh) is different from rhq-init-script which contains:
    #!/bin/sh
    # description:rhqagent
    # chkconfig: 345 80 20

    export JAVA_HOME=/usr/java/default

    function main {
    case "$1" in
    start)
    ~jboss/rhqagent/rhq-agent/bin/rhq-agent-wrapper.sh start
    ;;
    stop)
    ~jboss/rhqagent/rhq-agent/bin/rhq-agent-wrapper.sh stop
    ;;
    kill)
    ~jboss/rhqagent/rhq-agent/bin/rhq-agent-wrapper.sh kill
    ;;
    restart)
    ~jboss/rhqagent/rhq-agent/bin/rhq-agent-wrapper.sh restart
    ;;
    status)
    ~jboss/rhqagent/rhq-agent/bin/rhq-agent-wrapper.sh status
    ;;
    *)
    echo "Usage: $0 { start | stop | kill | restart | status }"
    exit 1
    ;;
    esac
    }
    main $1

    I forgot putting it to the post. Sorry :)
    Last but not least, these three files(init script, install.sh and jar file) should be in same folder. Good luck.

    ReplyDelete

Post a Comment

Popular posts from this blog

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter:

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three