|
Top Document: INN FAQ Part 5/9: Other error messages and what they mean Previous Document: (5.4) Why does my innd often die with the message "Can't sync history, interrupted system call" Next Document: (5.6) syslog msg: ME cant sendto CCreader bytes 4 No such file or directory See reader questions & answers on this topic! - Help others by sharing your knowledge
The socket sendto wants to write to isn't available. This can either
come from a dead server (e.g. send a ctlinnd shutdown twice) or from a
process (find -exec rm{} comes to mind) that removed the socket from
the filesystem.
Look after _PATH_NEWSCONTROL in config.data and find out if all components
of the path exist and are accessible. (inncheck could be of help ...)
This condition will occur whenever news.daily is run as root, leaving
the ownership of history, active, etc files as root. Change ownership
of these files back to news and then restart.
User Contributions:Comment about this article, ask questions, or add new information about this topic:Top Document: INN FAQ Part 5/9: Other error messages and what they mean Previous Document: (5.4) Why does my innd often die with the message "Can't sync history, interrupted system call" Next Document: (5.6) syslog msg: ME cant sendto CCreader bytes 4 No such file or directory 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 August 08 2012 @ 06:20 AM
|
