<error code="503" type="cancel"><service-unavailable ... when sending periodically a message

174 views

Skip to first unread message

Ibon Goikoetxea

unread,

Jan 24, 2016, 8:28:31 PM1/24/16

to SleekXMPP Discussion

I am using SleekXMPP client in a Raspberry Pi to connect and send data messages to an application running in Google AppEngine (using the XMPP service Google has, in talk.google.com).

The client device periodically sends a series of messages with updated data to the application. The flow of messages starts ok, and the application responds with an ackn after each reception.

But then suddenly after a send, the client receives an error message of the type: "<error code="503" type="cancel"><service-unavailable ....", and all subsequent messages that it tries to send all get the same error response from server.

I have checked JIDs and compared with other messages that go through correctly, but i am unable to identify why the client gets stuck in this error, and is left unable to further communicate.

I include here the log of the client with the submittal of a "get_reading" message that goes ok, and the next message "get_CPU" that already gets the error message. (the thread_XMPP_WD in between does nothing in this case, only increments a watchdog for the comms)

I have been stuck with this issue for weeks... :( : i would appreciate if you could give me a hint of where it could come from, and i can further check

thanks in advance

---------------------------------------------------------------------------- XMPP Client Log ------------------------------------------

2016-01-25 00:52:48,536: DEBUG : SEND: <message to="xm...@groovy-legacy-814.appspotchat.com" type="chat" xml:lang="en" from="macar...@gmail.com/pi_white:DD90EF3D"><body>{"cmd": "get_readings", "data": {"datestamp_msg": "2016/01/25-00:52:39", "ind_elem_data": {"remark": "any remark relative to this datapoint", "datestamp_data": "2016/01/25-00:52:39", "temp_c": 50.3, "cmd_data": "TEMP_data", "pir": 0, "relays": {"relay_1": 0, "relay_2": 0}, "light_pct": 60.5541234925081}, "ind_elem_info": {"Device_owner": "macar...@gmail.com/pi_white:", "ind_elem_name": "TEMP_SENSOR_01", "ind_elem_uuid": "01234abcd56789", "Device_name": "pi_white"}}}</body><subject>get_readings</subject><nick xmlns="http://jabber.org/protocol/nick" /></message>

2016-01-25 00:52:48,906: DEBUG : RECV: <message from="xm...@groovy-legacy-814.appspotchat.com/bot" type="chat" id="5FD92800" to="macar...@gmail.com/pi_white:DD90EF3D"><body>{"cmd": "xmpp_ackn", "params": {"last_cmd": "get_readings", "error_msg": ""}}</body></message>

2016-01-25 00:52:49,631: DEBUG : SEND: <message to="xm...@groovy-legacy-814.appspotchat.com" type="chat" xml:lang="en" from="macar...@gmail.com/pi_white:DD90EF3D"><body>{"cmd": "get_CPU", "data": {"datestamp_msg": "2016/01/25-00:52:39", "ind_elem_data": {"loop_duration": 0, "RAM": [455712768, 366972928, 19.5, 143757312, 311955456, 108593152, 14741504, 14454784, 40562688], "remark": "any remark relative to this datapoint", "CPU_Usage": 100.0, "Disk": [6011998208, 4984631296, 698376192, 82.9], "datestamp_data": "2016/01/25-00:52:39", "Core_Temp": 50.8, "cmd_data": "CPU_data"}, "ind_elem_info": {"Device_owner": "macar...@gmail.com/pi_white:", "ind_elem_name": "CPU_Core", "ind_elem_uuid": "01234abcd56789", "Device_name": "pi_white"}}}</body><subject>get_CPU</subject><nick xmlns="http://jabber.org/protocol/nick" /></message>

2016-01-25 00:52:49,651: DEBUG : ------[00:52:49]---------------------------THREAD XMPP WD (0)------------------

2016-01-25 00:52:49,709: DEBUG : ------[00:52:49]---------------------------|_ END OF THREAD XMPP WD (0)------------------

2016-01-25 00:52:49,970: DEBUG : RECV: <message to="macar...@gmail.com/pi_white:DD90EF3D" type="error" xml:lang="en" from="xm...@groovy-legacy-814.appspotchat.com"><body>{"cmd": "get_CPU", "data": {"datestamp_msg": "2016/01/25-00:52:39", "ind_elem_data": {"loop_duration": 0, "RAM": [455712768, 366972928, 19.5, 143757312, 311955456, 108593152, 14741504, 14454784, 40562688], "remark": "any remark relative to this datapoint", "CPU_Usage": 100.0, "Disk": [6011998208, 4984631296, 698376192, 82.9], "datestamp_data": "2016/01/25-00:52:39", "Core_Temp": 50.8, "cmd_data": "CPU_data"}, "ind_elem_info": {"Device_owner": "macar...@gmail.com/pi_white:", "ind_elem_name": "CPU_Core", "ind_elem_uuid": "01234abcd56789", "Device_name": "pi_white"}}}</body><subject>get_CPU</subject><nick xmlns="http://jabber.org/protocol/nick" /><error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /></error></message>

Reply all

Reply to author

Forward

0 new messages