reconcile: ERR_CODE_TABLE_FULL #98

Closed
opened 2026-10-05 01:57:06 +02:00 by adam · 8 comments
Owner

I had many reoccuring/looping errors in the Logs like these:

Apr 01 08:08:15 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:15 - app.radio_sync - WARNING - Failed to add contact 83f6809169d6 during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'}
Apr 01 08:08:15 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:15 - app.radio_sync - WARNING - Failed to add contact 7cd79d3df8ff during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'}
Apr 01 08:08:16 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:16 - app.radio_sync - WARNING - Failed to add contact 83f6809169d6 during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'}
Apr 01 08:08:16 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:16 - app.radio_sync - WARNING - Failed to add contact 7cd79d3df8ff during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'}

It seems that it was not able or had no logic to cleanup the contactlist, before it tried to add an contact. I manually purged the contact list on the companion afterward it was fine. Also i enabled the option to delete the oldest entry automatically so it wont happen again.

I suggest to add manually an contactpurge button within the tool, or add some logic to check the contactlist on the device and do a cleanup if full.

I had many reoccuring/looping errors in the Logs like these: ```Apr 01 08:08:15 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:15 - app.radio_sync - WARNING - Failed to add contact 7cd79d3df8ff during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 01 08:08:15 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:15 - app.radio_sync - WARNING - Failed to add contact 83f6809169d6 during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 01 08:08:15 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:15 - app.radio_sync - WARNING - Failed to add contact 7cd79d3df8ff during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 01 08:08:16 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:16 - app.radio_sync - WARNING - Failed to add contact 83f6809169d6 during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 01 08:08:16 MeshcoreObserver uvicorn[952]: 2026-04-01 08:08:16 - app.radio_sync - WARNING - Failed to add contact 7cd79d3df8ff during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} ``` It seems that it was not able or had no logic to cleanup the contactlist, before it tried to add an contact. I manually purged the contact list on the companion afterward it was fine. Also i enabled the option to delete the oldest entry automatically so it wont happen again. I suggest to add manually an contactpurge button within the tool, or add some logic to check the contactlist on the device and do a cleanup if full. <!-- github-sync-id:4184776727 -->
adam closed this issue 2026-10-05 01:57:06 +02:00
Author
Owner

Hmmm interesting. What model radio are you running and what was your max contacts on radio setting within RemoteTerm set to?

Hmmm interesting. What model radio are you running and what was your max contacts on radio setting within RemoteTerm set to? <!-- github-comment-id:4170781480 -->
Author
Owner

I've pushed the latest version to eliminate a case where this can happen, where the default fill level exceeds capacity on a very select group of radios that have ultra-low contact limits. Still interested to hear your radio type and if you've changed the max contacts setting, but latest should have safeguards for the scenarios where this can happen that we can predict

I've pushed the latest version to eliminate a case where this can happen, where the default fill level exceeds capacity on a very select group of radios that have ultra-low contact limits. Still interested to hear your radio type and if you've changed the max contacts setting, but latest should have safeguards for the scenarios where this can happen that we can predict <!-- github-comment-id:4174479108 -->
Author
Owner

Sure, it is an t1000, and i hat it set to 200 (default?).

Sure, it is an t1000, and i hat it set to 200 (default?). <!-- github-comment-id:4183390588 -->
Author
Owner

Huh, weird, yeah that's a 350 contact radio. Well, I'm not sure if the updates I pushed will help you or not, but let me know how you go. If you've updated to the latest version, going to Settings -> About -> "Open debug support snapshot" and are willing to paste me at least the first block up to "Stop copying here if you don't want logs included", that can tell me a bit more about your setup and possibly help me spot other problems that could cause this (although my hopes are somewhat lower knowing you're on a t1000 and not a much smaller radio).

Huh, weird, yeah that's a 350 contact radio. Well, I'm not sure if the updates I pushed will help you or not, but let me know how you go. If you've updated to the latest version, going to Settings -> About -> "Open debug support snapshot" and are willing to paste me at least the first block up to "Stop copying here if you don't want logs included", that can tell me a bit more about your setup and possibly help me spot other problems that could cause this (although my hopes are somewhat lower knowing you're on a t1000 and not a much smaller radio). <!-- github-comment-id:4184113839 -->
Author
Owner

I have the same error on v. 3.7.1

