home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!dog.ee.lbl.gov!epb11.lbl.gov!envbvs
- From: envbvs@epb11.lbl.gov (Brian V. Smith)
- Newsgroups: comp.unix.ultrix
- Subject: Re: RPC can't encode arguments
- Date: 21 Dec 1992 16:51:29 GMT
- Organization: lbl
- Lines: 30
- Distribution: world
- Message-ID: <28098@dog.ee.lbl.gov>
- References: <28043@dog.ee.lbl.gov>
- NNTP-Posting-Host: 128.3.12.123
-
- Since I wrote that our Vaxstation is giving the error "RPC can't encode arguments",
- four people have responded that they too had gotten that error at one time, but
- they don't know what caused it and it eventually went away. They have suggested
- possible causes, but none has been the culprit. They suggested that:
-
- 1) Look for a problem with NFS, possibly permissions related.
-
- 2) DEC's elcsd is the one which produced the message since (he had reconfigured
- the elcsd.conf file)
-
- 3) RPC library on Ultrix prints that message when the destination hostname could
- not be translated into IP address. It should be "unknown host".
-
-
- Does anyone there at DEC have any idea what this error means and/or where it
- might be coming from?
-
- Here is my original post:
-
- |> Out of the blue one of our Vaxstation II's running Ultrix 4.2 is printing the
- |> following message on the console: RPC: can't encode arguments.
- |>
- |> It is not going into the syserr log file, just on the screen.
- |> I tried rebooting to no avail. Is there any way to know which program
- |> is causing this and why?
-
- --
- Brian V. Smith (bvsmith@lbl.gov)
- Lawrence Berkeley Laboratory
- I don't speak for LBL; they don't pay me enough for that.
-