Jump to content

Khinsu

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

 Content Type 

Posts posted by Khinsu

    Log is at 100%, getting flooded by BTRFS errors

    in General Support

    Posted

    Hello everybody,

     

    recently my unraid log is getting flooded by a BTRFS Error 

    Oct  3 06:55:10 unraid kernel: sd 12:0:0:0: [sdh] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
Oct  3 06:55:10 unraid kernel: sd 12:0:0:0: [sdh] tag#15 CDB: opcode=0x28 28 00 00 61 b4 00 00 00 20 00
Oct  3 06:55:10 unraid kernel: blk_update_request: I/O error, dev sdh, sector 6403072 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct  3 06:55:10 unraid kernel: BTRFS error (device sdi1): bdev /dev/sdh1 errs: wr 1, rd 4820158, flush 0, corrupt 0, gen 0
Oct  3 06:55:11 unraid kernel: sd 36:0:0:0: [sdi] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
Oct  3 06:55:11 unraid kernel: sd 36:0:0:0: [sdi] tag#14 CDB: opcode=0x28 28 00 00 61 14 00 00 00 20 00
Oct  3 06:55:11 unraid kernel: blk_update_request: I/O error, dev sdi, sector 6362112 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct  3 06:55:11 unraid kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 1, rd 4820159, flush 0, corrupt 0, gen 0


    The errors produced from an unused btrfs pool, which i created in the past to use it only for docker. (i have never moved something to it, it is empty)

    Its a bunch of old SSDs and i have no clue why this error appear nor how to solve it.
     

    If you have any advise how to solve the problem, would be great.

     

    many thanks in advance

     

    unraid-diagnostics-20221003-0716.zip

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    Thank you for the quick reply. 

    My router is only exposing 80 and 443.

     

    Yes my VPN is exposing all inbound ports. The VPN provider has a Feature called NAT-Firewall, when enable noone is able to connect to me. That means deluge leeches but is not seeding.

     

    Is there any way to do this with iptabels?

    Are other VPN providers have more control about exposing inbound ports?

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    If the container is running about half an hour to an hour the privoxy service is getting really slow and later not usable at all.


    I enabled some of the privoxy debug settings and found messages like:  

    /config/privoxy/logfile
2022-03-24 21:06:55.135 1465599df180 Error: Rejecting connection from 193.57.40.8. Maximum number of connections reached.
2022-03-24 21:06:55.203 1465599df180 Error: Rejecting connection from 46.161.27.177. Maximum number of connections reached.
2022-03-24 21:06:55.204 1465599df180 Error: Rejecting connection from 46.161.27.177. Maximum number of connections reached.

    So i tried to increase 'max-client-connections' to over 1024 but this doesn't help, its just delaying the slowdown.

    After enabling more of the debug settings i found something wired, it looks like many other ppl using my privoxy:

    Spoiler

    185.105.116.116 - - [26/Mar/2022:11:10:51 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=785E4A5A1FDEE3C676636267BFF41850&steamids=76561198068674229 HTTP/1.1" 200 329
    91.199.118.174 - - [26/Mar/2022:11:10:52 +0100] "CONNECT 212.227.17.178:993 HTTP/1.1" 200 4846
    91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT www.bing.com:443 HTTP/1.1" 200 174001
    91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT 212.227.17.178:993 HTTP/1.1" 200 4846
    91.199.118.174 - - [26/Mar/2022:11:10:53 +0100] "CONNECT redsky.target.com:443 HTTP/1.1" 200 6499
    142.132.224.0 - - [26/Mar/2022:11:10:54 +0100] "CONNECT steamcommunity.com:443 HTTP/1.1" 200 3986
    91.199.118.174 - - [26/Mar/2022:11:10:54 +0100] "CONNECT www.amazon.com:443 HTTP/1.1" 200 8853
    77.223.113.54 - - [26/Mar/2022:11:10:54 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=BDFAA0B48EFB3785A044B35C421423BF&steamids=76561198807819327 HTTP/1.1" 200 341
    91.199.118.174 - - [26/Mar/2022:11:10:54 +0100] "CONNECT www.walmart.com:443 HTTP/1.1" 200 15160
    91.199.118.174 - - [26/Mar/2022:11:10:55 +0100] "CONNECT allegro.pl:443 HTTP/1.1" 200 5843
    142.132.224.0 - - [26/Mar/2022:11:10:55 +0100] "GET http://api.steampowered.com/ISteamUser/GetFriendList/v1/?key=DD92DA7247D10B6B2330C7ED97C6CD9A&steamid=76561198998915288 HTTP/1.1" 200 245
    91.199.118.174 - - [26/Mar/2022:11:10:55 +0100] "CONNECT 52.98.151.82:993 HTTP/1.1" 200 4423
    149.154.117.169 - - [26/Mar/2022:11:10:55 +0100] "CONNECT o2.mail.ru:443 HTTP/1.1" 200 4089
    149.154.117.169 - - [26/Mar/2022:11:10:56 +0100] "CONNECT o2.mail.ru:443 HTTP/1.1" 200 4089
    91.199.118.174 - - [26/Mar/2022:11:10:56 +0100] "CONNECT t.me:443 HTTP/1.1" 200 15661
    91.199.118.174 - - [26/Mar/2022:11:10:56 +0100] "CONNECT outlook.office365.com:993 HTTP/1.1" 200 4401
    185.105.116.116 - - [26/Mar/2022:11:10:56 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=E98F71799ABDF712BB9A87DCFAB8F020&steamids=76561198823641533 HTTP/1.1" 200 351
    77.223.113.54 - - [26/Mar/2022:11:10:57 +0100] "CONNECT steamcommunity.com:443 HTTP/1.1" 200 4025
    193.108.113.6 - - [26/Mar/2022:11:10:57 +0100] "GET http://api.steampowered.com/ISteamUser/GetPlayerSummaries/v2/?key=070149BA46D4B1BD19FEDBC6C160A33E&steamids=76561198798735736 HTTP/1.1" 200 265
    95.216.42.199 - - [26/Mar/2022:11:10:57 +0100] "CONNECT texas.savvyatfirstbanklubbock.com:443 HTTP/1.0" 200 4172
    20.73.244.41 - - [26/Mar/2022:11:10:58 +0100] "CONNECT api.ivi.ru:443 HTTP/1.0" 200 4668 

     

    There thousands of these messages in the log.
    If i restart the container it takes again half an hour to an hour till all these messages appear again.

    It always starts with a request similar to this one: 

    2022-03-24 21:52:47.755 15320cde6640 Header: scan: CONNECT check.best-proxies.ru:443 HTTP/1.1
2022-03-24 21:52:47.756 15320cde6640 Header: scan: Host: check.best-proxies.ru:443
2022-03-24 21:52:47.756 15320cde6640 Header: scan: Proxy-Connection: keep-alive
2022-03-24 21:52:47.756 15320cde6640 Header: scan: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
2022-03-24 21:52:47.756 15320cde6640 Header: crumble crunched: Proxy-Connection: keep-alive!
2022-03-24 21:52:47.757 15320cde6640 Request: check.best-proxies.ru:443/



    I tried to adjust the iptables by my self but i dont get it working. 

    Any advise how I can prevent the internet from connecting to my privoxy container?
    I doesn't want it to be visible/connectable from outside my local network.
     







     

×
×
  • Create New...