/var/log/messages error "kernel: RPC: bad TCP reclen" Post: 302614785

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO UNIX "TCP/IP not licensed error"

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. Shell Programming and Scripting

read -p "prompt text" foo say "read: bad option(s)" in Bourne-Shell

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?

3. Shell Programming and Scripting

Error-- : " bad string"

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 --------------------------------------------- ...

4. UNIX for Advanced & Expert Users

separate "named daemon" message from /var/adm/messages

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. Solaris

"! bad user (root)" in cron log

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?

6. Solaris

Error : "RPC: Rpcbind failure - RPC: Timed out"

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 -...

7. Solaris

Repeated error - "se_hdlc: clone device must be attached before use" in /var/adm/messages

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...

8. AIX

How to enable "TCP MD5 Signatures" and "https" on AIX?

I have searched many times but nothing found. Somebody help please :(:(:(

9. Shell Programming and Scripting

Failure: if grep "$Var" "$line" inside while read line loop

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 " "...

LEARN ABOUT DEBIAN

kumoctl

KUMOCTL(1)						      General Commands Manual							KUMOCTL(1)

NAME

       kumoctl - show kumofs status

SYNOPSIS

       kumoctl address[:port=19750] command [options]

DESCRIPTION

       Show status of kumo-manager and send control commands to kumo-manager.

COMMANDS

       status show status of the cluster

       attach attach all new servers and start replace

       attach-noreplace
	      attach all new servers

       detach detach all fault servers and start replace

       detach-noreplace
	      detach all fault servers

       replace
	      start replace without attach/detach

       full-replace
	      start full-replace (repair consistency)

       backup [suffix=20090304]
	      create backup with specified suffix

       enable-auto-replace
	      enable auto replace

       disable-auto-replace
	      disable auto replace

STATUS

       hash space timestamp
	      The  time  that the list of attached kumo-servers is updated. It is updated when new kumo-server is added or existing kumo-server is
	      down.

       attached node
	      The list of attached kumo-servers. (active) is normal node and (fault) is fault node or recoverd but not re-attached node.

       not attached node
	      The list of recognized but not-attached nodes.

AUTO REPLACING

       By default, you have to attach new kumo-servers manually using kumoctl command. If the auto replacing  is  enabled,  new  kumo-servers  are
       attached automatically.	This is experimental feature.

EXAMPLE

       $ kumoctl mgr1 status

       $ kumoctl mgr1 attach

SEE ALSO

       kumo-manager(1).

kumoctl 							     July 2009								KUMOCTL(1)