kakmoster

I have had the same errors since october 1st. Has anyone figured this out? Log ignored errors/warnings is set to "yes" Local TLD is set to "local" Bond type is set to "active backup"

I will try is_paused=True, use_auto_torrent_management=False, Instead of paused and autoTTM tonight.

Hello, thanks for the scripts! I have two problems though. For some reason the torrents are not added in a paused state. I have copied your code exactly and only changed file paths, auth info and client ip/port. The other problem is that some torrents are added as a subfolder inside the main folder. (example: series/seriesname/season2/season2/episode1.mkv or movies/moviename1/moviename1/moviename1.mkv). I can live with that if I can load them as paused

Thank you, I will look into that.

Four days ago unraid crashed and I started getting ATA3 errors during a parity check. I canceled the parity check as it was too slow. After that I did a simple check on my drives, just copying files to and from them without any issues. They all seemed fine and the errors stopped. However I checked the logs now and the errors persist. Diagnistics is attached. What is the issue, I can't figure it out. Thanks. blunova-diagnostics-20221119-2112.zip

No data is saved for me... I have got detection working and so on.. record: enabled for each camera. Events are created in the ui but no data is saved.. Media Path is mapped to an unassigned devices disks using the slave option. Not sure what's wrong. Edit: Managed to get it to work by adding object tracking as well i the config

I have started getting the following: 2022-04-16 17:20:43,347 DEBG 'rutorrent-script' stderr output: 16 17:20:43 [error] 701#701: *2536 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:21:41,496 DEBG 'rutorrent-script' stderr output: 16 17:21:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:21:43,369 DEBG 'rutorrent-script' stderr output: 16 17:21:43 [error] 700#700: *2552 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:22:41,547 DEBG 'rutorrent-script' stderr output: 16 17:22:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:23:13,317 DEBG 'rutorrent-script' stderr output: 16 17:23:13 [error] 700#700: *2561 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:24:11,544 DEBG 'rutorrent-script' stderr output: 16 17:24:11 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:24:13,336 DEBG 'rutorrent-script' stderr output: 16 17:24:13 [error] 700#700: *2564 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:25:11,570 DEBG 'rutorrent-script' stderr output: 16 17:25:11 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:25:43,332 DEBG 'rutorrent-script' stderr output: 16 17:25:43 [error] 700#700: *2568 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:26:41,582 DEBG 'rutorrent-script' stderr output: 16 17:26:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:26:43,344 DEBG 'rutorrent-script' stderr output: 16 17:26:43 [error] 700#700: *2571 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:27:41,623 DEBG 'rutorrent-script' stderr output: 16 17:27:41 [error] 700#700: *2550 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:28:13,378 DEBG 'rutorrent-script' stderr output: 16 17:28:13 [error] 700#700: *2575 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:29:13,407 DEBG 'rutorrent-script' stderr output: 16 17:29:13 [error] 700#700: *2577 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:42:41,860 DEBG 'rutorrent-script' stderr output: 16 17:42:41 [error] 700#700: *2579 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:43:41,891 DEBG 'rutorrent-script' stderr output: 16 17:43:41 [error] 700#700: *2579 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:44:13,609 DEBG 'rutorrent-script' stderr output: 16 17:44:13 [error] 700#700: *2583 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 17:45:13,648 DEBG 'rutorrent-script' stderr output: 16 17:45:13 [error] 700#700: *2585 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 18:13:42,558 DEBG 'rutorrent-script' stderr output: 16 18:13:42 [error] 700#700: *2588 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 18:14:42,586 DEBG 'rutorrent-script' stderr output: 16 18:14:42 [error] 700#700: *2588 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 18:15:14,112 DEBG 'rutorrent-script' stderr output: 16 18:15:14 [error] 701#701: *2592 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 18:16:14,152 DEBG 'rutorrent-script' stderr output: 16 18:16:14 [error] 700#700: *2594 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 19:14:43,830 DEBG 'rutorrent-script' stderr output: 16 19:14:43 [error] 700#700: *2599 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 19:15:43,861 DEBG 'rutorrent-script' stderr output: 16 19:15:43 [error] 700#700: *2599 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 19:16:14,969 DEBG 'rutorrent-script' stderr output: 16 19:16:14 [error] 700#700: *2603 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" 2022-04-16 19:17:15,002 DEBG 'rutorrent-script' stderr output: 16 19:17:15 [error] 700#700: *2605 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.2:9080" I have tried removing docker container and install new one, only keeping the session folder. This has happended twice in two days.

I am having some issues with the Official Plex container and want to migrate to this one. What folders should I copy from the official one so that all settings and history is kept?

Looks like the MB455SFP-B is EoL and is getting expensive (220 euro). The Istarusa and norco is not sold in europe and the Supermicro is hard to come by (also EoL?) and expensive (300 euro) What are the options in 2022? Would like a cage for ~150 euro or less.

To enable VPN using OVPN, do I just download the configuration files (udp or tcp?), place them in /config/openvpn and enable set VPN_ENABLED to yes? Is it that easy?

