outdated device ticket error - device cannot connect when running diode socksd

[hansr]

a developer workstation running diode socksd intermittently gets an "outdated device ticket" error below.

specific command:

$ ps aux |grep diode
root      155123  2.4  1.6 1762552 31744 ?       Ssl  16:01   4:15 /usr/local/bin/diode -debug -diodeaddrs=34.60.163.150:41046 socksd -socksd_port 1081
root      155244  0.0  0.7 1068864 14312 ?       Ssl  16:03   0:02 /usr/bin/python3 /usr/local/bin/diode_proxy --dns-server 127.0.0.53 --listen-host 0.0.0.0 --socks-host 127.0.0.1 --socks-port 1081 --mapping glass-dev.internal:0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d.diode

specific error:

Oct 03 18:49:03 authproxy-tool-001 diode[155123]: DEBUG Validating ticket based on unchecked block 9772742 9777355 server=157.173.98.132:41046
Oct 03 18:49:03 authproxy-tool-001 diode[155123]: ERROR Failed to connectDevice(0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d): outdated device ticket
Oct 03 18:49:48 authproxy-tool-001 diode[155123]: DEBUG 3555212313744672483: New request for 0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d
Oct 03 18:49:49 authproxy-tool-001 diode[155123]: DEBUG Validating ticket based on unchecked block 9772742 9777355 server=157.173.98.132:41046
Oct 03 18:49:49 authproxy-tool-001 diode[155123]: WARN found outdated deviceticket() &{Version:1 ServerID:[206 202 47 140 241 152 59 76 240 193 186 81 253 56 44 43 195 122 186 88] BlockNumber:9772742 BlockHash:[0 0 5 92 157 66 165 75 57 162 245 86 40 122 191 1 242 245 127 184 123 40 158 36 22 66 161 141 228 241 122 175] FleetAddr:[96 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] TotalConnections:+81 TotalBytes:+128040434 LocalAddr:[] DeviceSig:[1 36 36 30 210 56 43 221 37 119 196 128 170 213 247 55 215
 250 78 91 176 9 13 63 173 205 189 96 119 76 245 230 147 75 111 102 129 250 43 51 69 77 98 158 118 81 202 128 24 42 16 129 141 144 178 208 145 35 11 85 50 93 138 147 193] ServerSig:[1 164 243 231 163 125 100 130 80 202 161 79 31 105 83 177 69 150 96 175 47 228 69 248 22 133 77 39 108 60 92 82 218 95 252 73 43 2 41 188 79 78 164 108 43 89 6 217 131 216 163 189 105 209 238 41 32 243 148 86 63 112 124 209 8] ChainID:0 Epoch:0 CacheTime:0001-01-01 00:00:00 +0000 UTC deviceAddress:[0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0] Err:} server=157.173.98.132:41046
Oct 03 18:49:49 authproxy-tool-001 diode[155123]: DEBUG Validating ticket based on unchecked block 9772742 9777355 server=157.173.98.132:41046
Oct 03 18:49:49 authproxy-tool-001 diode[155123]: ERROR Failed to connectDevice(0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d): outdated device ticket

on the other side, the resource they are trying to reach is ssh ubuntu@0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d.diode

device 0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d is running the Diode CLI with:

diode -debug -diodeaddrs=34.60.163.150:41046 socksd -socksd_port 1081

I really don't know why the logs show "DEBUG Validating ticket based on unchecked block 9772742 9777355 server=157.173.98.132:41046" -> why is that server even being connected to??!

[hansr]

Oct 03 19:01:32 authproxy-tool-001 diode[155123]: DEBUG 4694294322523551558: New request for 0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d
Oct 03 19:01:32 authproxy-tool-001 diode[155123]: DEBUG Validating ticket based on unchecked block 9772742 9777387 server=157.173.98.132:41046
Oct 03 19:01:32 authproxy-tool-001 diode[155123]: WARN found outdated deviceticket() &{Version:1 ServerID:[206 202 47 140 241 152 59 76 240 193 186 81 253 56 44 43 195 122 186 88] BlockNumber:9772742 BlockHash:[0 0 5 92 157 66 165 75 57 162 245 86 40 122 191 1 242 245 127 184 123 40 158 36 22 66 161 141 228 241 122 175] FleetAddr:[96 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] TotalConnections:+81 TotalBytes:+128040434 LocalAddr:[] DeviceSig:[1 36 36 30 210 56 43 221 37 119 196 128 170 213 247 55 215
 250 78 91 176 9 13 63 173 205 189 96 119 76 245 230 147 75 111 102 129 250 43 51 69 77 98 158 118 81 202 128 24 42 16 129 141 144 178 208 145 35 11 85 50 93 138 147 193] ServerSig:[1 164 243 231 163 125 100 130 80 202 161 79 31 105 83 177 69 150 96 175 47 228 69 248 22 133 77 39 108 60 92 82 218 95 252 73 43 2 41 188 79 78 164 108 43 89 6 217 131 216 163 189 105 209 238 41 32 243 148 86 63 112 124 209 8] ChainID:0 Epoch:0 CacheTime:0001-01-01 00:00:00 +0000 UTC deviceAddress:[0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0] Err:} server=157.173.98.132:41046
Oct 03 19:01:32 authproxy-tool-001 diode[155123]: DEBUG Validating ticket based on unchecked block 9772742 9777387 server=157.173.98.132:41046
Oct 03 19:01:32 authproxy-tool-001 diode[155123]: ERROR Failed to connectDevice(0xb280937ec8485447b5e94b6cf0fa072d0cb9ea9d): outdated device ticket

[hansr]

the 157.173.98.132 is eu2.prenet.diode.io

since both sides are specifying a -diodeaddrs=[blah] why is the CLI continuing to try to use EU2 for something???!

[dominicletz]

The outdated ticket might point to eu2 - Older tickets should not be retrieved.

[dominicletz]

Suggested work-around:

• Add simple timestamp to stored tickets (all objects)
• Do regular garbage collect of old tickets
• https://github.com/diodechain/diode_node/blob/main/lib/cron.ex

[hansr]

[hansr]

The publishing Diode Client shows this error:

Is there anything I can provide for you to identify the memory leak resulting in OOM for the diode client on that server?

[Mon Nov 17 01:34:14 2025] node invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
[Mon Nov 17 01:34:14 2025] Out of memory: Killed process 3227471 (diode) total-vm:20583256kB, anon-rss:10711920kB, file-rss:1664kB, shmem-rss:0kB, UID:0 pgtables:24628kB oom_score_adj:0

[dominicletz]

This should be fixed with #4