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

Bug#291461: marked as done (kppp: wrong error messages on failure)



Your message dated Tue, 27 Mar 2007 11:25:02 -0400
with message-id <9f694b820703270825t558a4cfeu2e945af025696817@mail.gmail.com>
and subject line Old bug, do you still have the problem ?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: kppp
Version: 4:3.3.1-2
Severity: minor

Because of some temporary problem at my ISP, I was recently unable to
connect.  kppp would dial up and then disconnect shortly after
connecting.  The details button showed an error message complaining
about being unable to write to /var/log/syslog, ppp.log, and one other
logfile that I can't remember.

This happened several times.

However, the logfiles were being written to, and showed this
information:
Jan 20 12:12:34 wheat pppd[3758]: pppd 2.4.2 started by ross, uid 1000
Jan 20 12:12:34 wheat pppd[3758]: Using interface ppp0
Jan 20 12:12:34 wheat pppd[3758]: Connect: ppp0 <--> /dev/tts/0
Jan 20 12:12:35 wheat pppd[3758]: PAP authentication succeeded
Jan 20 12:12:35 wheat pppd[3758]: kernel does not support PPP filtering
Jan 20 12:12:37 wheat pppd[3758]: LCP terminated by peer
Jan 20 12:12:40 wheat pppd[3758]: Connection terminated.
Jan 20 12:12:40 wheat pppd[3758]: Exit.

The "terminated by peer" message means, I think, that the problem was
at the other end--nothing to do with writing to local files.

Because the problem at the ISP has been fixed, I can no longer
reproduce this failure.  I realize this may make it hard to track
down, but it seems likely some of the error handling code is getting
confused.

As the error message directs attention toward a completely different
source than the true error, it's a bit of a problem.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kppp depends on:
ii  kdelibs4                 4:3.3.1-4       KDE core libraries
ii  libart-2.0-2             2.3.16-6        Library of functions for 2D graphi
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries an
ii  libfam0c102              2.7.0-6         client library to control the FAM 
ii  libgcc1                  1:3.4.3-6       GCC support library
ii  libice6                  4.3.0.dfsg.1-10 Inter-Client Exchange library
ii  libidn11                 0.5.2-3         GNU libidn library, implementation
ii  libpng12-0               1.2.8rel-1      PNG library - runtime
ii  libqt3c102-mt            3:3.3.3-7       Qt GUI Library (Threaded runtime v
ii  libsm6                   4.3.0.dfsg.1-10 X Window System Session Management
ii  libstdc++5               1:3.3.5-5       The GNU Standard C++ Library v3
ii  libx11-6                 4.3.0.dfsg.1-10 X Window System protocol client li
ii  libxext6                 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii  libxrender1              0.8.3-7         X Rendering Extension client libra
ii  xlibs                    4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu
ii  zlib1g                   1:1.2.2-3       compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Submitter was asked to provide more information about this bug
( http://bugs.debian.org/291461 ) four weeks ago.

Since more info was not provided, we are closing the bug.
Feel free to reopen this bug if you are still experiencing this issue
and you have extra information on how reproduce the issue.

Thanks,
Olivier

--- End Message ---

Reply to: