orlando500

hi guys, i have just installed prowlarr. Working fine for the first 3-4 indexers. But then its not syncing the indexers into sonarr. The indexers do work in sonarr as it was configured directly before. Seems i can change some parameters in the indexers and then it gets synced, but then another is gone from the list in sonarr.

yeah good question. AS im getting traffic when i disconnect the 1 gb cable. But the speed was not there.

root@Tower:~# ethtool eth1 Settings for eth1: Supported ports: [ FIBRE ] Supported link modes: 1000baseKX/Full 10000baseKR/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 1000baseKX/Full 10000baseKR/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 10000Mb/s Duplex: Full Auto-negotiation: off Port: FIBRE PHYAD: 0 Transceiver: internal Supports Wake-on: d Wake-on: d Current message level: 0x00000014 (20) link ifdown Link detected: yes ethtool -l eth1: driver: mlx4_en version: 4.0-0 firmware-version: 2.42.5000 expansion-rom-version: bus-info: 0000:0b:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes btw: i use the same sfp+ in the microtik 10gb switch inbetween the servers and the UDM pro

im using optical patch cord im3-lc-lc-d1m om3 LC to LC MMF duplex 1m from 10gtek. all new, and all new 10gb sfp+ from https://www.amazon.co.uk/gp/product/B013WFH7C8/ref=ppx_yo_dt_b_asin_title_o00_s01?ie=UTF8&psc=1

yeah the info looks ok, i have link on the 10 gb card. root@battlestar:~# ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 11: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT group default qlen 1000 link/ether 70:85:c2:28:bb:f2 brd ff:ff:ff:ff:ff:ff 12: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc fq state DOWN mode DEFAULT group default qlen 1000 link/ether 70:85:c2:28:bb:f4 brd ff:ff:ff:ff:ff:ff 13: eth2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9004 qdisc mq master br2 state UP mode DEFAULT group default qlen 1000 link/ether e4:1d:2d:7f:22:f0 brd ff:ff:ff:ff:ff:ff 30: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 70:85:c2:28:bb:f2 brd ff:ff:ff:ff:ff:ff 34: eth2.3010@eth2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9004 qdisc noqueue master br2.3010 state UP mode DEFAULT group default qlen 1000 link/ether e4:1d:2d:7f:22:f0 brd ff:ff:ff:ff:ff:ff 35: br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9004 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether e4:1d:2d:7f:22:f0 brd ff:ff:ff:ff:ff:ff 36: br2.3010: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9004 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether e4:1d:2d:7f:22:f0 brd ff:ff:ff:ff:ff:ff 37: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default link/ether 02:42:fb:bd:60:82 brd ff:ff:ff:ff:ff:ff 40: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq state UNKNOWN mode DEFAULT group default qlen 500 link/none 42: veth21c8498@if41: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default link/ether 5a:4e:e9:75:c6:1d brd ff:ff:ff:ff:ff:ff link-netnsid 1 52: veth1ebc0d3@if51: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default link/ether ea:00:4f:15:b4:a1 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@battlestar:~# root@battlestar:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on Port: Twisted Pair PHYAD: 1 Transceiver: internal MDI-X: on (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes root@battlestar:~# ethtool eth2 Settings for eth2: Supported ports: [ FIBRE ] Supported link modes: 1000baseKX/Full 10000baseKR/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 1000baseKX/Full 10000baseKR/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 10000Mb/s Duplex: Full Auto-negotiation: off Port: FIBRE PHYAD: 0 Transceiver: internal Supports Wake-on: d Wake-on: d Current message level: 0x00000014 (20) link ifdown Link detected: yes

