Re: SIGTERM Error
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | tolj.org system architecture |
| Message-ID | <[email protected]> |
Carlos G. Pachas Boza schrieb:
> Hi, I'm implementing the 1,4,1 version and I got this error.
>
> It works ok for a while but suddenly it shutdown.
>
> Wapbox:
>
> 2008-06-14 18:50:51 [13855] [6] DEBUG: WTP: resp_machine 17897, state
> RESULT_WAIT, event RcvAbort.
> 2008-06-14 18:50:51 [13855] [6] DEBUG: WTP 17897: New state LISTEN
> 2008-06-14 18:50:51 [13855] [6] DEBUG: WTP: Destroying WTPRespMachine
> 0x8724c88 (17897)
> 2008-06-14 18:50:51 [13850] [1] DEBUG: WSP: machine 0x445efbb0, state
> CONNECTED, event TR-Abort.ind
> 2008-06-14 18:50:51 [13850] [1] DEBUG: WSP: method 17897, state
> PROCESSING, event TR-Abort.ind
> 2008-06-14 18:50:51 [13850] [1] DEBUG: WSP 597/17897: New method state
> NULL_METHOD
> 2008-06-14 18:50:51 [13850] [1] DEBUG: Destroying WSPMethodMachine 17897
> 2008-06-14 18:50:51 [13850] [1] DEBUG: WSP 597: New state CONNECTED
> 2008-06-14 18:50:51 [13843] [0] ERROR: SIGINT or SIGTERM received, let's
> die.
> 2008-06-14 18:50:51 [13843] [0] INFO: Kannel wapbox terminating.
> 2008-06-14 18:50:51 [13865] [15] DEBUG: Thread 15
> (gw/heartbeat.c:heartbeat_thread) terminates.
> 2008-06-14 18:50:51 [13843] [0] DEBUG: Waiting for 5
> (wap/wtp_init.c:main_thread) to terminate
> 2008-06-14 18:50:51 [13854] [5] DEBUG: Thread 5
> (wap/wtp_init.c:main_thread) terminates.
> 2008-06-14 18:50:51 [13843] [0] DEBUG: wtp_initiator_shutdown: 0
> init_machines left
> 2008-06-14 18:50:51 [13843] [0] DEBUG: Waiting for 6
> (wap/wtp_resp.c:main_thread) to terminate
>
> Bearerbox:
>
> 008-06-14 18:51:00 [13866] [12] DEBUG: send_msg: sending msg to box:
> <127.0.0.1>
> 2008-06-14 18:51:00 [13866] [12] DEBUG: boxc_sender: sent message to
> <127.0.0.1>
> 2008-06-14 18:51:00 [13866] [12] DEBUG: send_msg: sending msg to box:
> <127.0.0.1>
> 2008-06-14 18:51:00 [13866] [12] DEBUG: boxc_sender: sent message to
> <127.0.0.1>
> 2008-06-14 18:51:01 [13816] [0] WARNING: Killing signal or HTTP admin
> command received, shutting down...
> 2008-06-14 18:51:01 [13816] [0] DEBUG: Shutting down Kannel...
> 2008-06-14 18:51:01 [13816] [0] DEBUG: shutting down smsc
> 2008-06-14 18:51:01 [13816] [0] DEBUG: shutting down udp
> 2008-06-14 18:51:01 [13816] [0] DEBUG: udp_shutdown: Starting avalanche
> 2008-06-14 18:51:01 [13821] [4] DEBUG: Thread 4
> (gw/bb_udp.c:udp_receiver) terminates.
> 2008-06-14 18:51:01 [13823] [6] DEBUG: Thread 6
> (gw/bb_udp.c:udp_receiver) terminates.
>
> Somebody help me, please!
now, it's obvious what happens here: both processes get a SIGTERM signal and go
into shutdown phase.
So someone did INTEND to stop the processes by signaling them. This is no
"sudden dead" ;)
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------