Hi, Someone manually issued a:
pkill -HUP bearerbox When bearerbox receives such a signal it reopens logs. This is used to rotate them. It's all in the User's guide. How to avoid it? Do not send it. BR, Nikos ----- Original Message ----- From: Elton Hoxha To: kannel users Sent: Thursday, November 05, 2009 6:46 PM Subject: log clarification hi guys, I faced some strange behaviour, logs were not written for about 13 minutes, then started again independedly. 2009-11-05 17:26:25 [8000] [6] DEBUG: SMPP[gprs-bill]: Sending PDU: 2009-11-05 17:26:25 [8000] [6] DEBUG: SMPP PDU 0x9913760 dump: 2009-11-05 17:26:25 [8000] [6] DEBUG: type_name: deliver_sm_resp 2009-11-05 17:26:25 [8000] [6] DEBUG: command_id: 2147483653 = 0x80000005 2009-11-05 17:26:25 [8000] [6] DEBUG: command_status: 0 = 0x00000000 2009-11-05 17:26:25 [8000] [6] DEBUG: sequence_number: 24 = 0x00000018 2009-11-05 17:26:25 [8000] [6] DEBUG: message_id: NULL 2009-11-05 17:26:25 [8000] [9] DEBUG: send_msg: sending msg to box: <10.1.5.26> 2009-11-05 17:26:25 [8000] [6] DEBUG: SMPP PDU dump ends. 2009-11-05 17:26:25 [8000] [9] DEBUG: boxc_sender: sent message to <10.1.5.26> 2009-11-05 17:26:25 [8000] [8] DEBUG: boxc_receiver: got ack 2009-11-05 17:26:53 [8000] [6] DEBUG: SMPP[gprs-bill]: Sending enquire link: 2009-11-05 17:39:47 [8000] [6] DEBUG: SMPP PDU 0xb2400468 dump: 2009-11-05 17:39:47 [8000] [0] WARNING: SIGHUP received, catching and re-opening logs 2009-11-05 17:39:47 [8000] [6] DEBUG: type_name: enquire_link 2009-11-05 17:39:47 [8000] [6] DEBUG: command_id: 21 = 0x00000015 2009-11-05 17:39:47 [8000] [6] DEBUG: command_status: 0 = 0x00000000 2009-11-05 17:39:47 [8000] [6] DEBUG: sequence_number: 53 = 0x00000035 2009-11-05 17:39:47 [8000] [6] DEBUG: SMPP PDU dump ends. What does this line mean? 2009-11-05 17:39:47 [8000] [0] WARNING: SIGHUP received, catching and re-opening logs Any advice how can I avoid this? Thanks Elton
