Well, those changes did not help much.... looks like here is some "underground" process running every three hours causing the spikes:
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.
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 PLAN9
attach
ATTACH(5) File Formats Manual ATTACH(5)NAME
attach, session, nop - messages to initiate activity
SYNOPSIS
Tnop tag[2]
Rnop tag[2]
Tsession tag[2] chal[8]
Rsession tag[2] chal[8] authid[28] authdom[48]
Tattach tag[2] fid[2] uid[28] aname[28] ticket[72] auth[13]
Rattach tag[2] fid[2] qid[8] rauth[13]
DESCRIPTION
The nop request does nothing overt but may be used to synchronize the channel between two service hosts initially.
The session request is used to initialize a connection between a client and a server. All outstanding I/O on the connection is aborted.
The set of messages between session requests is called a session. The host's user name (authid) and its authentication domain (authdom)
identify the key to be used when authenticating to this host. The exchanged challenges (chal) are used in the authentication algorithm.
If authid is a null string no authentication is performed in this session.
The tag should be NOTAG (value 0xFFFF) for a nop or session message.
The attach message serves as a fresh introduction from a user on the client machine to a server. The message identifies the user (uid) and
may select the file tree to access (aname). The ticket and auth arguments contains authorization data derived from the exchanged chal-
lenges of the session message; see auth(6).
As a result of the attach transaction, the client will have a connection to the root directory of the desired file tree, represented by
fid. An error is returned if fid is already in use. The server's idea of the root of the file tree is represented by the returned qid.
ENTRY POINTS
An attach transaction will be generated for kernel devices (see intro(3)) when a system call evaluates a file name beginning with Pipe(2)
generates an attach on the kernel device pipe(3). The mount system call (see bind(2)) generates an attach messages to the remote file
server. When the kernel boots, an attach is made to the root device, root(3), and then an attach is made to the requested file server
machine.
SEE ALSO auth(6)ATTACH(5)