Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring Using Node-RED and MQTT to Monitor Server and Application Stats Post 303043733 by Neo on Wednesday 5th of February 2020 07:28:19 AM
Old 02-05-2020
Well, those changes did not help much.... looks like here is some "underground" process running every three hours causing the spikes:

Using Node-RED and MQTT to Monitor Server and Application Stats-screen-shot-2020-02-05-72457-pmjpg


I checked all the forum software and all the cron files on the server, but so far, no joy in finding the process causing the intermittent performance hit.
 

7 More Discussions You Might Find Interesting

1. AIX

How to add node to the cluster with stoping the application?

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)
Discussion started by: manjunath.m
1 Replies

2. AIX

powerha application monitor restart counter?

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)
Discussion started by: skeyeung
1 Replies

3. Homework & Coursework Questions

Accessing one UNIX node from another node of the same server

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)
Discussion started by: arun1377
5 Replies

4. Red Hat

Red Hat application server ssl keystore problem

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)
Discussion started by: kkinney
1 Replies

5. Programming

ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages

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)
Discussion started by: Neo
6 Replies

6. Programming

Publish and Subscribe to AES-256 Encrypted MQTT Messages to Node-RED from PHP Scripts

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)
Discussion started by: Neo
0 Replies

7. Programming

Node-RED: Writing MQTT Messages to MySQL DB with UNIX timestamp

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
myproxy-admin-query(8)						      MyProxy						    myproxy-admin-query(8)

NAME
myproxy-admin-query - query MyProxy repository contents SYNOPSIS
myproxy-admin-query [ options ] DESCRIPTION
The myproxy-admin-query command displays information about the credentials stored in the MyProxy repository. It can also be used to remove credentials from the repository, by combining query options with --remove. It accesses the repository directly and must be run on the machine where the myproxy-server(8) is installed from the account that owns the repository. An example cron job for running myproxy-admin-query periodically to remove invalid (expired, revoked, etc.) credentials from the repository is provided at $GLOBUS_LOCATION/share/myproxy/myproxy.cron. OPTIONS
-h, --help Displays command usage text and exits. -u, --usage Displays command usage text and exits. -v, --verbose Enables verbose debugging output to the terminal. -V, --version Displays version information and exits. -l username, --username username Return information on credentials for a single username. By default, the command returns information on all credentials for all usernames. -k name, --credname name Return information on the credentials with the specified name. -o DN, --owner DN Return information on the credentials owned by the specified distinguished name. -e hours, --expiring_in hours Return information on credentials with remaining lifetime less than the specified number of hours. For example, -e 0 will return all expired credentials. -t hours, --time_left hours Return information on credentials with remaining lifetime greater than the specified number of hours. -i, --invalid Return information on invalid (expired, revoked, etc.) credentials. -s dir, --storage dir Specifies the location of the credential storage directory. The directory must be accessible only by the user running the myproxy- server process for security reasons. Default: /var/lib/myproxy or /var/myproxy or $GLOBUS_LOCATION/var/myproxy -c file, --config file Specifies the location of the myproxy-server configuration file, for OCSP options. Default: /etc/myproxy-server.config or $GLOBUS_LOCATION/etc/myproxy-server.config -r, --remove Remove the credentials matching the query from the repository. For example, myproxy-admin-query -e 0 -r will remove all expired credentials from the repository. -L 'msg', --lock 'msg' Places the credentials matching the query under an administrative lock and specifies a message to be returned on access attempts. Be sure to put the message in quotes so it is captured as one argument to the command. -U, --unlock Removes any administrative locks for the credentials matching the query. EXIT STATUS
0 on success, >0 on error AUTHORS
See http://myproxy.ncsa.uiuc.edu/about for the list of MyProxy authors. SEE ALSO
myproxy-change-pass-phrase(1), myproxy-destroy(1), myproxy-init(1), myproxy-logon(1), myproxy-retrieve(1), myproxy-store(1), myproxy- server.config(5), myproxy-admin-adduser(8), myproxy-admin-change-pass(8), myproxy-admin-load-credential(8), myproxy-server(8) MyProxy 2011-09-19 myproxy-admin-query(8)
All times are GMT -4. The time now is 02:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy