[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#72272: marked as done (Diald busy-loops)

Your message dated Thu, 7 May 2009 19:45:42 +0100
with message-id <200905071845.n47IjghA014553@kmos.homeip.net>
and subject line diald has been removed from Debian, closing #72272
has caused the Debian Bug report #72272,
regarding Diald busy-loops
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
72272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=72272
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: diald
Version: 0.99.1-1

Description:

Diald hangs (99%CPU) if there's a FIFO 'reset' command during the dial and
the connection fails with a hangup before the 'connect' script returns.

Info:

> Sep 22 23:53:22 mayday diald[205]: start sl0: SIOCSIFMETRIC: Operation not supported
> Sep 22 23:53:30 mayday diald[205]: Trigger: udp    212.229.197.73/1024 192.203.230.10/53
> Sep 22 23:53:30 mayday diald[205]: Calling site 10.0.0.0
> Sep 22 23:53:31 mayday diald[205]: FIFO: reset request received - re-reading configuration
This is in the connect script, I use it to dynamically decide on the protocol
that I'm going to use on this connection (slip or ppp). This in turn depends
on the system being called.

If I don't call the reset it appears (so far) that diald doesn't hang.
It doesn't seem to matter if it's ppp or slip.

> Sep 22 23:53:32 mayday connect: Calling ntl on 08005190100
The connect script has decided to call NTL.
It also adds a line to diald.log.

> Sep 22 23:53:53 mayday diald[205]: Connected to site 10.0.0.0
> Sep 22 23:56:05 mayday diald[205]: SIGHUP: modem got hung up on.
The connection failed
At this point it seems to be busy-looping (99% cpu)

I tried a kill -1 ...
> Sep 22 23:59:59 mayday diald[205]: SIGHUP: modem got hung up on.

I tried a kill -15 ...
> Sep 23 00:00:37 mayday diald[205]: SIGTERM. Termination request received.

I tried a kill -9 ...
... Yup that worked :-(

If I do the reset from ip-up there doesn't seem to be any problem so most
of the time that's what I do now.

I _guess_ that the modem port is giving an error or EOF to diald and 
diald doesn't notice and retries.

-- 
Rob.                          (Robert de Bath <http://poboxes.com/rdebath>)
                    <rdebath @ poboxes.com> <http://www.cix.co.uk/~mayday>

--- End Message ---
--- Begin Message --- 
Version: 0.99.4-9+rm

The diald package has been removed from Debian so we are closing
the bugs that were still opened against it.

For more information about this package's removal, read
http://bugs.debian.org/526512 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

Kind regards,
--
Marco Rodrigues

--- End Message ---
Reply to: