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

List:       linux-diald
Subject:    Re: Trigger stops working after a pppd link abnormal failure
From:       rleggitt () concentric ! net
Date:       2000-08-14 18:09:58
[Download RAW message or body]

OK, I've seen this when I accidently turned the modem off. Triggers are
logged but pppd doesn't start. However the fifo 'up' command DOES work. 

Jul 28 17:20:52 shorty pppd[7524]: Hangup (SIGHUP)
Jul 28 17:20:52 shorty pppd[7524]: Modem hangup
Jul 28 17:20:52 shorty pppd[7524]: Connection terminated.
Jul 28 17:20:53 shorty pppd[7524]: Exit.
Jul 28 17:20:53 shorty diald[301]: Link died on remote end.
Jul 28 17:20:56 shorty diald[301]: start sl0: SIOCDELRT: No such process 
Jul 28 17:20:56 shorty diald[301]: stop ppp0: SIOCDELRT: No such process 
Jul 28 17:20:56 shorty diald[301]: stop ppp0: SIOCSIFFLAGS: Device not
configured 
Jul 28 17:22:56 shorty kernel: PPP: ppp line discipline successfully
unregistered
Jul 28 17:55:11 shorty diald[301]: Trigger: udp ...
(and nothing happened, so...)
Jul 28 17:56:21 shorty diald[301]: FIFO: link up request
Jul 28 17:56:21 shorty diald[301]: Calling site ...
Jul 28 17:56:22 shorty chat[7655]: abort on (NO CARRIER)
etc.

diald is in a wrong state, it could be interesting to put 'echo down >
diald.ctl' in ip-down.local??

== Rich

On Mon, 14 Aug 2000, Fergus McDonald wrote:

> Date: Mon, 14 Aug 2000 17:37:42 +0100
> From: Fergus McDonald <quantum@indigo.ie>
> To: "linux-diald@vger.rutgers.edu" <linux-diald@vger.rutgers.edu>
> Subject: Trigger stops working after a pppd link abnormal failure
> 
> I have found a few messages in the list archive about this, but no replies 
> to any of them. Maybe others having this problem could respond with their 
> distribution version and diald version, so we can see if there's a pattern 
> here.
> 
> What seems to happen [with my 0.99.3 on redhat 6.0 anyway] is everything is 
> going ok, but if the ppp link ends abnormally during a call, everything 
> seems to clean-up in the log ok, but diald logs subsequent triggers, but 
> doesn't proceed to try and dial the remote site.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to majordomo@vger.rutgers.edu
> 


-
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]