home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!ALW.NIH.GOV!rdew
- From: rdew@ALW.NIH.GOV (Bob Dew)
- Newsgroups: comp.soft-sys.andrew
- Subject: AMDS problem
- Message-ID: <YectBDy0ts4j4x9VAw@alw.nih.gov>
- Date: 1 Sep 92 15:59:11 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 51
-
-
- Since building Andrew 5.1 on sun4c_41 running afs31b, we've been
- experiencing frequent, but sporadic problems in reading new mail from a
- user's home-area Mailbox.
-
- When attempting to read new mail, a pop-up window reports, "Messages in
- /afs/alw.nih.gov/dcrt/userid_here/Mailbox could not be properly read and
- delivered (0 successes, 0 failures (0 locked, 0 in progress))". The
- message window at the bottom of the screen says, "Error: Bogus return
- from system call (in system in ProcessNewMesssages)".
-
- When this problem occurs, the user's setup appears fine--tokens are
- present, quotas are well below limits, etc. What's odd, though, is that
- the occurrence of this problem is linked to a host, rather than to a
- specific user. That is, when one user experiences difficulty reading
- new mail from a particular workstation, everybody who logs into that
- workstation sees the same problem. Yet the workstation setup looks
- normal. Many different workstations (all with nearly identical setups)
- have been experiencing this problem.
-
- An automatic bug report generated from messages on a disfunctioning
- workstation consistently shows only one peculiarity: a warning always
- indicates the presence of an open messages file in /tmp, as shown below:
-
- Here are the open files known to the file descriptor plumber:
-
- ----------------------------------------
-
- <warning:fdplumb>File '/tmp/oecs5xi0ts190kEU85' (opened by fopen) is
- still open.
-
- <warning:fdplumb>Total of 1 open files.
-
-
- Oddly, a directory listing of /tmp shows no such file, which leads one
- to believe that messages is attempting to use /tmp for some sort of
- temporary storage during new mail processing, and that the transaction
- is unsuccessful.
-
- This problem persists for hours or days at a time, then disappears.
-
- If anyone has clue what might be causing this problem, we'd be very
- grateful for some help.
-
-
- Thanks,
-
- Bob Dew
- National Institutes of Health
- Bethesda, MD 20892
- (301) 496-5361
-