04-14-2009
protocol failure in circuit setup
Receiving the above error from an application. I narrowed it down to a problem with rsh. If the rsh command is issued too rapidly it fails intermittently.
Try this script on your linux box...
#!/bin/sh -f
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
do
echo $i
rsh `hostname` "echo $i" &
done
If you don't get the error right away, try running the script a few times in close succession.
I think the problem is with the /etc/xinetd.conf settings. Anyone know what flag or setting we have to tweek to avoid this problem?
Here's part of the output....
17
18
19
20
poll: protocol failure in circuit setup
poll: protocol failure in circuit setup
poll: protocol failure in circuit setup
poll: protocol failure in circuit setup
poll: protocol failure in circuit setup
poll: protocol failure in circuit setup
poll: protocol failure in circuit setup
1
17
9
16
13
6
Last edited by kevinl33; 04-14-2009 at 08:38 PM..
6 More Discussions You Might Find Interesting
1. AIX
I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it?
I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame.
Any help is appreciated. (1 Reply)
Discussion started by: pdtak
1 Replies
2. Homework & Coursework Questions
My problem is I need to control a 7 segment LED circuit (currently on a breadboard, eventually on a PCB). The only option I have from my PC is through USB. The circuit I have built on a breadboard uses 7 segment LED's and 4206 decade counters. I have cut a USB cable in half, and am using the... (2 Replies)
Discussion started by: bkhusky
2 Replies
3. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
4. Shell Programming and Scripting
Hello everyone,
just wondering if this type of if condition will execute properly.
Suppose I have a script with two functions in it called abc and def:
is this code valid, or is there a better way to short circuit the if statement?
#! /bin/ksh93
abc(){
statement 1 using $1
statement 2... (4 Replies)
Discussion started by: gio001
4 Replies
5. UNIX and Linux Applications
Hi all.
In some articles I have read about a "UNIX Circuit Design System", which was written originally in some version of
Research UNIX by Sandy Fraser.
Here is a quote from the article "A Research UNIX Reader: Annotated Excerpts from the Programmer's Manual", by Douglas McIlroy:
Even... (1 Reply)
Discussion started by: mghis
1 Replies
6. Answers to Frequently Asked Questions
Hi. i am new to Linux. i have a Turbo-cad and circuit wizard programme on CD that I want to install and run. I keep getting the message I do not have an auto-run programme. Do I need to install specific drivers for this? What programme do I need? (1 Reply)
Discussion started by: Alfred Kruger
1 Replies
LEARN ABOUT DEBIAN
mailping-success
2004-04-16
mailping
0.0.4
MAILPING-SUCCESS(1) Mailping MAILPING-SUCCESS(1)
NAME
mailping-success - Munin plugin to graph time since last mail delivery
SYNOPSIS
/usr/share/mailping/munin-plugins/mailping-success {[config] | ['']}
DESCRIPTION
mailping-success is a Munin plugin that monitors time passed since last successful email probe.
Configuration output
When passed config, it outputs Munin configuration information. If there are no circuits defined (no subdirectories in /etc/mailping), it
specifies that Munin should draw no graph either.
If configuration files /etc/mailping/circuit/warntime and /etc/mailping/circuit/failtime exist, the values in them are passed on to Munin,
for use in Nagios alert integration.
Value output
When passed an empty string '', mailping-success outputs the difference between current time and last successful probe, for each configured
circuit.
FILES
/etc/mailping/
List of circuits that exist; each subdirectory is a circuit.
/etc/mailping/circuit/warntime
If more than this many seconds have passed since last successful probe, a Nagios warning is triggered by Munin (assuming it has been
configured to do that). Default: no warnings.
/etc/mailping/circuit/failtime
If more than this many seconds have passed since last successful probe, a Nagios alert is triggered by Munin (assuming it has been
configured to do that). Default: no alerts.
/var/lib/mailping/state/circuit/success
Timestamp in seconds of the last successful probe for circuit.
ENVIRONMENT
MAILPING_CONFIGDIR
Override the location of the configuration directory. Default: /etc/mailping
MAILPING_STATEDIR
Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories
named after the circuit name. Default: /var/lib/mailping
SEE ALSO
mailping-latency(1), mailping-cron(1), mailping-store(1), munin-run(8), munin-node(8)
AUTHOR
Tommi Virtanen <tv@havoc.fi>
Havoc Consulting
Author.
COPYRIGHT
Copyright (C) 2004 Havoc Consulting
mailping 0. 2004-04-16 MAILPING-SUCCESS(1)