connecting problems (kppp)
 

I spent sometime trying to figure out what was happening before i asked here at the forum .since yesterday my kppp connection fails (almost) everytime i tried to connect , the error was :
bash-2.05# kppp
kppp: helperPid: 1018
kppp: found kppp.pid containing: 995
kppp:
---------------------------------------------
and the kppp window said :

"kppp has detected a /root/.kde/share/apps/kppp/kppp.pid file

another instance of kppp seemes to be running under process-ID 1074

make sure that you are not running another kppp,delete the pid file ,and restart kppp."

I did delete the pid file each time the message showed, and sometimes i could connect but most of them i couldn`t.
I also looked at the man pages and i found pid as being a "retrieve processs id(s)" .
i get different pid values ( 771,1774,1196,995,1018,etc...)each time i try to connect.
--------------------------------------------
my kppp process at command prompt:

kppp: Interface is down
kppp: if_waiting_timed_out()
kppp: sendRequest: trying to send msg type 10
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
kppp: recvResponse(): received message
kppp: response.status: 1
kppp: Received a SIGUSR1
kppp: It was pppd that died
kppp: sendRequest: trying to send msg type 7
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
kppp: recvResponse(): received message
kppp: response.status: 0
kppp: Executing command on disconnect since pppd has died.
kppp: sendRequest: trying to send msg type 4
kppp: sendRequest: sent message
kppp: response.status: 0
kppp: sendRequest: trying to send msg type 4
kppp: sendRequest: sent message
kppp: response.status: 0
kppp: UnLocking Modem Device
kppp: sendRequest: trying to send msg type 3
kppp: sendRequest: sent message
kppp: recvResponse(): waiting for message
kppp: recvResponse(): received message
kppp: response.status: 0
LD_LIBRARY_PATH=/opt/kde/lib
kdeinit: Launched DCOPServer, pid = 1082 result = 0
DCOPServer: SetAProc_loc: conn 0, prot=local, file=/tmp/.ICE-unix/1084
DCOP: register 'anonymous-1082' -> number of clients is now 1
DCOPServer up and running.
kdeinit: Launched KLauncher, pid = 1085 result = 0
DCOP: unregister 'anonymous-1082'
DCOP: number of clients is now down to 0
DCOP: register 'klauncher' -> number of clients is now 1
DCOP: new daemon klauncher
DCOP: register 'anonymous-1085' -> number of clients is now 1
DCOP: unregister 'anonymous-1085'
DCOP: number of clients is now down to 0
kdeinit: Launched KDED, pid = 1087 result = 0
DCOP: register 'kded' -> number of clients is now 1
kded: DCOP: register 'anonymous-1087' -> number of clients is now 2
Does not exist! (/root/.kde/share/servicetypes/)
DCOP: register 'anonymous-1088' -> number of clients is now 3
kio (KLauncher): KLauncher: Got kdeinit_exec_wait('kbuildsycoca', ...)
KInit: Got EXEC 'kbuildsycoca' from klauncher.
kio (KLauncher): kbuildsycoca (pid 1089) up and running.
DCOP: register 'kbuildsycoca' -> number of clients is now 4
kbuildsycoca: Recreating ksycoca file
kio (KSycoca): KSycocaDict: 150 entries.
kio (KSycoca): KSycocaDict: 59 entries.
kio (KSycoca): KSycocaDict: 4 entries.
kio (KSycoca): KSycocaDict: 456 entries.
kio (KSycoca): KSycocaDict: 456 entries.
kio (KSycoca): KSycocaDict: 456 entries.
kio (KSycoca): KSycocaDict: 13 entries.
kio (KSycoca): KSycocaDict: 30 entries.
kbuildsycoca: endOfData : 5b84d
kbuildsycoca: Build = 0s Save = 1s
kdeinit: PID 1089 terminated.
DCOP: unregister 'kbuildsycoca'
DCOP: number of clients is now down to 3
DCOP: unregister 'anonymous-1088'
DCOP: number of clients is now down to 2
DCOP: new daemon kded
kdeinit: PID 1087 terminated.
DCOP: unregister 'anonymous-1087'
DCOP: number of clients is now down to 0
kdeinit: opened connection to :0.0
DCOPServer : slotTerminate() -> sending terminateKDE signal.
klauncher: KLauncher::process ---> terminateKDE
kdeinit: terminate KDE.
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
DCOP: unregister 'klauncher'
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
DCOP: unregister 'kded'


sorry for the lenght of the thread :

1-can this be a hardware problem ?
2-I installed a firewall (firestarter).could it be interfering in anyway?
3-what does pid do ? does it appear only when there is a problem?

Have you tried any other dialup besides kppp to see if its clearly the program or connection, anything else that might be conflicting ? It could be your firewall but most likely not though.

Also, the pid is the process identification.. every process that is running has one. Most likely when its failing, the process isn't ending properly and that is why it tells you to kill the process so you can run it again since only one instance can run at any given time.

i tried gnome-ppp and i get connected but as soon as i start any browser it kills my connection.

i have a simple firewall setup :
-disabled ICMP fitering
-disabled service configuration
-disabled ToS filtering
-disabled masquerading

"Most likely when its failing, the process isn't ending properly and that is why it tells you to kill the process "

i just remember that two weeks ago there was a blackout while i was online . is it possible that some programs got damaged ? there were a message right after i switched the computer on that said something about running fsck2 or something and it also asked for my password . As i`m used to reinstall at slightest problem , i`m holding myself here not to go through all config steps again .

I reinstalled again everything first thing i did was set kppp and still i'm getting the same problem when i try to connect . any help would be apreciated .

To discart a hardware problem try with another modem.

Do you have installed or compiled a program by the time the problem begins?. If you have installed it, try removing the program.

Try connecting without the firewall.

Also in the log of kppp it have a line that says:
kppp: UnLocking Modem Device

the manpage of pppd says:
lock Specifies that pppd should create a UUCP-style lock
file for the serial device to ensure exclusive
access to the device.

So it can be that another process is trying to access the serial port.
Maybe a serial mouse?
check the BIOS configuration of the serial ports?

hope this help ^_^