innfeed not propagating articles
Steven L. Sesar
ssesar at rcn.com
Sat Dec 15 19:46:24 UTC 2001
> Is this sporadic? That is, do any articles ever get to that peer?
No.
> Hmm...things to check:
>
> - is your innfeed.conf right
pid-file: innfeed.pid # relative to pathrun
debug-level: 0
use-mmap: false
log-file: innfeed.log # relative to pathlog
stdio-fdmax: 0
backlog-directory: innfeed # relative to pathspool
backlog-rotate-period: 60
backlog-ckpt-period: 30
backlog-newfile-period: 600
dns-retry: 900
dns-expire: 86400
close-period: 3600
gen-html: false
status-file: innfeed.status # relative to pathlog
connection-stats: false
host-queue-highwater: 200
stats-period: 600
stats-reset: 43200
max-reconnect-time: 3600
initial-reconnect-time: 30
article-timeout: 600
response-timeout: 300
initial-connections: 1
max-connections: 1
min-queue-connection: false
max-queue-size: 25
streaming: true
no-check-high: 95.0
no-check-low: 90.0
no-check-filter: 50.0
port-number: 119
backlog-factor: 2.0
backlog-limit-highwater: 0
dynamic-method: 3
dynamic-backlog-filter: 0.7
dynamic-backlog-low: 25.0
dynamic-backlog-high: 50.0
no-backlog: false
drop-deferred: true
## Peers.
## Group peers together to give second level defaults.
group fast-sites {
max-connections: 10
peer agate {
ip-name: mitre-in.news.berkeley.edu
}
peer newslocal {
ip-name: newslocal.mitre.org
}
peer world {
ip-name: news-f.std.com
}
}
> - does the article appear in ~news/log/news on the remote server
No!
More information about the inn-workers
mailing list