processone / eturnal

STUN / TURN standalone server
https://eturnal.net
Apache License 2.0
225 stars 22 forks source link

Crash report in eturnal.log #66

Open dbi1 opened 3 months ago

dbi1 commented 3 months ago

Hello again,

As just discussed on the chat:

I noticed a crash report line that happened while some bot was trying various things:

2024-03-15 04:17:31.178248+00:00 [info] Accepting connection: xxx.xx.xxx.xx:xxxxx -> yy.yy.yy.yyy:yyy [TLS, session 547jkznze5fo]
2024-03-15 04:17:31.178531+00:00 [notice] Cannot start connection: enotconn [TLS, session 547jkznze5fo]
2024-03-15 04:17:31.178701+00:00 [error] CRASH REPORT:
  crasher:
    initial call: stun:init/1
    pid: <0.779.0>
    registered_name: []
    exception exit: enotconn
      in function  p1_fsm:init_it/6 (p1_fsm.erl, line 386)
    ancestors: [stun_tmp_sup,stun_sup,<0.581.0>]
    message_queue_len: 0
    messages: []
    links: [<0.586.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 376
    stack_size: 28
    reductions: 227
  neighbours:

Just before, the same bot tried something similar, like lots of other bots, but -as with all other bot attempts so far- for this eturnal simply logged the usual "connection failure" / "connection reset" line:

2024-03-15 04:17:27.707308+00:00 [info] Accepting connection: xxx.xx.xxx.xx:xxxxx -> yy.yy.yy.yyy:yyy [TLS, session ly8ip6m2lgu9]
2024-03-15 04:17:30.741074+00:00 [info] Connection failure: closed [TLS, session ly8ip6m2lgu9, anonymous, client xxx.xx.xxx.xx:xxxxx]

Thank you for looking into this!