Connection reset by peer -- usually means connection was abrupted by either bearerbox or remote side.
It's weird because the only time I saw kannel shutting down smsc connection if there is login problem (i.e. bad credentials - it won't reconnect automatically). Other than that it should try infinite to reconnect. If you can reply the situation would be good if you could post your smsc logs. 2013/9/2 Stefan Gromoll <ste...@gromoll.org>: > Hello, > > We're having a problem with one of our Kannel binds. Kannel establishes a > connection to a carrier and sends and receives messages without problems, but > after some period of time (e.g. 3 days) the connection fails with the > following error: > > 2013-09-01 22:04:14 [15544] [6] DEBUG: SMPP[test]: Sending enquire link: > 2013-09-01 22:04:14 [15544] [6] DEBUG: SMPP PDU 0x9fd3230 dump: > 2013-09-01 22:04:14 [15544] [6] DEBUG: type_name: enquire_link > 2013-09-01 22:04:14 [15544] [6] DEBUG: command_id: 21 = 0x00000015 > 2013-09-01 22:04:14 [15544] [6] DEBUG: command_status: 0 = 0x00000000 > 2013-09-01 22:04:14 [15544] [6] DEBUG: sequence_number: 27699 = 0x00006c33 > 2013-09-01 22:04:14 [15544] [6] DEBUG: SMPP PDU dump ends. > 2013-09-01 22:04:14 [15544] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) > 2013-09-01 22:04:14 [15544] [6] ERROR: Error reading from fd 21: > 2013-09-01 22:04:14 [15544] [6] ERROR: System error 104: Connection reset by > peer > 2013-09-01 22:04:14 [15544] [6] ERROR: SMPP[test]: Couldn't connect to SMS > center (retrying in 10 seconds). > > After this point Kannel tries to connect but is unable to. However, if we > start/stop kannel it reconnects without problem and the connection comes back > up. We have a second bind to a different SMSC of this carrier and it is > stable and runs without problems (and operate binds to many other carriers > with this version of Kannel without problems). We've tried debugging the > issue with the carrier, but they aren't sure what the problem is and don't > seem able to help. > > We're running Kannel from subversion (release 5014). Does anyone know what > the problem might be or how we can debug this? > > Thanks, > > -Stefan >
