Expanded the dashboard a bit, and found the time series data helpful in tracking down some nagging performance issues.
The time series charts in these screen shots illustrate two brief performance hits. Since these hits happen at the top of the hours, I looked carefully a the application scheduled tasks and found a number of "clean up" tasks which were not an issue with the DB was small, but with a large DB these "clean up" hourly scheduled tasks can slow the site down.
So, I moved around five clean-up tasks to Saturday and Sunday, since moving these batch jobs to the weekend will not effect the application very much, but does improve performance quite a bit.
In the production hacmp 5.3 is running with three nodes but i want to add new node to cluster with out stopping the application ie with same resource group if any bady know pls help me. (1 Reply)
I have configured a custom application monitor with restart count = 3.
say the application has restarted 2 times, if the application fail 2 more times within restart interval, it will failover.
Is there any counter to tell me the recent restart count?
Thanks!! (1 Reply)
Hi Experts,
I am in need of running a script from one node say node 1 via node 2.
My scheduling tool dont have access to node2 , so i need to invoke the list file from node1 but the script needs to run from node2. because the server to which i am hitting, is having access only for the node... (5 Replies)
A client is accessing our JBoss server. In the past, we set up a keystore and everything worked fine.
That certificat expired and we've installed the new one. Now the client is getting the following error -
HTTP/1.1 500 Internal Server Error
Date: Mon, 14 Apr 2014 13:25:44 GMT
Server:... (1 Reply)
Here we go....
Preface:
..... so in a galaxy far, far, far away from commercial, data sharing corporations.....
For this project, I used the ESP-WROOM-32 as an MQTT (publish / subscribe) client which receives Linux server "load averages" as messages published as MQTT pub/sub messages.... (6 Replies)
Various Node-Red crypto modules do not work with PHP, so to send an encrypted message from a PHP script (in this case from a Ubuntu server) to Node-RED we need our own code.
After a few hours of searching, testing various libs, more testing and debugging, I got this PHP to Node-RED code... (0 Replies)
First, I want to thank Neo (LOL) for this post from 2018, Node.js and mysql - ER_ACCESS_DENIED_ERROR
I could not get the Node-RED mysql module to work and searched Google until all my links were purple! I kept getting ER_ACCESS_DENIED_ERROR with the right credentials. Nothing on the web was... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT DEBIAN
chef-client
CHEF-CLIENT(8) Chef Manual CHEF-CLIENT(8)NAME
chef-client - Runs a client node connecting to a chef-server.
SYNOPSIS
chef-client (options)
-S, --server CHEFSERVERURL
The chef server URL
-c, --config CONFIG
The configuration file to use
-d, --daemonize
Daemonize the process
-g, --group GROUP
Group to set privilege to
-i, --interval SECONDS
Run chef-client periodically, in seconds
-j, --json-attributes JSON_ATTRIBS
Load attributes from a JSON file or URL
-E, --environment ENVIRONMENT
Set the Chef Environment on the node
-l, --log_level LEVEL
Set the log level (debug, info, warn, error, fatal)
-L, --logfile LOGLOCATION
Set the log file location, defaults to STDOUT - recommended for daemonizing
-V, --verbose
Ensures logging goes to STDOUT as well as to other configured log location(s).
-N, --node-name NODE_NAME
The node name for this client
-o, --override-runlist
Replace current run list with specified items
-K, --validation_key KEY_FILE
Set the validation key file location, used for registering new clients
-k, --client_key KEY_FILE
Set the client key file location
-s, --splay SECONDS
The splay time for running at intervals, in seconds
-u, --user USER
User to set privilege to
-P, --pid PIDFILE
Set the PID file location, defaults to /tmp/chef-client.pid
--once Cancel any interval or splay options, run chef once and exit
-v, --version
Show chef version
-h, --help
Show this message
DESCRIPTION
The Chef Client is where almost all of the work in Chef is done. It communicates with the Chef Server via REST, authenticates via Signed
Header Authentication, and compiles and executes Cookbooks.
A Chef Client does work on behalf of a Node. A single Chef Client can run recipes for multiple Nodes.
Clients are where all the action happens - the Chef Server and Chef Expander are largely services that exist only to provide the Client
with information.
SEE ALSO
Full documentation for Chef and chef-client is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.
AUTHOR
Chef was written by Adam Jacob adam@ospcode.com of Opscode (http://www.opscode.com), with contributions from the community. This manual
page was written by Joshua Timberman joshua@opscode.com with help2man. Permission is granted to copy, distribute and / or modify this docu-
ment under the terms of the Apache 2.0 License.
On Debian systems, the complete text of the Apache 2.0 License can be found in /usr/share/common-licenses/Apache-2.0.
Chef 10.12.0 June 2012 CHEF-CLIENT(8)