I get two alternating every two 0.5s forever in a loop:
Apr 06 10:02:32 rpt uvicorn[689]: 2026-04-06 10:02:32 - app.radio_sync - WARNING - Failed to add contact adfea1670fef during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 06 10:02:32 rpt uvicorn[689]: 2026-04-06 10:02:32 - app.radio_sync - WARNING - Failed to add contact 291995e35386 during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 06 10:02:32 rpt uvicorn[689]: 2026-04-06 10:02:32 - app.radio_sync - WARNING - Failed to add contact adfea1670fef during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'}
...

it is a Heltec Wireless paper and the max contacts field was at 202 (accidentally bumped it up when I was having problems saving radio settings --those needed a complete power cycle of the pi and the radio--

I will try version 3.8 now since I can not connect to the radio with anything else than the pi now (hard wired)...
I can not find a purge local contacts button anywhere in the "app" so I home this update works alone.

I have the same error on v. 3.7.1 I get two alternating every two 0.5s forever in a loop: `Apr 06 10:02:32 rpt uvicorn[689]: 2026-04-06 10:02:32 - app.radio_sync - WARNING - Failed to add contact adfea1670fef during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 06 10:02:32 rpt uvicorn[689]: 2026-04-06 10:02:32 - app.radio_sync - WARNING - Failed to add contact 291995e35386 during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'} Apr 06 10:02:32 rpt uvicorn[689]: 2026-04-06 10:02:32 - app.radio_sync - WARNING - Failed to add contact adfea1670fef during background reconcile: {'error_code': 3, 'code_string': 'ERR_CODE_TABLE_FULL'}` ... it is a Heltec Wireless paper and the max contacts field was at 202 (accidentally bumped it up when I was having problems saving radio settings --those needed a complete power cycle of the pi and the radio-- I will try version 3.8 now since I can not connect to the radio with anything else than the pi now (hard wired)... I can not find a purge local contacts button anywhere in the "app" so I home this update works alone. <!-- github-comment-id:4191069550 -->
Author
Owner

seems to be happy after the update:

260}}}, 'channels': {'synced': 0, 'cleared': 0}, 'contact_reconcile_started': True}
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.services.radio_lifecycle - INFO - Auto message fetching started
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic radio sync (interval: 300s)
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic advertisement task (interval configured in settings)
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic message audit task (interval: 3600s)
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic telemetry collection (interval: 28800s)
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.services.radio_lifecycle - INFO - Post-connect setup complete
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.main - INFO - Connected to radio
Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - uvicorn.access - INFO - 10.137.51.135:51197 - "GET /api/radio/config HTTP/1.1" 200 OK
Apr 06 10:14:40 rpt uvicorn[1146]: 2026-04-06 10:14:40 - app.radio_sync - INFO - Background contact reconcile complete: 144 contacts on radio working set
Apr 06 10:14:40 rpt uvicorn[1146]: 2026-04-06 10:14:40 - app.radio_sync - INFO - Background contact reconcile summary: removed 4, loaded 0, failed 0

seems to be happy after the update: 260}}}, 'channels': {'synced': 0, 'cleared': 0}, 'contact_reconcile_started': True} Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.services.radio_lifecycle - INFO - Auto message fetching started Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic radio sync (interval: 300s) Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic advertisement task (interval configured in settings) Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic message audit task (interval: 3600s) Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.radio_sync - INFO - Started periodic telemetry collection (interval: 28800s) Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.services.radio_lifecycle - INFO - Post-connect setup complete Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - app.main - INFO - Connected to radio Apr 06 10:14:39 rpt uvicorn[1146]: 2026-04-06 10:14:39 - uvicorn.access - INFO - 10.137.51.135:51197 - "GET /api/radio/config HTTP/1.1" 200 OK Apr 06 10:14:40 rpt uvicorn[1146]: 2026-04-06 10:14:40 - app.radio_sync - INFO - Background contact reconcile complete: 144 contacts on radio working set Apr 06 10:14:40 rpt uvicorn[1146]: 2026-04-06 10:14:40 - app.radio_sync - INFO - Background contact reconcile summary: removed 4, loaded 0, failed 0 <!-- github-comment-id:4191082239 -->
Author
Owner

Yay! Sorry you ran into issues as well but so happy the update took care of things.

Yay! Sorry you ran into issues as well but so happy the update took care of things. <!-- github-comment-id:4192924689 -->
Author
Owner

I'm going to close this issue since I think the update has fixed things, but feel free to reopen if either of you encounter issues in the future.

I'm going to close this issue since I think the update has fixed things, but feel free to reopen if either of you encounter issues in the future. <!-- github-comment-id:4196931332 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#98