[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
    Search the FAQ Archives

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.2) Bad file number writing history file -- throttling
Next Document: (5.4) Why does my innd often die with the message "Can't sync history, interrupted system call"


(5.3) log file fills with " 436 No space"


innd issues this message if it cannot create a directory for a group,
_no matter what the reason for the failure_.  In most cases,
/usr/spool/news (and the mount point it is symlinked to, if any)
accidentally has permissions and ownerships that do not permit write
access by innd (which runs as "news").  After chowning them to news,
and setting the permissions to 755, everything should work fine.



Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.2) Bad file number writing history file -- throttling
Next Document: (5.4) Why does my innd often die with the message "Can't sync history, interrupted system call"

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page


[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)

Last Update October 22 2009 @ 05:35 AM

Some parts © 2009 Advameg, Inc.