I am having the same issue as portonalga. Everything seem to work but the log is spitting out disconnects/reconnects/unregistrered connections and all kinds of errors. I am using a wildcard cert *.mydomain.com (let's encrypt - Cloudflare) for my subdomains. in my config.yml I have put subdomain.mydomain.com as only mydomain.com would give me 502. Not sure what information is necessary.

Copying rtorrent session folder was sufficient. However, I have mapped all my shares individually. /download/movies / -> /mnt/user/movies/downloads/ /download/series/ -> /mnt/user/series/ etc When I press the "add torrent" button the default directory is /data/incomplete/. I have chosen the "Default directory for downloads" to be "/download/" How can I change this?

I want to migrate to this container from another rtorrent container. What files/folders do I need to keep my current torrents? Rechecking everything is fine but I do not want to add anything manually.

reverseproxy443 * 443 192.168.1.2:1443 WAN reverseproxy80 * 80 192.168.1.2:180 WAN rtorrent * 51413 192.168.1.2:51413 WAN These are the port mappings on my router. Never had anything else opened.

I'm sorry but that's not really the main concern. Thanks anyway. What I'm concerned about is the connection from my router. Which have stopped now after I blocked an external IP.... Jan 30 07:08:46 Diabetes sshd[21229]: Connection from 192.168.1.1 port 55650 on 192.168.1.2 port 22 rdomain "" Jan 30 07:08:46 Diabetes sshd[21229]: error: kex_exchange_identification: Connection closed by remote host Jan 30 07:08:46 Diabetes sshd[21229]: Connection closed by 192.168.1.1 port 55650 Jan 30 07:08:46 Diabetes vsftpd[21228]: connect from 192.168.1.1 (192.168.1.1) Jan 30 07:08:46 Diabetes vsftpd[21235]: connect from 192.168.1.1 (192.168.1.1) Jan 30 07:08:57 Diabetes smbd[21231]: [2022/01/30 07:08:57.043674, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Jan 30 07:08:57 Diabetes smbd[21231]: read_fd_with_timeout failed for client 192.168.1.1 read error = NT_STATUS_END_OF_FILE. These messages are what I'm concerned about. Do they mean a successful connection have been established? Maybe I should reinstall my server just in case.

Okay, I changed my root password just incase. Are these messages in the log as a result of that? Jan 30 12:06:00 Diabetes chpasswd[11699]: pam_unix(chpasswd:chauthtok): password changed for root Jan 30 12:06:00 Diabetes emhttpd: shcmd (395): cp /etc/passwd /etc/shadow /var/lib/samba/private/smbpasswd /boot/config Jan 30 12:06:00 Diabetes emhttpd: Starting services... Jan 30 12:06:00 Diabetes emhttpd: shcmd (397): /etc/rc.d/rc.samba restart Jan 30 12:06:00 Diabetes nmbd[14941]: [2022/01/30 12:06:00.768344, 0] ../../source3/nmbd/nmbd.c:59(terminate) Jan 30 12:06:00 Diabetes winbindd[14951]: [2022/01/30 12:06:00.768345, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Jan 30 12:06:00 Diabetes nmbd[14941]: Got SIGTERM: going down... Jan 30 12:06:00 Diabetes winbindd[14951]: Got sig[15] terminate (is_parent=1) Jan 30 12:06:00 Diabetes winbindd[16796]: [2022/01/30 12:06:00.768921, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Jan 30 12:06:00 Diabetes winbindd[16796]: Got sig[15] terminate (is_parent=0) Jan 30 12:06:00 Diabetes winbindd[28269]: [2022/01/30 12:06:00.769427, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Jan 30 12:06:00 Diabetes winbindd[28269]: Got sig[15] terminate (is_parent=0) Jan 30 12:06:02 Diabetes root: Starting Samba: /usr/sbin/smbd -D Jan 30 12:06:02 Diabetes root: /usr/sbin/nmbd -D Jan 30 12:06:02 Diabetes smbd[11829]: [2022/01/30 12:06:02.962714, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Jan 30 12:06:02 Diabetes smbd[11829]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections Jan 30 12:06:02 Diabetes root: /usr/sbin/wsdd Jan 30 12:06:02 Diabetes nmbd[11834]: [2022/01/30 12:06:02.972361, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Jan 30 12:06:02 Diabetes nmbd[11834]: daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections Jan 30 12:06:02 Diabetes root: /usr/sbin/winbindd -D Jan 30 12:06:03 Diabetes winbindd[11844]: [2022/01/30 12:06:03.011707, 0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache) Jan 30 12:06:03 Diabetes winbindd[11844]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jan 30 12:06:03 Diabetes winbindd[11844]: [2022/01/30 12:06:03.012207, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Jan 30 12:06:03 Diabetes winbindd[11844]: daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections Jan 30 12:06:03 Diabetes emhttpd: shcmd (406): /etc/rc.d/rc.nginx reload Jan 30 12:06:03 Diabetes root: Checking configuration for correct syntax and Jan 30 12:06:03 Diabetes root: then trying to open files referenced in configuration... Jan 30 12:06:03 Diabetes root: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok Jan 30 12:06:03 Diabetes root: nginx: configuration file /etc/nginx/nginx.conf test is successful Jan 30 12:06:03 Diabetes root: Reloading Nginx configuration... Jan 30 12:06:06 Diabetes emhttpd: shcmd (407): /usr/bin/php -f /usr/local/emhttp/webGui/include/UpdateDNS.php Jan 30 12:06:06 Diabetes root: No change to report Jan 30 12:06:06 Diabetes nginx: 2022/01/30 12:06:06 [alert] 11585#11585: *161141 open socket #37 left in connection 12 Jan 30 12:06:06 Diabetes nginx: 2022/01/30 12:06:06 [alert] 11585#11585: aborting Jan 30 12:06:24 Diabetes webGUI: Successful login user root from 192.168.1.225 Jan 30 12:06:26 Diabetes nmbd[11834]: [2022/01/30 12:06:26.005265, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Jan 30 12:06:26 Diabetes nmbd[11834]: ***** Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: Samba name server DIABETES is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: ***** Jan 30 12:06:26 Diabetes nmbd[11834]: [2022/01/30 12:06:26.005327, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Jan 30 12:06:26 Diabetes nmbd[11834]: ***** Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: Samba name server DIABETES is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: ***** Jan 30 12:06:26 Diabetes nmbd[11834]: [2022/01/30 12:06:26.005363, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Jan 30 12:06:26 Diabetes nmbd[11834]: ***** Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: Samba name server DIABETES is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.2 Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: ***** Jan 30 12:06:26 Diabetes nmbd[11834]: [2022/01/30 12:06:26.005399, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Jan 30 12:06:26 Diabetes nmbd[11834]: ***** Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: Samba name server DIABETES is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Jan 30 12:06:26 Diabetes nmbd[11834]: Jan 30 12:06:26 Diabetes nmbd[11834]: *****

Yes I suspect so. It seems they have (re)moved the option to enable/disable the scanner in the latest controller version however...

Well, the main issue presented in the topic has not been fixed. Does anyone know what it could be?

Here you go I see now it's Plex Transcoding taking a few GB of memory. diabetes-diagnostics-20220129-2247.zip

I have removed that now, thanks. But I'm still getting the message. On top of that I'm also getting "Rootfs file is getting full" message. I don't havent changed any docker containers for a few months so there is nothing new that should be writing there.

My log shows this every 2 hours. Is this something to be worried about? I have tried googling but I'm not sure I understand/have found what it means. Same minute and second each time. I'll attach diagnostics. My router is a Ubiquiti Dream Machine, which the connection seem to come from. I have most security scanning options enabled. Could it be that? Jan 29 03:03:43 Diabetes smbd[9244]: [2022/01/29 03:03:43.078606, 0] ../../lib/param/loadparm.c:1890(lpcfg_do_service_parameter) Jan 29 03:03:43 Diabetes smbd[9244]: Global parameter max protocol found in service section! Jan 29 03:03:43 Diabetes smbd[9245]: [2022/01/29 03:03:43.079136, 0] ../../lib/param/loadparm.c:1890(lpcfg_do_service_parameter) Jan 29 03:03:43 Diabetes smbd[9245]: Global parameter max protocol found in service section! Jan 29 03:03:43 Diabetes sshd[9242]: Connection from 192.168.1.1 port 36328 on 192.168.1.2 port 22 rdomain "" Jan 29 03:03:43 Diabetes sshd[9242]: error: kex_exchange_identification: Connection closed by remote host Jan 29 03:03:43 Diabetes sshd[9242]: Connection closed by 192.168.1.1 port 36328 Jan 29 03:03:54 Diabetes smbd[9244]: [2022/01/29 03:03:54.085072, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Jan 29 03:03:54 Diabetes smbd[9244]: read_fd_with_timeout failed for client 192.168.1.1 read error = NT_STATUS_END_OF_FILE. Jan 29 03:03:54 Diabetes smbd[9340]: [2022/01/29 03:03:54.087303, 0] ../../lib/param/loadparm.c:1890(lpcfg_do_service_parameter) Jan 29 03:03:54 Diabetes smbd[9340]: Global parameter max protocol found in service section! diabetes-diagnostics-20220129-1610.zip

Lian Li PC-343B, but it is EOL.

Also, it seems like the autotools tool fails to hardlink. I have this setup /share1/movies/movie1.ext want to hard link them to the following when files are done downloading. /share1/links/movie1/movie1.ext But autotools copies the file instead.

Hey, I have an old rutorrent container (captrutorrent) and want to migrate to this one. Can I just copy over the rtorrent session files and be good to go? I have no problem rechecking everything (~1500 torrents). All mappings are exactly the same on both rutorrent containers.

Yeh, I think it was worth the price. I bought mine for 99 Euros at amazon.de. It seems like it's more expensive now tho.