I like to use tmadmin commands to monitor running application in tuxedo server 12c.But When i use tmadmin help command i get only meta commands.But i like to check printconn,printclient,printserver like that.But these commands are not avaialble in list.I here pasted the help command output.Can any one help me to get the above mentioned commands in tmadmin.
Thank you
Selvakumar
Moderator's Comments:
Please use code tags next time for your code and data. Thanks
Hello,
I work with 4 flavour of UNIX ( AIX, IRIX, HPUX and SUN). I have a problem maintaing the system. can any one let me know of the software or script that will check the date,time services running or not, perticular machine is up or not and post a mail with all the details.
It... (3 Replies)
I am the Linux Admin in my organisation and need to write a shell script which will monitor the machine statistics every day and will send a consolidated report to me on my email id / will display the output into a file.
Does anyone have such kind of script fulfilling this kind of purpose?
... (4 Replies)
Hi guys i have purchased sun server for my visualization project.
Request you to help me finding the io for disk .
I have put storage(disks) on different location (File Server) and on server (Application) i have configured 4 virtual machines.
How would i monitor the io for file server from... (0 Replies)
Hi,
We user What's Up Gold tool for monitoring the WIndows servers. My idea is to add my Solaris 10 server to this monitoring tool. Is it feasible? If yes, can somebody help in configuring the server onto the tool?
My current solaris 10 server is i86pc, and has SNMP daemons running. the... (0 Replies)
we have a server, which becomes down at times and we dont get any notification mail.
Can we monitor PID for that server run and create a script to send notification to a mail id?
I have URL for the server, which I can use.
Please let me know if more information is required from my end to... (2 Replies)
:wall:hi all, as hp support pack has hpasm, hpacu command using in linux server to show and monitor hareware status.
hpacu command was avaialbe in windows server also, but where can find hpasm command in windows, it looks hp support pack not support hpasm in windows. any one can help? an... (1 Reply)
Hi All,
I am new to JMX.Can anybody tell me how to use this it on unix server.
Using JMX i want to check the system monitoring(%cpu utilization , size utilization )how to start JMX on UNIX
Thanks
Double post, continued (9 Replies)
Hi all - newb here.
We're a Windows shop and I'm looking for something that I could stand up to monitor various aspects of our servers. I'm specifically looking for something that can:
verify that servers are up
verify services are up
verify remote sites are up/accessible
monitor CPU &... (2 Replies)
Hi forum
We have nearly 240 servers inclding zones . How can i monitor server and its performance by using any monitoring tools. My indentions is to plot graphs based on server utilization interms of cpu and memory
Is there any opensource tools for this.
I saw collectd and it has agent... (3 Replies)
I want to write a shell script which is used in cron job and it runs every 4 hours to check whether tomcat servers are running or not . If servers are not running , one email should be triggered like alert notification. if servers are Running then no need to print anything.
This is what i want... (5 Replies)
Discussion started by: kk123
5 Replies
LEARN ABOUT DEBIAN
ocf_heartbeat_nginx
OCF_HEARTBEAT_NGINX(7) OCF resource agents OCF_HEARTBEAT_NGINX(7)NAME
ocf_heartbeat_nginx - Manages an Nginx web/proxy server instance
SYNOPSIS
nginx [start | stop | status | monitor | meta-data | validate-all]
DESCRIPTION
This is the resource agent for the Nginx web/proxy server. This resource agent does not monitor POP or IMAP servers, as we don't know how
to determine meaningful status for them.
The start operation ends with a loop in which monitor is repeatedly called to make sure that the server started and that it is operational.
Hence, if the monitor operation does not succeed within the start operation timeout, the nginx resource will end with an error status.
The default monitor operation will verify that nginx is running.
The level 10 monitor operation by default will try and fetch the /nginx_status page - which is commented out in sample nginx
configurations. Make sure that the /nginx_status page works and that the access is restricted to localhost (address 127.0.0.1) plus
whatever places _outside the cluster_ you want to monitor the server from. See the status10url and status10regex attributes for more
details.
The level 20 monitor operation will perform a more complex set of tests from a configuration file.
The level 30 monitor operation will run an external command to perform an arbitrary monitoring operation.
SUPPORTED PARAMETERS
configfile
The full pathname of the Nginx configuration file. This file is parsed to provide defaults for various other resource agent parameters.
(unique, optional, string, no default)
httpd
The full pathname of the httpd binary (optional). (optional, string, default /usr/sbin/httpd)
port
A port number that we can probe for status information using the statusurl. This will default to the port number found in the
configuration file, or 80, if none can be found in the configuration file. .sp
(optional, integer, no default)
status10url
The URL to monitor (the nginx server status page by default) when given a level 10 monitor operation. If left unspecified, it will be
inferred from the nginx configuration file, or defaulted to /nginx_status. .sp If you set this, make sure that it succeeds *only* from
the localhost (127.0.0.1) and no other cluster nodes. Otherwise, the cluster software may complain about it being active on multiple
nodes. (optional, string, no default)
status10regex
Regular expression to match in the output of status10url. Case insensitive. (optional, string, default Reading: [0-9]+ Writing: [0-9]+
Waiting: [0-9]+)
testclient
Client to use to query to Nginx for level 10 and level 20 tests. If not specified, the RA will try to find one on the system.
Currently, wget and curl are supported, with curl being preferred. For example, you can set this parameter to "wget" if you prefer that
to curl. (optional, string, no default)
testurl
URL to test. If it does not start with "http", then it's considered to be relative to the document root address. (optional, string, no
default)
test20regex
Regular expression to match in the output of testurl. Case insensitive. (optional, string, no default)
testconffile
A file which contains a more complex test configuration. Could be useful if you have to check more than one web application or in case
sensitive info should be passed as arguments (passwords). Furthermore, using a config file is the only way to specify certain
parameters. .sp Please see README.webapps for examples and file description. (optional, string, no default)
test20name
Name of the test within the test configuration file. (optional, string, no default)
external_monitor30_cmd
Command string to run which implements level 30 monitoring. (optional, string, no default)
options
Extra options to apply when starting nginx. (optional, string, no default)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 40s.
stop
Stops the resource. Suggested minimum timeout: 60s.
reload
Suggested minimum timeout: 40s.
status
Performs a status check. Suggested minimum timeout: 30s.
monitor
Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 10s.
monitor
Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 30s.
monitor
Performs a detailed status check. Suggested minimum timeout: 45s.
monitor
Performs a detailed status check. Suggested minimum timeout: 60s.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a nginx resource using the crm(8) shell:
primitive p_nginx ocf:heartbeat:nginx
op monitor timeout="30s" depth="0" interval="10s"
op monitor timeout="30s" depth="10" interval="30s"
op monitor timeout="45s" depth="20"
op monitor timeout="60s" depth="30"
SEE ALSO
http://www.linux-ha.org/wiki/nginx_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_NGINX(7)