[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
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.13) news.daily reports: "Expire had problems removing articles"
Next Document: (5.15) syslog: ME cant nonblock 15 Operation not supported
-
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.13) news.daily reports: "Expire had problems removing articles"
Next Document: (5.15) syslog: ME cant nonblock 15 Operation not supported
(5.14) syslog: nnrpd[22560]: ? cant gethostbyaddr 198.3.24.3 Permission denied
When someone connects to nnrpd, nnrpd does a reverse lookup on the clients IP address so it can look up the hostname in nnrpd.access. If the client's DNS information is incorrect, you will get this error. Make sure your SOA record is correct, as well as your in-addr.arpa data. Derek <ddl@clipper.ssb.com> adds that another cause for this problem, at least under SunOS 4.1.x, is that nnrpd wasn't linked with the proper resolver library (statically or dynamically). Even when you've replaced Sun's fershlugger libresolv.a you've still gotta remind yourself to _use_ it properly.
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.13) news.daily reports: "Expire had problems removing articles"
Next Document: (5.15) syslog: ME cant nonblock 15 Operation not supported
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