Greetings - Since migrating to 7.1, I have an odd problem with my dial-on-demand setup using wvdial. When running fetchmail, the first server that gets contacted reports an error that a connection could not be made. The rest of the servers work fine and if I run fetchmail again, before the modem hangs up, the first server works fine. If I start wvdial manually, I don't get this same error message. And, if I start kppp, I don't have this problem. I looked at var/log/messages, but don't see anything that immediately jumps out at me as a problem. This is somewhat annoying. Any ideas on what I should be looking for? Thanks, Harry
Harry Reinert wrote:
Since migrating to 7.1, I have an odd problem with my dial-on-demand setup using wvdial. When running fetchmail, the first server that gets contacted reports an error that a connection could not be made. The rest of the servers work fine and if I run fetchmail again, before the modem hangs up, the first server works fine.
I could be wrong, but I bet the problem is in your phones or ISP. I have seen the exact same problem with our server (6.4), and if you check your logs, you may see busy or no carrier messages coming back from your modem. Fetchmail seems to try for so long on the first entry, then time out since the connection is not up, then move on to the next entry. What I usually do is call the dialup numbers (usually there is more then one), listen for line noise and clarity, and change the number (Yast or /etc/wvdial.conf). Many times the modem answers but doesn't send any carrier. I doubt your fetchmail or dial on demand are to fault.
If I start wvdial manually, I don't get this same error message. And, if I start kppp, I don't have this problem.
This is because the connection is made first. If it dials on demand, wvdial.dod is OK. The above proves fetchmail is OK. It is more than likely the less than perfect PSTN or perhaps some bad modems in your ISPs modem pool. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris "All I have seen teaches me to trust the Creator for all I have not seen." --Ralph Waldo Emerson
On Mon, Jun 04, 2001 at 10:24:30PM -0700, Harry Reinert wrote:
Since migrating to 7.1, I have an odd problem with my dial-on-demand setup using wvdial. When running fetchmail, the first server that gets contacted reports an error that a connection could not be made. The rest of the servers work fine and if I run fetchmail again, before the modem hangs up, the first server works fine.
If I start wvdial manually, I don't get this same error message. And, if I start kppp, I don't have this problem.
I looked at var/log/messages, but don't see anything that immediately jumps out at me as a problem. This is somewhat annoying. Any ideas on what I should be looking for?
It's just that fetchmail is timing out on the first mailserver. The modem takes a certain amount of time to dialup. If there are problems, or you just take longer than usual to connect, then fetchmail may time out on the first server before the connection is fully up. What I sometimes do (to speed up the fetchmail retrieval) is run fetchmail, wait until I think the connection is up, then abort and re-run fetchmail. Normally is gets stuck on the DNS lookups for me (because I run a caching DNS server, it's waiting for a reply from the local DNS, so as far as it's concerned the connection is up). It's nothing to worry about, if slightly annoying. Either do something like I do, or ping google or somewhere a short while before running fetchmail - that'll do the trick too. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
participants (3)
-
Chris Reeves -
Harry Reinert -
Joe Morris