On Mon, 25 Nov 2002 11:13:25 +0000 Len Lawrence <[EMAIL PROTECTED]> wrote: > ----------- snip ------------- > every now and again, usually at intervals of a couple of days, the pppd > daemon launches after a connection has been successfully negotiated > but then spews out a constant stream of "ppp0 interface not found" > type messages. This is probably kppp going into a loop. After that > kppp (for instance) has to be killed, but even root cannot stop pppd, > which has status D in a gtop listing. It is then impossible to > reestablish an internet connection without rebooting. Rebooting > through the user interface does not work when this problem occurs. > The closedown sequence starts but the system covers the screen with a > repeating pattern of some sort and hangs completely - so hit the reset > button. Sometimes the Alt SysRq recovery sequence (rseiub) works, > sometimes it does not (press the reset button). So what gives? Is > 8.2 known to be unstable with respect to PPP? How do you recover > ppp0? What is the ppp0 interface?
Further to this, the following two excerpts from the terminal sessions show the difference between a successful connection and the no ppp0 interface situation. Can't make any sense of the second case - it is obviously totally different from the first. Both sessions were invoked with kppp & in a Gnome terminal (Gnome 1.4 + Sawfish). All that KDE stuff is very puzzling, and then there is the ICE message at the end! Good: [lcl@localhost ~]$ Opener: received OpenLock Opener: received OpenDevice Opener: received ExecPPPDaemon In parent: pppd pid 3148 Couldn't find interface ppp0: No such device Kernel supports ppp alright. Opener: received OpenResolv Opener: received OpenResolv Opener: received OpenResolv Opener: received RemoveSecret Opener: received RemoveSecret Opener: received KillPPPDaemon In killpppd(): Sending SIGTERM to 3148 Opener: received RemoveSecret Opener: received RemoveSecret Opener: received OpenResolv Opener: received OpenResolv Opener: received RemoveLock It was pppd that died pppd exited with return value 5 Sending 3144 a SIGUSR1 Bad: [lcl@localhost ~]$ QToolBar::QToolBar main window cannot be 0. Opener: received OpenLock Opener: received OpenDevice Opener: received RemoveLock kdeinit: Launched DCOPServer, pid = 2996 result = 0 DCOP: register 'anonymous-2996' -> number of clients is now 1 DCOPServer up and running. DCOP: unregister 'anonymous-2996' kdeinit: Launched KLauncher, pid = 3000 result = 0 DCOP: register 'klauncher' -> number of clients is now 1 DCOP: unregister 'klauncher' DCOP: register 'klauncher' -> number of clients is now 1 DCOP: register 'anonymous-3000' -> number of clients is now 2 DCOP: new daemon klauncher DCOP: unregister 'anonymous-3000' DCOP: register 'kded' -> number of clients is now 1 DCOP: unregister 'kded' kdeinit: Launched KDED, pid = 3003 result = 0 DCOP: register 'kded' -> number of clients is now 1 DCOP: register 'anonymous-3003' -> number of clients is now 2 DCOP: register 'anonymous-3004' -> number of clients is now 3 kdeinit: Got EXEC_NEW 'kbuildsycoca' from launcher. DCOP: register 'kbuildsycoca' -> number of clients is now 4 kdeinit: PID 3005 terminated. DCOP: unregister 'kbuildsycoca' DCOP: unregister 'anonymous-3004' kdeinit: Got EXEC_NEW 'kconf_update' from launcher. kdeinit: PID 3006 terminated. DCOP: new daemon kded kdeinit: PID 3003 terminated. kdeinit: opened connection to :0.0 DCOP: unregister 'anonymous-3003' DCOPServer : slotTerminate() -> sending terminateKDE signal. kdeinit: terminate KDE. kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. KLauncher: Exiting on signal 1 DCOP: unregister 'klauncher' kdeinit: sending SIGTERM to children. kdeinit: Exit. ICE default IO error handler doing an exit(), pid = 3004, errno = 2 [2] Exit 1 kppp Will have another go with gnome-ppp and see if any messages can be retrieved. Previously the system locked up completely after gnome-ppp (or whatever) failed. ------------ Len Lawrence
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
