Re: Status page not responding, among other things.

Hi Brenton,

To me one consistent message I am hearing is environment (network /
comms) issues - mySQL disconnect, monitoring showing up and down ..
status slow response. These don't sound like issues with Kannel
itself .. but possibly how you are trying to implement it. It could be
something like DNS problems that are causing you the issues you are
seeing. 

If it's your first time I'd definitely recommend a stand-alone local
instance to get a better understanding (stick to ips - all local in this
instance).

Otherwise I'd recommend you check your environment for issues (try using
wireshark - or tcpdump and load into wireshark locally) and post your
config / debug logs for more assistance. Might be wrong - this is just a
hunch.

Cheers,
Alan



On Thu, 2013-03-21 at 18:14 +1100, Brenton Murray wrote:
> Hi all,
> 
> I've been playing with kannel for the last couple of weeks and i'm 
> having a really hard time to get it to stay fully functional and 
> running. Using Kannel 1.5 snapshot.
> 
> My main problem is that after some time (4days to 20minutes) the status 
> page becomes unresponsive. When this occurs i can still send SMSs to the 
> smsbox->bearerbox->SMSC, but the DLRs no longer are returned. (There 
> have been a few occasions when everything stops)
> 
> I detected the problem because DLRs weren't being sent to our webserver. 
> At this time the status was unavailable. After setting up some server 
> monitors i have seen it go:
> 
> 5:19am Monitor is down
> 7:15am Monitor is up
> 7:40am monitor is down
> 9:08am monitor is up
> 
> There were times when the system was not being used to send but was just 
> running.
> 
> After having it run on my server with other daemons i've now put it on 
> it's own instance (Using AWS) and still getting the same problem.
> 
> 2013-03-21 05:43:01 [17504] [2] DEBUG: HTTP: Creating HTTPClient for 
> `46.165.195.139'.
> 2013-03-21 05:43:01 [17504] [2] DEBUG: HTTP: Created HTTPClient area 
> 0x7fbbd8000a60.
> 2013-03-21 05:43:01 [17504] [2] DEBUG: HTTP: Creating HTTPClient for 
> `174.34.224.167'.
> 2013-03-21 05:43:01 [17504] [2] DEBUG: HTTP: Created HTTPClient area 
> 0x7fbbd8001520.
> 2013-03-21 05:43:06 [17504] [6] DEBUG: SMPP[clx_1]: Sending enquire link:
> 2013-03-21 05:43:06 [17504] [6] DEBUG: SMPP PDU 0x7fbbe00058f0 dump:
> 
> The above is what is happening, clients get created but no data is sent.
> 
> Even when attempting to view the status from localhost/127.0.0.1, it 
> still idles and receives no data.
> 
> 2013-03-21 05:59:58 [17504] [2] DEBUG: HTTP: Creating HTTPClient for 
> `127.0.0.1'.
> 2013-03-21 05:59:58 [17504] [2] DEBUG: HTTP: Created HTTPClient area 
> 0x7fbbd8002fd0.
> 2013-03-21 06:00:21 [17504] [2] DEBUG: HTTP: Creating HTTPClient for 
> `127.0.0.1'.
> 2013-03-21 06:00:21 [17504] [2] DEBUG: HTTP: Created HTTPClient area 
> 0x7fbbd8002e10.
> 2013-03-21 06:01:50 [17504] [2] DEBUG: HTTP: Creating HTTPClient for 
> `174.34.224.167'.
> 2013-03-21 06:01:50 [17504] [2] DEBUG: HTTP: Created HTTPClient area 
> 0x7fbbd8004210.
> 
> I'm hoping someone else may have experienced something similar and could 
> point me in the right direction to debug it?
> 
> Another thing I've noticed is that during these times the mySQL 
> connections start to slowly disconnect and do not attempt to reconnect. 
> I have upped the mySQL wait timeout to 48hrs. Should I have try lowering 
> instead to force reconnections earlier?
> 
> I can supply more logs and configs etc if you need more info, I'm hoping 
> someone out there may have some ideas as i'm not finding any existing 
> issues being discussed similar to this.
> 
> Best Regards,
>      Brenton
>