Comments (6)
Seji64
commented on June 11, 2024
1
please note replacing sniproxy with nginx resulted in a breaking change. nginx is listening on port 8080 (before 80) and 8443 (before 443). Ensure you update your docker configuration accordingly!
from snidust.
Seji64
commented on June 11, 2024
Maybe sniproxy gets OOM killed? Is something logged in journald or dmesg?
from snidust.
Spaghetti-jpg
commented on June 11, 2024
Yeah, sniproxy was killed by OOM
dmesg
[284608.619735] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=containerd.service,mems_allowed=0,global_oom,task_memcg=/system.slice/docker-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18.scope,task=sniproxy,pid=180416,uid=0
[284608.619762] Out of memory: Killed process 180416 (sniproxy) total-vm:1481096kB, anon-rss:611924kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:1612kB oom_score_adj:0
[284609.900176] net_ratelimit: 17449 callbacks suppressed
[284609.900182] TCP: too many orphaned sockets
[284609.900267] TCP: too many orphaned sockets
[284609.900363] TCP: too many orphaned sockets
[284609.900376] TCP: too many orphaned sockets
[284609.900439] TCP: too many orphaned sockets
[284609.900453] TCP: too many orphaned sockets
[284609.900515] TCP: too many orphaned sockets
[284609.900529] TCP: too many orphaned sockets
[284609.900586] TCP: too many orphaned sockets
[284609.900610] TCP: too many orphaned sockets
docker logs
snidust | [INFO] [SniDust] *** End of Domain List ***
snidust | [INFO] [SniDust] Domain Lists reloaded!
snidust | /entrypoint.sh: line 55: 19 Killed /usr/local/bin/sniproxy --config "/etc/sniproxy/config.yaml"
snidust | [WARN] sniproxy crashed with exit code 1. Restarting...
snidust | 2024-02-19T19:59:58Z INF starting sniproxy. version v2.0.4, commit eecf94a0e8df7eaaaa9946fd21f80e392c9642cd
snidust | /entrypoint.sh: line 55: 187 Killed /usr/local/bin/sniproxy --config "/etc/sniproxy/config.yaml"
snidust | [WARN] sniproxy crashed with exit code 1. Restarting...
snidust | 2024-02-19T20:36:33Z INF starting sniproxy. version v2.0.4, commit eecf94a0e8df7eaaaa9946fd21f80e392c9642cd
snidust | /entrypoint.sh: line 55: 759 Killed /usr/local/bin/sniproxy --config "/etc/sniproxy/config.yaml"
snidust | [WARN] sniproxy crashed with exit code 1. Restarting...
snidust | 2024-02-19T20:40:55Z INF starting sniproxy. version v2.0.4, commit eecf94a0e8df7eaaaa9946fd21f80e392c9642cd
snidust | /entrypoint.sh: line 55: 828 Killed /usr/local/bin/sniproxy --config "/etc/sniproxy/config.yaml"
snidust | [WARN] sniproxy crashed with exit code 1. Restarting...
snidust | 2024-02-19T21:04:56Z INF starting sniproxy. version v2.0.4, commit eecf94a0e8df7eaaaa9946fd21f80e392c9642cd
snidust | /entrypoint.sh: line 55: 1210 Killed /usr/local/bin/sniproxy --config "/etc/sniproxy/config.yaml"
snidust | [WARN] sniproxy crashed with exit code 1. Restarting...
snidust | 2024-02-19T21:39:09Z INF starting sniproxy. version v2.0.4, commit eecf94a0e8df7eaaaa9946fd21f80e392c9642cd
snidust | /entrypoint.sh: line 55: 1730 Killed /usr/local/bin/sniproxy --config "/etc/sniproxy/config.yaml"
snidust | [WARN] sniproxy crashed with exit code 1. Restarting...
snidust | 2024-02-19T21:58:24Z INF starting sniproxy. version v2.0.4, commit eecf94a0e8df7eaaaa9946fd21f80e392c9642cd
journalctl
Feb 20 00:01:34 host systemd[1]: run-docker-runtime\x2drunc-moby-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18-runc.iT9TBY.mount: Deactivated successfully.
Feb 20 00:02:05 host systemd[1]: run-docker-runtime\x2drunc-moby-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18-runc.TYoI3H.mount: Deactivated successfully.
Feb 20 00:02:35 host systemd[1]: run-docker-runtime\x2drunc-moby-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18-runc.S5ZDHk.mount: Deactivated successfully.
Feb 20 00:03:05 host systemd[1]: run-docker-runtime\x2drunc-moby-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18-runc.QuVIxg.mount: Deactivated successfully.
Feb 20 00:03:35 host systemd[1]: run-docker-runtime\x2drunc-moby-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18-runc.OhfGFQ.mount: Deactivated successfully.
Feb 20 00:04:53 host kernel: containerd invoked oom-killer: gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=-999
Feb 20 00:04:53 host kernel: CPU: 0 PID: 109444 Comm: containerd Not tainted 5.15.0-78-generic #85-Ubuntu
Feb 20 00:04:53 host kernel: Hardware name: Red Hat KVM, BIOS 1.11.0-2.el7 04/01/2014
Feb 20 00:04:53 host kernel: Call Trace:
Feb 20 00:04:53 host kernel: <TASK>
Feb 20 00:04:53 host kernel: show_stack+0x52/0x5c
Feb 20 00:04:53 host kernel: dump_stack_lvl+0x4a/0x63
Feb 20 00:04:53 host kernel: dump_stack+0x10/0x16
Feb 20 00:04:53 host kernel: dump_header+0x53/0x228
Feb 20 00:04:53 host kernel: oom_kill_process.cold+0xb/0x10
Feb 20 00:04:53 host kernel: out_of_memory+0x106/0x2e0
Feb 20 00:04:53 host kernel: __alloc_pages_slowpath.constprop.0+0x9b7/0xa80
Feb 20 00:04:53 host kernel: __alloc_pages+0x311/0x330
Feb 20 00:04:53 host kernel: alloc_pages+0x9e/0x1e0
Feb 20 00:04:53 host kernel: __page_cache_alloc+0x7e/0x90
Feb 20 00:04:53 host kernel: pagecache_get_page+0x152/0x590
Feb 20 00:04:53 host kernel: ? page_cache_ra_unbounded+0x166/0x210
Feb 20 00:04:53 host kernel: filemap_fault+0x488/0xab0
Feb 20 00:04:53 host kernel: ? filemap_map_pages+0x309/0x400
Feb 20 00:04:53 host kernel: __do_fault+0x3c/0x120
Feb 20 00:04:53 host kernel: do_read_fault+0xeb/0x160
Feb 20 00:04:53 host kernel: do_fault+0xa0/0x2e0
Feb 20 00:04:53 host kernel: handle_pte_fault+0x1cd/0x240
Feb 20 00:04:53 host kernel: __handle_mm_fault+0x405/0x6f0
Feb 20 00:04:53 host kernel: handle_mm_fault+0xd8/0x2c0
Feb 20 00:04:53 host kernel: do_user_addr_fault+0x1c9/0x670
Feb 20 00:04:53 host kernel: exc_page_fault+0x77/0x170
Feb 20 00:04:53 host kernel: asm_exc_page_fault+0x27/0x30
Feb 20 00:04:53 host kernel: RIP: 0033:0x564c3231931d
Feb 20 00:04:53 host kernel: Code: Unable to access opcode bytes at RIP 0x564c323192f3.
Feb 20 00:04:53 host kernel: RSP: 002b:00007f7e7a6afd18 EFLAGS: 00010202
Feb 20 00:04:53 host kernel: RAX: 0000000000000000 RBX: 0000000000002710 RCX: 0000564c3231931d
Feb 20 00:04:53 host kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007f7e7a6afd18
Feb 20 00:04:53 host kernel: RBP: 00007f7e7a6afd28 R08: 00000000000263bd R09: 0000000000000000
Feb 20 00:04:53 host kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00007f7e7a6af738
Feb 20 00:04:53 host kernel: R13: 0000000000000034 R14: 000000c0000069c0 R15: 0000000000000001
Feb 20 00:04:53 host kernel: </TASK>
Feb 20 00:04:53 host kernel: Mem-Info:
Feb 20 00:04:53 host kernel: active_anon:261 inactive_anon:241860 isolated_anon:0
active_file:3 inactive_file:117 isolated_file:0
unevictable:6905 dirty:0 writeback:0
slab_reclaimable:29023 slab_unreclaimable:200955
mapped:2303 shmem:263 pagetables:1526 bounce:0
kernel_misc_reclaimable:0
free:13975 free_pcp:536 free_cma:0
Feb 20 00:04:53 host kernel: Node 0 active_anon:1044kB inactive_anon:967440kB active_file:12kB inactive_file:468kB unevictable:27620kB isolated(anon):0kB isolated(file):0kB mapped:9212kB dirty:0kB writeback:0kB shmem:1052kB shmem_thp: 0kB shmem_pmdmapped:>
Feb 20 00:04:53 host kernel: Node 0 DMA free:7696kB min:364kB low:452kB high:540kB reserved_highatomic:0KB active_anon:0kB inactive_anon:4416kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB mlocked:0kB >
Feb 20 00:04:53 host kernel: lowmem_reserve[]: 0 1834 1834 1834 1834
Feb 20 00:04:53 host kernel: Node 0 DMA32 free:48204kB min:44688kB low:55860kB high:67032kB reserved_highatomic:4096KB active_anon:1044kB inactive_anon:963024kB active_file:12kB inactive_file:468kB unevictable:27620kB writepending:0kB present:2080624kB ma>
Feb 20 00:04:53 host kernel: lowmem_reserve[]: 0 0 0 0 0
Feb 20 00:04:53 host kernel: Node 0 DMA: 2*4kB (ME) 1*8kB (E) 6*16kB (UME) 5*32kB (UME) 4*64kB (M) 4*128kB (UME) 4*256kB (M) 3*512kB (ME) 4*1024kB (UME) 0*2048kB 0*4096kB = 7696kB
Feb 20 00:04:53 host kernel: Node 0 DMA32: 138*4kB (UME) 327*8kB (UM) 121*16kB (UME) 44*32kB (UME) 56*64kB (ME) 86*128kB (ME) 48*256kB (ME) 29*512kB (UM) 0*1024kB 0*2048kB 0*4096kB = 48240kB
Feb 20 00:04:53 host kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Feb 20 00:04:53 host kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Feb 20 00:04:53 host kernel: 2661 total pagecache pages
Feb 20 00:04:53 host kernel: 0 pages in swap cache
Feb 20 00:04:53 host kernel: Swap cache stats: add 0, delete 0, find 0/0
Feb 20 00:04:53 host kernel: Free swap = 0kB
Feb 20 00:04:53 host kernel: Total swap = 0kB
Feb 20 00:04:53 host kernel: 524154 pages RAM
Feb 20 00:04:53 host kernel: 0 pages HighMem/MovableOnly
Feb 20 00:04:53 host kernel: 21384 pages reserved
Feb 20 00:04:53 host kernel: 0 pages hwpoisoned
Feb 20 00:04:53 host kernel: Tasks state (memory values in pages):
Feb 20 00:04:53 host kernel: [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
Feb 20 00:04:53 host kernel: [ 452] 103 452 2251 529 49152 0 -900 dbus-daemon
Feb 20 00:04:53 host kernel: [ 457] 0 457 8182 2246 102400 0 0 networkd-dispat
Feb 20 00:04:53 host kernel: [ 463] 0 463 3956 434 65536 0 0 systemd-logind
Feb 20 00:04:53 host kernel: [ 507] 0 507 27437 2217 114688 0 0 unattended-upgr
Feb 20 00:04:53 host kernel: [ 732] 0 732 362962 7674 471040 0 -500 dockerd
Feb 20 00:04:53 host kernel: [ 750] 0 750 1543 22 45056 0 0 agetty
Feb 20 00:04:53 host kernel: [ 109397] 0 109397 1724 572 57344 0 0 cron
Feb 20 00:04:53 host kernel: [ 109401] 0 109401 59904 418 102400 0 0 upowerd
Feb 20 00:04:53 host kernel: [ 109404] 104 109404 22340 291 73728 0 0 systemd-timesyn
Feb 20 00:04:53 host kernel: [ 109405] 0 109405 73896 1188 167936 0 0 packagekitd
Feb 20 00:04:53 host kernel: [ 109406] 107 109406 55602 604 81920 0 0 rsyslogd
Feb 20 00:04:53 host kernel: [ 109408] 0 109408 55042 920 462848 0 -250 systemd-journal
Feb 20 00:04:53 host kernel: [ 109411] 0 109411 72329 6775 110592 0 -1000 multipathd
Feb 20 00:04:53 host kernel: [ 109415] 0 109415 6404 668 73728 0 -1000 systemd-udevd
Feb 20 00:04:53 host kernel: [ 109416] 0 109416 98109 1348 126976 0 0 udisksd
Feb 20 00:04:53 host kernel: [ 109423] 0 109423 321242 3922 294912 0 -999 containerd
Feb 20 00:04:53 host kernel: [ 109426] 0 109426 58624 861 86016 0 0 polkitd
Feb 20 00:04:53 host kernel: [ 109434] 0 109434 79491 863 122880 0 0 ModemManager
Feb 20 00:04:53 host kernel: [ 109466] 101 109466 4063 350 69632 0 0 systemd-network
Feb 20 00:04:53 host kernel: [ 109482] 0 109482 311449 2721 245760 0 -900 snapd
Feb 20 00:04:53 host kernel: [ 123599] 0 123599 4273 476 73728 0 0 systemd
Feb 20 00:04:53 host kernel: [ 123601] 0 123601 42630 1239 98304 0 0 (sd-pam)
Feb 20 00:04:53 host kernel: [ 134377] 0 134377 3859 1180 69632 0 -1000 sshd
Feb 20 00:04:53 host kernel: [ 155452] 0 155452 4367 825 73728 0 0 sshd
Feb 20 00:04:53 host kernel: [ 155509] 0 155509 2700 1462 61440 0 0 bash
Feb 20 00:04:53 host kernel: [ 178033] 0 178033 288893 135 135168 0 -500 docker-proxy
Feb 20 00:04:53 host kernel: [ 178038] 0 178038 288893 132 126976 0 -500 docker-proxy
Feb 20 00:04:53 host kernel: [ 178053] 0 178053 288893 132 139264 0 -500 docker-proxy
Feb 20 00:04:53 host kernel: [ 178058] 0 178058 288893 133 139264 0 -500 docker-proxy
Feb 20 00:04:53 host kernel: [ 178073] 0 178073 360949 56813 606208 0 -500 docker-proxy
Feb 20 00:04:53 host kernel: [ 178078] 0 178078 288893 132 131072 0 -500 docker-proxy
Feb 20 00:04:53 host kernel: [ 178096] 0 178096 180634 928 110592 0 -998 containerd-shim
Feb 20 00:04:53 host kernel: [ 178119] 0 178119 212 10 40960 0 0 tini
Feb 20 00:04:53 host kernel: [ 178150] 0 178150 584 69 45056 0 0 bash
Feb 20 00:04:53 host kernel: [ 178160] 100 178160 7886 1828 106496 0 0 dnsdist
Feb 20 00:04:53 host kernel: [ 178161] 0 178161 584 69 45056 0 0 bash
Feb 20 00:04:53 host kernel: [ 180416] 0 180416 370274 152981 1650688 0 0 sniproxy
Feb 20 00:04:53 host kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=containerd.service,mems_allowed=0,global_oom,task_memcg=/system.slice/docker-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18.scope,task=sniproxy,pid=1>
Feb 20 00:04:53 host kernel: Out of memory: Killed process 180416 (sniproxy) total-vm:1481096kB, anon-rss:611924kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:1612kB oom_score_adj:0
Feb 20 00:04:53 host systemd[1]: docker-bc9cbd704ac7955e5ed1cb33723411c265c740766378ed1e27dfb56e62560c18.scope: A process of this unit has been killed by the OOM killer.
Feb 20 00:04:54 host kernel: net_ratelimit: 17449 callbacks suppressed
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
Feb 20 00:04:54 host kernel: TCP: too many orphaned sockets
from snidust.
Seji64
commented on June 11, 2024
How much RAM does your VPS / Server have? I have not much load on my SniDust instance, but i had never this kind of issue.
from snidust.
Pachini
commented on June 11, 2024
Same problem here and I know why
if ANYONE will do http request to server ip HTTP: GET / HTTP/1.1 snidust instantly falls into an infinite loop
tcpdump:
20:04:07.991292 eth0 In IP 45.86.229.244.49548 > 5.161.198.251.80: Flags [S], seq 466288105, win 64240, options [mss 1460,sackOK,TS val 1007446571 ecr 0,nop,wscale 7], length 0
20:04:07.991330 br-c8f6d363995f Out IP 45.86.229.244.49548 > 172.18.0.2.80: Flags [S], seq 466288105, win 64240, options [mss 1460,sackOK,TS val 1007446571 ecr 0,nop,wscale 7], length 0
20:04:07.991337 veth8a72bfb Out IP 45.86.229.244.49548 > 172.18.0.2.80: Flags [S], seq 466288105, win 64240, options [mss 1460,sackOK,TS val 1007446571 ecr 0,nop,wscale 7], length 0
20:04:07.991363 veth8a72bfb P IP 172.18.0.2.80 > 45.86.229.244.49548: Flags [S.], seq 3337158364, ack 466288106, win 65160, options [mss 1460,sackOK,TS val 1288683790 ecr 1007446571,nop,wscale 7], length 0
20:04:07.991367 br-c8f6d363995f In IP 172.18.0.2.80 > 45.86.229.244.49548: Flags [S.], seq 3337158364, ack 466288106, win 65160, options [mss 1460,sackOK,TS val 1288683790 ecr 1007446571,nop,wscale 7], length 0
20:04:07.991372 eth0 Out IP 5.161.198.251.80 > 45.86.229.244.49548: Flags [S.], seq 3337158364, ack 466288106, win 65160, options [mss 1460,sackOK,TS val 1288683790 ecr 1007446571,nop,wscale 7], length 0
20:04:08.102234 eth0 In IP 45.86.229.244.49548 > 5.161.198.251.80: Flags [.], ack 1, win 502, options [nop,nop,TS val 1007446682 ecr 1288683790], length 0
20:04:08.102263 br-c8f6d363995f Out IP 45.86.229.244.49548 > 172.18.0.2.80: Flags [.], ack 1, win 502, options [nop,nop,TS val 1007446682 ecr 1288683790], length 0
20:04:08.102270 veth8a72bfb Out IP 45.86.229.244.49548 > 172.18.0.2.80: Flags [.], ack 1, win 502, options [nop,nop,TS val 1007446682 ecr 1288683790], length 0
20:04:08.102710 eth0 In IP 45.86.229.244.49548 > 5.161.198.251.80: Flags [P.], seq 1:421, ack 1, win 502, options [nop,nop,TS val 1007446682 ecr 1288683790], length 420: HTTP: GET / HTTP/1.1
20:04:08.102718 br-c8f6d363995f Out IP 45.86.229.244.49548 > 172.18.0.2.80: Flags [P.], seq 1:421, ack 1, win 502, options [nop,nop,TS val 1007446682 ecr 1288683790], length 420: HTTP: GET / HTTP/1.1
20:04:08.102721 veth8a72bfb Out IP 45.86.229.244.49548 > 172.18.0.2.80: Flags [P.], seq 1:421, ack 1, win 502, options [nop,nop,TS val 1007446682 ecr 1288683790], length 420: HTTP: GET / HTTP/1.1
20:04:08.102736 veth8a72bfb P IP 172.18.0.2.80 > 45.86.229.244.49548: Flags [.], ack 421, win 506, options [nop,nop,TS val 1288683901 ecr 1007446682], length 0
20:04:08.102741 br-c8f6d363995f In IP 172.18.0.2.80 > 45.86.229.244.49548: Flags [.], ack 421, win 506, options [nop,nop,TS val 1288683901 ecr 1007446682], length 0
20:04:08.102747 eth0 Out IP 5.161.198.251.80 > 45.86.229.244.49548: Flags [.], ack 421, win 506, options [nop,nop,TS val 1288683901 ecr 1007446682], length 0
20:04:08.103053 veth8a72bfb P IP 172.18.0.2.45076 > 5.161.198.251.80: Flags [S], seq 835487573, win 64240, options [mss 1460,sackOK,TS val 2007221226 ecr 0,nop,wscale 7], length 0
20:04:08.103074 br-c8f6d363995f In IP 172.18.0.2.45076 > 5.161.198.251.80: Flags [S], seq 835487573, win 64240, options [mss 1460,sackOK,TS val 2007221226 ecr 0,nop,wscale 7], length 0
20:04:08.103097 br-c8f6d363995f Out IP 5.161.198.251.80 > 172.18.0.2.45076: Flags [S.], seq 334357068, ack 835487574, win 65160, options [mss 1460,sackOK,TS val 3797011594 ecr 2007221226,nop,wscale 7], length 0
20:04:08.103100 veth8a72bfb Out IP 5.161.198.251.80 > 172.18.0.2.45076: Flags [S.], seq 334357068, ack 835487574, win 65160, options [mss 1460,sackOK,TS val 3797011594 ecr 2007221226,nop,wscale 7], length 0
20:04:08.103116 veth8a72bfb P IP 172.18.0.2.45076 > 5.161.198.251.80: Flags [.], ack 1, win 502, options [nop,nop,TS val 2007221226 ecr 3797011594], length 0
20:04:08.103118 br-c8f6d363995f In IP 172.18.0.2.45076 > 5.161.198.251.80: Flags [.], ack 1, win 502, options [nop,nop,TS val 2007221226 ecr 3797011594], length 0
20:04:08.103261 veth8a72bfb P IP 172.18.0.2.45076 > 5.161.198.251.80: Flags [P.], seq 1:367, ack 1, win 502, options [nop,nop,TS val 2007221227 ecr 3797011594], length 366: HTTP: GET / HTTP/1.1
20:04:08.103264 br-c8f6d363995f In IP 172.18.0.2.45076 > 5.161.198.251.80: Flags [P.], seq 1:367, ack 1, win 502, options [nop,nop,TS val 2007221227 ecr 3797011594], length 366: HTTP: GET / HTTP/1.1
20:04:08.103269 br-c8f6d363995f Out IP 5.161.198.251.80 > 172.18.0.2.45076: Flags [.], ack 367, win 507, options [nop,nop,TS val 3797011595 ecr 2007221227], length 0
20:04:08.103270 veth8a72bfb Out IP 5.161.198.251.80 > 172.18.0.2.45076: Flags [.], ack 367, win 507, options [nop,nop,TS val 3797011595 ecr 2007221227], length 0
20:04:08.103439 br-c8f6d363995f Out IP 172.18.0.1.41696 > 172.18.0.2.80: Flags [S], seq 1464475819, win 64240, options [mss 1460,sackOK,TS val 558437229 ecr 0,nop,wscale 7], length 0
20:04:08.103440 veth8a72bfb Out IP 172.18.0.1.41696 > 172.18.0.2.80: Flags [S], seq 1464475819, win 64240, options [mss 1460,sackOK,TS val 558437229 ecr 0,nop,wscale 7], length 0
20:04:08.103451 veth8a72bfb P IP 172.18.0.2.80 > 172.18.0.1.41696: Flags [S.], seq 2970199944, ack 1464475820, win 65160, options [mss 1460,sackOK,TS val 876148646 ecr 558437229,nop,wscale 7], length 0
20:04:08.103452 br-c8f6d363995f In IP 172.18.0.2.80 > 172.18.0.1.41696: Flags [S.], seq 2970199944, ack 1464475820, win 65160, options [mss 1460,sackOK,TS val 876148646 ecr 558437229,nop,wscale 7], length 0
20:04:08.103459 br-c8f6d363995f Out IP 172.18.0.1.41696 > 172.18.0.2.80: Flags [.], ack 1, win 502, options [nop,nop,TS val 558437229 ecr 876148646], length 0
20:04:08.103459 veth8a72bfb Out IP 172.18.0.1.41696 > 172.18.0.2.80: Flags [.], ack 1, win 502, options [nop,nop,TS val 558437229 ecr 876148646], length 0
20:04:08.103545 br-c8f6d363995f Out IP 172.18.0.1.41696 > 172.18.0.2.80: Flags [P.], seq 1:367, ack 1, win 502, options [nop,nop,TS val 558437229 ecr 876148646], length 366: HTTP: GET / HTTP/1.1
20:04:08.103546 veth8a72bfb Out IP 172.18.0.1.41696 > 172.18.0.2.80: Flags [P.], seq 1:367, ack 1, win 502, options [nop,nop,TS val 558437229 ecr 876148646], length 366: HTTP: GET / HTTP/1.1
and after some time in snidust logs
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
2024-03-31T06:13:50Z ERR EOF service=http
So, snidust can survive if server will have ~4GB ram, but moment it goes into an infinite loop, it eats up 4GB of memory minimum and floods the server with endless connections to itself
Btw, problem related to issue #34
from snidust.
Seji64
commented on June 11, 2024
Hm, as the dev of the sniproxy Version we are using here is no longer active and so the root cause won't get fixed soon, its maybe better to Switch back to the plain old Version of sniproxy
from snidust.
Related Issues (20)
- Not unblocking HOT 7
- bypass Great Firewall HOT 1
- Website sometime not loading
- docker becames unresponsive after some time HOT 3
- Localhost socks5 HOT 1
- Question HOT 6
- SniDust + Adguard Home HOT 3
- Question: Different location depending on domain/service? HOT 1
- high bandwidth HOT 2
- Odd domains in lookup in docker log - Large bandwidth useage HOT 10
- Noob question
- Cron permission error HOT 1
- No internet when the VPS server as DNS HOT 1
- iussue with changing upstream DNS HOT 2
- New port change introduces invalid CIDR address error HOT 4
- huge disk usage by nginx logs HOT 4
- not working without any error in logs HOT 2
- How to find YouTube domains? HOT 1
- Can you please add disney plus and hotstar
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from snidust.