i just got myself 2 Mellanox 10 cards in my unraid servers. Have made subnet for them and Connected them up and testing a bit with iperf3. Got this results who is clearly wrong... Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.11.140, port 53738 [ 5] local 192.168.11.20 port 5201 connected to 192.168.11.140 port 53742 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 472 KBytes 3.86 Mbits/sec 3 8.74 KBytes [ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 1 8.74 KBytes [ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0 8.74 KBytes [ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 1 8.74 KBytes [ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0 8.74 KBytes [ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec 0 8.74 KBytes [ 5] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec 1 8.74 KBytes [ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 0 8.74 KBytes [ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec 0 8.74 KBytes [ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 0 8.74 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 472 KBytes 387 Kbits/sec 6 sender how do i troubleshoot this?

broken again

yes.. more episodes where we meet the developers, content creators etc.

yeah i know about the mappings. but i was more thinking of the attack vector to attack at ports from inside the network to other dockers or the host it self. As there really is no docker firewall as far as i know

Hmm i have not had anything like this, but the post makes me think of security in the dockers images we download. Payload can be downloaded with images and then attack the host from within maybe. Dont know how the security in that regard works...

Hi, i have a intel cpu ( Intel Core i9-9820X Prosessor) without graphics integrated, i put in a nvidia 1050 graphics card. After boot can i use that card inside unraid ?. like passtru to a VM or plex etc? If so anything spesical i have to do for it to work (other than normal passtru settings)

Hi, i have a intel cpu ( Intel Core i9-9820X Prosessor) without graphics integrated, i put in a nvidia 1050 graphics card. After boot can i use that card inside unraid. like passtru to a VM or plex etc? If so anything spesical i have to do for it to work (other than normal passtru settings)

after upgrading the gpustat i got the same message "[nvidia] mapping multiple BARs" filling up my syslog. i removed the gpustat and the messages went away.

hi i just noticed my backup of flash was not up to date. i have removed and installed the plugin again. but still get:

yeah i totaly agree. just wanted to know the intervals :-) thanks

@dsmith44 hi what interval is new builds uploaded to unraid app store? i see the tailscale is saying the current docker is running an old version.

Hi, where did you use the Icy Dock flexiDOCK MB795SP-B ? i have a new define 7 xl that im going to start building a new server in. But was thinking of going only with standard drive trays. Didnt see the ice in the picture i think :-)

Did a reinstall and everything worked like a charm with the same setup. Guess the image had taken a hit in the upgrade or something. Thanks for the help

https gave the same error. Im trying to reinstall now. ps: you deserve some support for all your hard work. we take for granted all the hours you put down in the binhex dockers. But from time to time i try to show that i care and want to thank you...

1) same for different machine 2) same for different browser (tried chrome and MS edge) 3) not blocking any local traffic 4)wireguard is off 5) no vlan use 6) sh-5.1# curl http://localhost:8112 curl: (7) Failed to connect to localhost port 8112: Connection refused sh-5.1# 7) host is restarted 8 ) yes it seems i need to start from scratch... strange, it would be nice to have some sort of "check the config/problem solving" script :-) i just dont know what to look for in these stops. And yes i know its been a while for the update. This is the reason i dont like to update so often. It tends to break stuff. All other binhex dockers run fine and i update them once a week. edit: btw: the first curl was from container terminal, here is from server terminal: root@hal:~# curl http://localhost:8112 curl: (56) Recv failure: Connection reset by peer

192.168.10.100 have not changed the config. been working for months. Just the latest update broke it. 192.168.10.20 is the server

supervisord.log

@binhex after update to latest docker version tonight the docker seen to be stuck at: "021-06-07 00:02:24,105 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '44002' 2021-06-07 00:02:24,358 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2021-06-07 00:02:24,459 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.64.100' 2021-06-07 00:02:24,459 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2021-06-07 00:02:24,464 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.25.112.222 different, marking for reconfigure 2021-06-07 00:02:24,468 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2021-06-07 00:02:24,470 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2021-06-07 00:02:24,473 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-06-07 00:02:24,473 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 44002 different, marking for reconfigure 2021-06-07 00:02:24,473 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2021-06-07 00:02:24,775 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.24.112.166' [info] Deluge key 'listen_interface' will have a new value '10.25.112.222' [info] Writing changes to Deluge config file '/config/core.conf'... 2021-06-07 00:02:24,894 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'tun0' [info] Deluge key 'outgoing_interface' will have a new value 'tun0' [info] Writing changes to Deluge config file '/config/core.conf'... " using 6.26% cpu and memory: 307MiB / 62.76GiB I have PIA as VPN provider and this have worked great until the lastest update. edit: additional info: did a top in the docker and config_deluge.p is using 100% of cpu edit2: tried to disable vpn and privoxy in the container. But still no deluge gui. Any ideas on how to get this unstuck...? tnx

hi, first time using influxdb. seems the influx has changes since a lot of the guides was written. Im getting influxdb.exceptions.InfluxDBClientError: 401: {"code":"unauthorized","message":"Unauthorized"} When trying to use userid and password that i selected in influxdb. But with software that support token im getting a connection to the database. Is there a way to enable legacy use of userid/password?

when i get this error message is usually a browser windows that has a unraid server console session before you did a reboot. Do a close all browsers and see then