[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-diald
Subject:    diald 0.99.3 stopped dialling out after a few days working ok
From:       Fergus McDonald <quantum () indigo ! ie>
Date:       2000-08-10 11:30:26
[Download RAW message or body]

Have Redhat 6.0 dist, with diald 0.99.3

Everything was running pretty much fine for a few days.. then one morning 
we found no dial-outs taking place. The log showed diald logging triggers, 
and diald-top was showing packets waiting in the queue and expiring, but no 
sign of any attempt to run the connect script. Tracing back through the 
log, it looks like it stopped working after the line dropped during running 
the connect sequence. I have DNS running locally.

Here's the log:

Aug  9 05:56:02 xeon diald[8372]: Trigger: tcp      192.168.64.2/62349 
   128.32.18.166/80
Aug  9 05:56:02 xeon diald[8372]: Calling site 194.125.145.104
Aug  9 05:56:03 xeon connect: Initializing Modem
Aug  9 05:56:04 xeon connect: Dialing system
Aug  9 05:56:39 xeon connect: Connected
Aug  9 05:56:39 xeon connect: Loggin in
Aug  9 05:56:40 xeon connect: Starting Comm Protocol
Aug  9 05:56:41 xeon diald[8372]: connector: /usr/lib/diald/connectisp: [: 
to: binary operator expected
Aug  9 05:56:41 xeon connect: Protocol started
Aug  9 05:56:41 xeon diald[8372]: Connected to site 193.121.145.104
Aug  9 05:56:41 xeon diald[8372]: Running pppd (pid = 9413).
Aug  9 05:56:43 xeon kernel: PPP: version 2.3.3 (demand dialling)
Aug  9 05:56:43 xeon kernel: PPP line discipline registered.
Aug  9 05:56:43 xeon kernel: registered device ppp0
Aug  9 05:56:43 xeon pppd[9413]: pppd 2.3.7 started by root, uid 0
Aug  9 05:56:43 xeon pppd[9413]: Using interface ppp0
Aug  9 05:56:43 xeon pppd[9413]: Connect: ppp0 <--> /dev/ttyS0
Aug  9 05:56:46 xeon modprobe: can't locate module ppp-compress-21
Aug  9 05:56:47 xeon modprobe: can't locate module ppp-compress-26
Aug  9 05:56:47 xeon modprobe: can't locate module ppp-compress-24
Aug  9 05:56:47 xeon pppd[9413]: local  IP address 193.121.207.47
Aug  9 05:56:47 xeon pppd[9413]: remote IP address 193.121.145.171
Aug  9 05:56:48 xeon diald[8372]: New addresses: local 193.121.207.47, 
remote 194.125.145.171, broadcast 0.0.0.0
Aug  9 05:56:48 xeon diald[8372]: start ppp0: SIOCSIFMETRIC: Operation not 
supported

so far so good.. then diald runs a script of mine to sync the clock with 
chronyd and do some pop3 pickups. However, in the middle of this, pppd 
seems to report a hangup and terminates. Then diald seems to try and stop 
ppp (the lines starting with ***). After this, my ip-up script continues to 
run with the fetchmail/chronyd stuff which fails, and about 10 mins later, 
a ppp unregistering msg is logged (which is prolly about the time diald 
should be timing out the link). And after that, triggers logged, but no 
action..

Aug  9 05:56:49 xeon diald[8372]: running ip-up script '/etc/getourmail 
'ppp0' '255.255.255.255' '193.121.207.47' '193.121.145.171''
Aug  9 05:56:50 xeon chronyd[8053]: Source 134.226.81.3 online
Aug  9 05:56:50 xeon chronyd[8053]: Source 130.235.20.3 online
Aug  9 05:56:50 xeon diald[8372]: ip-up: 200 OK
Aug  9 05:56:50 xeon diald[8372]: ip-up: 200 OK
Aug  9 05:57:01 xeon pppd[9413]: Hangup (SIGHUP)
Aug  9 05:57:01 xeon pppd[9413]: Modem hangup
Aug  9 05:57:01 xeon pppd[9413]: Connection terminated.
Aug  9 05:57:01 xeon pppd[9413]: Connect time 0.3 minutes.
Aug  9 05:57:01 xeon pppd[9413]: Sent 589 bytes, received 158 bytes.
Aug  9 05:57:02 xeon pppd[9413]: Exit.
Aug  9 05:57:02 xeon diald[8372]: Link died on remote end.
Aug  9 05:57:02 xeon diald[8372]: start sl0: SIOCSIFMETRIC: Operation not 
supported
***Aug  9 05:57:03 xeon diald[8372]: stop ppp0: SIOCDELRT: No such process
***Aug  9 05:57:03 xeon kernel: ppp: ppp0 not active
***Aug  9 05:57:03 xeon diald[8372]: stop ppp0: SIOCSIFFLAGS: Device not 
configured
***Aug  9 05:57:03 xeon diald[8372]: Closing /dev/ttyS0
Aug  9 05:58:16 xeon diald[8372]: ip-up: fetchmail: POP3 connection failed: 
temporary name server error
Aug  9 05:58:16 xeon diald[8372]: ip-up: fetchmail: Query status=2
Aug  9 05:59:44 xeon diald[8372]: ip-up: fetchmail: POP3 connection failed: 
temporary name server error
Aug  9 05:59:44 xeon diald[8372]: ip-up: fetchmail: Query status=2
Aug  9 06:01:17 xeon diald[8372]: ip-up: fetchmail: POP3 connection failed: 
temporary name server error
Aug  9 06:01:17 xeon diald[8372]: ip-up: fetchmail: Query status=2
Aug  9 06:05:28 xeon chronyd[8053]: Selected source 130.235.20.3
Aug  9 06:10:01 xeon kernel: PPP: ppp line discipline successfully 
unregistered
Aug  9 07:00:05 xeon diald[8372]: Trigger: udp      192.168.64.2/1024 
     128.218.14.2/53
Aug  9 08:04:14 xeon diald[8372]: Trigger: udp      192.168.64.2/1024 
     128.218.14.2/53
Aug  9 09:08:37 xeon diald[8372]: Trigger: udp      192.168.64.2/1024 
     128.218.14.2/53


Is this a known problem or does it require investigation?

Regards

Fergus


-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to majordomo@vger.rutgers.edu

[prev in list] [next in list] [prev in thread] [next in thread]