03-06-2012
/var/log/messages error "kernel: RPC: bad TCP reclen"
Hi,
I am seeing the following errors in my environment, not sure why is it happening, any ideas? Thanks.
kernel: RPC: bad TCP reclen 0x73746174 (non-terminal ) Dec 17 02:14:48 kernel: RPC: bad TCP reclen 0x63480000 (large) Dec 17 02:14:48
kernel: RPC: bad TCP reclen 0x633f0000 (large) Dec 17 02:14:48
kernel: RPC: bad TCP reclen 0x1201001a (non-terminal
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have been running 5.0.02 for more than 10 years in its present configuration. I am running a business software package on it (text based).
I am trying to use my windows machines to access it through a program like "reflections" so that I can run my software from different systems but I get... (2 Replies)
Discussion started by: Parkegio
2 Replies
2. Shell Programming and Scripting
Hallo,
i need a Prompting read in my script:
read -p "Enter your command: " command
But i always get this Error:
-p: is not an identifier
When I run these in c-shell i get this error
/usr/bin/read: read: bad option(s)
How can I use a Prompt in the read command? (9 Replies)
Discussion started by: wiseguy
9 Replies
3. Shell Programming and Scripting
Hi All,
wen i am running a script . its giveing the below error and hanging there
Bad string
*******************
Please enter the following details one by one
---------------------------------------------
... (6 Replies)
Discussion started by: manoj_dahiya22
6 Replies
4. UNIX for Advanced & Expert Users
Hello group,
How can I separate "named daemon" messages to the other file instead of /var/adm/messages. I still want all other daemons log the messages to /var/adm/messages.
i.e.
named => /var/adm/named.message
other daemons => /var/adm/messages.
I searched unix.com, and google but I still... (5 Replies)
Discussion started by: dannytrinh
5 Replies
5. Solaris
I am getting the following error in the cron log:
! bad user (root) Wed Sep 22 14:30:00 2010
< root 8989 c Wed Sep 22 14:30:00 2010 rc=1
What does this mean? (5 Replies)
Discussion started by: jastanle84
5 Replies
6. Solaris
Hello I am having an issue with a server SUN FIRE T2000 (Solaris 10).
First of all the server didn't boot normaly so I did a full restoration of the file systems.
Now the server boot, most of the services are available (not all the services), but I keep on seeing
RPC: Rpcbind failure -... (4 Replies)
Discussion started by: feg
4 Replies
7. Solaris
Below is the error being repeated on my Solaris 9 Sun-Fire-V890 machine.
SAN team confirmed as everything is fine from their end. I did google and found that some people say its a known Oracle bug when you have Oracle 10G installed on your system but I kind of disagree with them. Please see below... (2 Replies)
Discussion started by: vikkash
2 Replies
8. AIX
I have searched many times but nothing found. Somebody help please :(:(:( (1 Reply)
Discussion started by: bobochacha29
1 Replies
9. Shell Programming and Scripting
Hi everybody,
I am new at Unix/Bourne shell scripting and with my youngest experiences, I will not become very old with it :o
My code:
#!/bin/sh
set -e
set -u
export IFS=
optl="Optl"
LOCSTORCLI="/opt/lsi/storcli/storcli"
($LOCSTORCLI /c0 /vall show | grep RAID | cut -d " "... (5 Replies)
Discussion started by: Subsonic66
5 Replies
rpc(n) Tnm Tcl Extension rpc(n)
__________________________________________________________________________________________________________________________________________________
NAME
rpc - A simple RPC protocol for Tcl applications.
_________________________________________________________________
DESCRIPTION
RPC COMMAND
rpc server port
Set up an RPC server listening an port port. This command returns a rpc handle that be used to register Tcl procs that will be
exported by a trivial RPC protocol on top of TCP. This RPC mechanism allows us to write cooperating scripts without worrying much
about the communication protocol.
rpc client host port
Connect to the RPC server running on host with port port. The returned client handle can be used to invoke an exported proc on the
server host.
rpc delete handle
Delete a server or a client RPC handle. All connections associated with the handle will be closed.
rpc register rpchandle proc
Export proc as an RPC callable proc using the server handle rpchandle. Only registered procs can be called by RPC clients.
rpc unregister rpchandle proc
Remove proc from the list of exported procs on server handle rpchandle.
rpc info [rpchandle]
Calling rpc info without any arguments returns a list of all rpc handles that have been created using the rpc server and rpc client
command. Info about a specific rpc file handle rpchandle is returned by using the optional argument. The result is a list contain-
ing the tcp file handle used for the communication and the list of registered commands for a rpc handle and a list of all files that
represent connections to an rpc server. This list is empty if rpchandle belongs to a rpc client.
rpc# [-async] proc arg1 arg2 ...
To invoke a remote procedure proc, use the same syntax as used with a local invocation preceeded by a client rpchandle. The result
of the remote procedure call will be returned or an error if the underlying communication channel signals errors. The -async options
can be used to invoke proc without waiting for it to complete. The async option will never return a result.
SEE ALSO
scotty(1), Tcl(n)
AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl>
Tnm rpc(n)