Locating cause of signal
I'm having a problem with a signal, (SIGHUP), killing a running daemon, pppd! How do I find the cause of the signal, so I can stop it from happening??? I have tried debugging my connection, and nothing jumps out. Everything is clean around the timeframe of the signal. I have tried strace, yet within the time I need to trace, I would have over 65,000 lines of output. MTIA Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
On Wednesday 24 September 2003 12:13 pm, Bernd wrote:
I'm having a problem with a signal, (SIGHUP), killing a running daemon, pppd!
How do I find the cause of the signal, so I can stop it from happening???
That's the normal signal PPPD gives when the line drops... Sep 2 19:51:04 linux1 pppd[333]: Hangup (SIGHUP) Sep 2 19:51:04 linux1 pppd[333]: Modem hangup Sep 2 19:51:04 linux1 pppd[333]: Connection terminated. Sep 2 19:51:04 linux1 pppd[333]: Connect time 330.6 minutes. Sep 2 19:51:04 linux1 pppd[333]: Sent 5106937 bytes, received 15273290 bytes. Sep 2 19:51:04 linux1 pppd[333]: Script /etc/ppp/ip-down finished (pid 16694), status = 0x0 Sep 2 19:51:15 linux1 chat[16718]: report (CONNECT) Sep 2 19:51:15 linux1 chat[16718]: timeout set to 60 seconds Sep 2 19:51:15 linux1 chat[16718]: send (ATZ^M) Sep 2 19:51:15 linux1 chat[16718]: expect (OK) Sep 2 19:51:15 linux1 chat[16718]: ^M Sep 2 19:51:15 linux1 chat[16718]: NO CARRIER^M My line has been a bit flakey lately but the connect times run from 23 mins to 1184 mins so it's just line drop.
I have tried debugging my connection, and nothing jumps out. Everything is clean around the timeframe of the signal. I have tried strace, yet within the time I need to trace, I would have over 65,000 lines of output.
MTIA
Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea."
Antoine de St. Exupery
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/24/03 14:54 + +----------------------------------------------------------------------------+ "To make tax forms true they should read 'Income Owed Us' and Incommode You'."
On Wednesday, 24 September, 2003 11:56, Bruce Marshall wrote:
On Wednesday 24 September 2003 12:13 pm, Bernd wrote:
I'm having a problem with a signal, (SIGHUP), killing a running daemon, pppd!
How do I find the cause of the signal, so I can stop it from happening???
That's the normal signal PPPD gives when the line drops...
Sep 2 19:51:04 linux1 pppd[333]: Hangup (SIGHUP) Sep 2 19:51:04 linux1 pppd[333]: Modem hangup Sep 2 19:51:04 linux1 pppd[333]: Connection terminated. Sep 2 19:51:04 linux1 pppd[333]: Connect time 330.6 minutes. Sep 2 19:51:04 linux1 pppd[333]: Sent 5106937 bytes, received 15273290 bytes. Sep 2 19:51:04 linux1 pppd[333]: Script /etc/ppp/ip-down finished (pid 16694), status = 0x0
Same thing, yet as quick as 30 seconds, and NEVER longer than 59.4 minutes. I have delved as far as I can. ********** How can I find out -where- the (SIGHUP) is coming from, OR the -cause- of the (SIGHUP)???? ********** Thanks, Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
* Bernd (bernd@covenantmail.net) [030924 12:14]:
How can I find out -where- the (SIGHUP) is coming from, OR the -cause- of the (SIGHUP)????
Most likely from the program/script that started pppd. You can turn debugging by sending pppd a SIGUSR1. -- -ckm
On Wednesday 24 September 2003 15:14 pm, Bernd wrote:
On Wednesday, 24 September, 2003 11:56, Bruce Marshall wrote:
On Wednesday 24 September 2003 12:13 pm, Bernd wrote:
I'm having a problem with a signal, (SIGHUP), killing a running daemon, pppd!
How do I find the cause of the signal, so I can stop it from happening???
That's the normal signal PPPD gives when the line drops...
Sep 2 19:51:04 linux1 pppd[333]: Hangup (SIGHUP) Sep 2 19:51:04 linux1 pppd[333]: Modem hangup Sep 2 19:51:04 linux1 pppd[333]: Connection terminated. Sep 2 19:51:04 linux1 pppd[333]: Connect time 330.6 minutes. Sep 2 19:51:04 linux1 pppd[333]: Sent 5106937 bytes, received 15273290 bytes. Sep 2 19:51:04 linux1 pppd[333]: Script /etc/ppp/ip-down finished (pid 16694), status = 0x0
Same thing, yet as quick as 30 seconds, and NEVER longer than 59.4 minutes. I have delved as far as I can.
********** How can I find out -where- the (SIGHUP) is coming from, OR the -cause- of the (SIGHUP)???? **********
A SIGHUP is the signal used when you want a process to restart. Such as: killall -HUP inetd would cause inetd to restart (and re-read its /etc/inetd.conf file) I'm not sure on this but pppd may be giving itself a SIGHUP when the line drops if you have the PERSIST option set, which means that pppd will restart itself and dial again.
Thanks,
Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea."
Antoine de St. Exupery
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/24/03 15:23 + +----------------------------------------------------------------------------+ "You simply cannot understand psychedelic drugs, which activate the brain, unless you understand something about computers." - Timothy Leary
On Wednesday, 24 September, 2003 12:25, Bruce Marshall wrote: <snip>
********** How can I find out -where- the (SIGHUP) is coming from, OR the -cause- of the (SIGHUP)???? **********
A SIGHUP is the signal used when you want a process to restart. Such as:
killall -HUP inetd
would cause inetd to restart (and re-read its /etc/inetd.conf file)
I'm not sure on this but pppd may be giving itself a SIGHUP when the line drops if you have the PERSIST option set, which means that pppd will restart itself and dial again.
I don't have the persist option set in pppd options. This is coming out of the ether, as far as I can tell. This is why I need to find out how to backtrack -where- the signal is coming from. Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
On Friday 26 September 2003 3:17 am, Bernd wrote:
On Wednesday, 24 September, 2003 12:25, Bruce Marshall wrote: <snip>
********** How can I find out -where- the (SIGHUP) is coming from, OR the -cause- of the (SIGHUP)???? **********
A SIGHUP is the signal used when you want a process to restart. Such as:
killall -HUP inetd
would cause inetd to restart (and re-read its /etc/inetd.conf file)
I'm not sure on this but pppd may be giving itself a SIGHUP when the line drops if you have the PERSIST option set, which means that pppd will restart itself and dial again.
I don't have the persist option set in pppd options. This is coming out of the ether, as far as I can tell. This is why I need to find out how to backtrack -where- the signal is coming from.
I doubt very much if a random SIGHUP is being sent from anywhere. I think it comes from pppd itself for whatever reason and I think your line is just dropping... for some unknown reason. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/26/03 11:58 + +----------------------------------------------------------------------------+ "What this country needs is a dime that will buy a good five-cent bagel."
On Wednesday 24 September 2003 12:13 pm, Bernd wrote:
I'm having a problem with a signal, (SIGHUP), killing a running daemon, pppd!
How do I find the cause of the signal, so I can stop it from happening???
I have tried debugging my connection, and nothing jumps out. Everything is clean around the timeframe of the signal. I have tried strace, yet within the time I need to trace, I would have over 65,000 lines of output.
Ya know... I've been watching you struggle with this and I must give you a heck of a lot of credit for keeping at it. I am sure you'll get it working. I can't help you with kppp (never use it) but if you want to get down to the nitty gritty and just use pppd, you'll find it isn't that hard. (and you'll have more control) Be glad to help on that. And BTW, one thing I almost always do with a new release is to rename /etc/ppp/options. Seems that it does more harm than good.
MTIA
Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea."
Antoine de St. Exupery
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/24/03 15:00 + +----------------------------------------------------------------------------+ "Chateau Microsoft '95: also known as vintage "whines."
participants (3)
-
Bernd -
Bruce Marshall -
Christopher Mahmood