Jump to content
binhex

[Support] binhex - rTorrentVPN

2192 posts in this topic Last Reply

Recommended Posts

On 1/18/2020 at 3:41 PM, Cat_Seeder said:

Since netstat is not showing the desired port as LISTEN you may also try to dynamically set the port:


rtxmlrpc network.port_range.set '' "60210-60210"
rtxmlrpc dht.port.set '' "60210"

 

Thanks for the ideas. Do these lines go in rtorrent.conf or somewhere else?

Share this post


Link to post
18 hours ago, DavidAUK said:

Thanks for the ideas. Do these lines go in rtorrent.conf or somewhere else?

Those are shell commands directly inside the container. To open a shell inside your container you can issue the following command in your host:

docker exec -it <container name> sh
Edited by Cat_Seeder
Wrong argument for docker exec command

Share this post


Link to post
On 1/19/2020 at 7:14 AM, Cat_Seeder said:

Ratio info should be saved to rtorrent.rc file in your mounted volume (the plugin ultimately issues xmlrpc commands to modify ratio settings in rtorrent itself). If settings are reverting to default my guess would be a problem with either the mounted volume or file permissions.

it does appear to be saving on two servers through restarts now.  not sure why the original settings made did not hold.

Share this post


Link to post

hopefully last question....

 

files are added and downloaded correctly.  they are then moved using AutoTools to the correct location but end up in a "Pausing" state in the GUI and the path is not updated.

 

i haven't found a definitive cause to this issue.  i have checked permissions / folder owners.  (what are the correct settings?  nobody?

 

last thing i am leaning to - what should the UMASK during docker creation be set to 000, 1000?, 0? 777? or am I completely on the wrong path

Edited by morreale

Share this post


Link to post
1 hour ago, morreale said:

it does appear to be saving on two servers through restarts now.  not sure why the original settings made did not hold.

Well, at least it's fixed :)

1 hour ago, morreale said:

hopefully last question....

 

files are added and downloaded correctly.  they are then moved using AutoTools to the correct location but end up in a "Pausing" state in the GUI and the path is not updated.

 

i haven't found a definitive cause to this issue.  i have checked permissions / folder owners.  (what are the correct settings?  nobody?

Have you enabled "Start download automatically" in Autotools settings? https://github.com/Novik/ruTorrent/wiki/PluginAutotools 

Quote

last thing i am leaning to - what should the UMASK during docker creation be set to 000, 1000?, 0? 777? or am I completely on the wrong path

Depends on how paranoid you are about the container modifying file permissions in your host's mounted volumes. I personally let the container do whatever it wants (UMASK 000) with data and config files. I have a dedicated "docker" user on the host and am correctly setting user and group ids during container startup (see notes at: https://github.com/binhex/arch-rtorrentvpn/blob/master/README.md).

I'm actually enforcing file permissions at the host level instead of the container. I have a good set of ACL rules ( https://wiki.archlinux.org/index.php/Access_Control_Lists) that let docker do whatever it wants with its files and also grants some permissions to Plex (so that it can read fully downloaded files and write to some specific folders). Neither the docker nor the Plex user can do much else on my NAS. Otherwise the container is very well behaved and I don't have any reason to distrust it (and if @binhex, for whatever reason, decides to 777 random files we know where to complain :D).

Share this post


Link to post
15 hours ago, Cat_Seeder said:

Have you enabled "Start download automatically" in Autotools settings?

 

this doesn't happen when the operation type is "copy" only with "move"   (it also seems copy is doing exactly what i want and moving files from the incomplete folders to the complete folders)  i wonder if hardlink / softlink may be a better option

 

Yep.  All that seems to work correctly.  It is once the download has completed and the file is moved to the final location based on label,etc.  in the GUI it doesn't update its location and the torrent ends up in a "pausing" state.  i can do a "save to" and correct the location and it will check the file and confirm it has completed download but will not start seeding again until the container is restarted and a force recheck.  some people were saying the session files were not being updated after the move happened.  it was an open issue on the Novik Github but doesn't seem to have been resolved.

 

the tracker status is also "Download registered as completed, but hash check returned unfinished chunks."

 

Thanks for all the help by the way!

Edited by morreale

Share this post


Link to post

Has something been changed with the rutorrent-script with regard to nginx?

A few days ago my rutorrent UI stopped responding, and checking the logs I find this on startup:

2020-01-22 17:25:38,433 DEBG 'rutorrent-script' stderr output:
ln: failed to create hard link '/home/nobody/bin/nginx' => '/usr/bin/nginx'
2020-01-22 17:25:38,433 DEBG 'rutorrent-script' stderr output:
: Operation not permitted

2020-01-22 17:25:38,434 DEBG 'rutorrent-script' stderr output:
/home/nobody/rutorrent.sh: line 342: /home/nobody/bin/nginx: No such file or directory

2020-01-22 17:25:38,434 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 140256739577568 for <Subprocess at 140256739577520 with name rutorrent-script in state RUNNING> (stdout)>
2020-01-22 17:25:38,434 DEBG fd 25 closed, stopped monitoring <POutputDispatcher at 140256739636848 for <Subprocess at 140256739577520 with name rutorrent-script in state RUNNING> (stderr)>
2020-01-22 17:25:38,434 INFO exited: rutorrent-script (exit status 127; not expected)
2020-01-22 17:25:38,434 DEBG received SIGCHLD indicating a child quit
2020-01-22 17:25:40,703 DEBG 'watchdog-script' stdout output:
[info] rTorrent process started
[info] Waiting for rTorrent process to start listening on port 5000...

2020-01-22 17:25:40,713 DEBG 'watchdog-script' stdout output:
[info] rTorrent process listening on port 5000

2020-01-22 17:25:40,720 DEBG 'watchdog-script' stdout output:
[info] Autodl-irssi not enabled, skipping startup

2020-01-22 17:25:40,721 DEBG 'watchdog-script' stdout output:
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

2020-01-22 17:25:40,738 DEBG 'watchdog-script' stdout output:
[info] rTorrent running
[info] Initialising ruTorrent plugins (checking nginx is running)...

The process hangs for a long time waiting for nginx with nothing happening

Edited by 7thSon

Share this post


Link to post
38 minutes ago, 7thSon said:

ln: failed to create hard link '/home/nobody/bin/nginx' => '/usr/bin/nginx' 2020-01-22 17:25:38,433 DEBG 'rutorrent-script' stderr output: : Operation not permitted

github issue raised, i have a test tagged version up right now with what i think is the fix, feel free to test it out, see here:-

https://github.com/binhex/arch-rtorrentvpn/issues/139#issuecomment-577255180

 

edit - my fix looks good, building new 'latest' tagged image right now, please check for updates in about 30 mins.

Edited by binhex

Share this post


Link to post
1 hour ago, binhex said:

github issue raised, i have a test tagged version up right now with what i think is the fix, feel free to test it out, see here:-

https://github.com/binhex/arch-rtorrentvpn/issues/139#issuecomment-577255180

 

edit - my fix looks good, building new 'latest' tagged image right now, please check for updates in about 30 mins.

Yeah, it works again with that fix applied. Thanks.

Share this post


Link to post

Weird, since yesterday rtorrent chrashes my server.

Tried to delete the docker image and reapply the docker but all dockers i got installed works exept rtorrentvpn.

Tried only the rtorrent after removing docker image but unraid chrashes after 5-10min.

Any ideas whats causing this? No error in logs before the crash.

 

Heres a snippet from the crash.

 

Jan 22 20:49:55 Tower kernel: BUG: Bad page state in process shfs pfn:4c8407
Jan 22 20:49:55 Tower kernel: page:ffffea00132101c0 count:262144 mapcount:0 mapping:0000000000000000 index:0x1
Jan 22 20:49:55 Tower kernel: flags: 0x2fbff0000000000()
Jan 22 20:49:55 Tower kernel: raw: 02fbff0000000000 dead000000000100 dead000000000200 0000000000000000
Jan 22 20:49:55 Tower kernel: raw: 0000000000000001 0000000000000000 00040000ffffffff 0000000000000000
Jan 22 20:49:55 Tower kernel: page dumped because: nonzero _count
Jan 22 20:49:55 Tower kernel: Modules linked in: tun arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod it87 hwmon_vid igb i2c_algo_bit e1000e edac_mce_amd kvm_amd kvm hid_logitech_hidpp k10temp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc i2c_piix4 ahci i2c_core libahci mpt3sas aesni_intel hid_logitech_dj wmi_bmof mxm_wmi aes_x86_64 crypto_simd cryptd ccp raid_class scsi_transport_sas glue_helper button wmi pcc_cpufreq acpi_cpufreq [last unloaded: i2c_algo_bit]
Jan 22 20:49:55 Tower kernel: CPU: 4 PID: 25091 Comm: shfs Not tainted 4.19.94-Unraid #1
Jan 22 20:49:55 Tower kernel: Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 5008 06/24/2019
Jan 22 20:49:55 Tower kernel: Call Trace:
Jan 22 20:49:55 Tower kernel: dump_stack+0x67/0x83
Jan 22 20:49:55 Tower kernel: bad_page+0xec/0x106
Jan 22 20:49:55 Tower kernel: get_page_from_freelist+0x9f4/0xd0b
Jan 22 20:49:55 Tower kernel: __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: __do_page_cache_readahead+0x106/0x183
Jan 22 20:49:55 Tower kernel: ondemand_readahead+0x21d/0x22f
Jan 22 20:49:55 Tower kernel: generic_file_read_iter+0x243/0x6d0
Jan 22 20:49:55 Tower kernel: __vfs_read+0xf9/0x132
Jan 22 20:49:55 Tower kernel: vfs_read+0xa4/0x124
Jan 22 20:49:55 Tower kernel: ksys_pread64+0x5d/0x79
Jan 22 20:49:55 Tower kernel: do_syscall_64+0x57/0xf2
Jan 22 20:49:55 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 22 20:49:55 Tower kernel: RIP: 0033:0x154aa5f36e27
Jan 22 20:49:55 Tower kernel: Code: 08 89 3c 24 48 89 4c 24 18 e8 b5 f3 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 48 8b 74 24 08 8b 3c 24 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 04 24 e8 e5 f3 ff ff 48 8b
Jan 22 20:49:55 Tower kernel: RSP: 002b:0000154a7f3f8a50 EFLAGS: 00000297 ORIG_RAX: 0000000000000011
Jan 22 20:49:55 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 0000154aa5f36e27
Jan 22 20:49:55 Tower kernel: RDX: 0000000000020000 RSI: 0000154a602ba000 RDI: 0000000000000407
Jan 22 20:49:55 Tower kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
Jan 22 20:49:55 Tower kernel: R10: 000000001aa6a000 R11: 0000000000000297 R12: 0000154a7f3f8c18
Jan 22 20:49:55 Tower kernel: R13: 0000000000000000 R14: 0000154a6003ab78 R15: 0000000000000000
Jan 22 20:49:55 Tower kernel: Disabling lock debugging due to kernel taint
Jan 22 20:49:55 Tower kernel: BUG: Bad page state in process shfs pfn:4c840d
Jan 22 20:49:55 Tower kernel: page:ffffea0013210340 count:1048576 mapcount:0 mapping:0000000000000000 index:0x1
Jan 22 20:49:55 Tower kernel: flags: 0x2efff0000000000()
Jan 22 20:49:55 Tower kernel: raw: 02efff0000000000 dead000000000100 dead000000000200 0000000000000000
Jan 22 20:49:55 Tower kernel: raw: 0000000000000001 0000000000000000 00100000ffffffff 0000000000000000
Jan 22 20:49:55 Tower kernel: page dumped because: nonzero _count
Jan 22 20:49:55 Tower kernel: Modules linked in: tun arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod it87 hwmon_vid igb i2c_algo_bit e1000e edac_mce_amd kvm_amd kvm hid_logitech_hidpp k10temp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc i2c_piix4 ahci i2c_core libahci mpt3sas aesni_intel hid_logitech_dj wmi_bmof mxm_wmi aes_x86_64 crypto_simd cryptd ccp raid_class scsi_transport_sas glue_helper button wmi pcc_cpufreq acpi_cpufreq [last unloaded: i2c_algo_bit]
Jan 22 20:49:55 Tower kernel: CPU: 4 PID: 25091 Comm: shfs Tainted: G B 4.19.94-Unraid #1
Jan 22 20:49:55 Tower kernel: Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 5008 06/24/2019
Jan 22 20:49:55 Tower kernel: Call Trace:
Jan 22 20:49:55 Tower kernel: dump_stack+0x67/0x83
Jan 22 20:49:55 Tower kernel: bad_page+0xec/0x106
Jan 22 20:49:55 Tower kernel: get_page_from_freelist+0x9f4/0xd0b
Jan 22 20:49:55 Tower kernel: __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: __do_page_cache_readahead+0x106/0x183
Jan 22 20:49:55 Tower kernel: ondemand_readahead+0x21d/0x22f
Jan 22 20:49:55 Tower kernel: generic_file_read_iter+0x243/0x6d0
Jan 22 20:49:55 Tower kernel: __vfs_read+0xf9/0x132
Jan 22 20:49:55 Tower kernel: vfs_read+0xa4/0x124
Jan 22 20:49:55 Tower kernel: ksys_pread64+0x5d/0x79
Jan 22 20:49:55 Tower kernel: do_syscall_64+0x57/0xf2
Jan 22 20:49:55 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 22 20:49:55 Tower kernel: RIP: 0033:0x154aa5f36e27
Jan 22 20:49:55 Tower kernel: Code: 08 89 3c 24 48 89 4c 24 18 e8 b5 f3 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 48 8b 74 24 08 8b 3c 24 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 04 24 e8 e5 f3 ff ff 48 8b
Jan 22 20:49:55 Tower kernel: RSP: 002b:0000154a7f3f8a50 EFLAGS: 00000297 ORIG_RAX: 0000000000000011
Jan 22 20:49:55 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 0000154aa5f36e27
Jan 22 20:49:55 Tower kernel: RDX: 0000000000020000 RSI: 0000154a602ba000 RDI: 0000000000000407
Jan 22 20:49:55 Tower kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
Jan 22 20:49:55 Tower kernel: R10: 000000001aa6a000 R11: 0000000000000297 R12: 0000154a7f3f8c18
Jan 22 20:49:55 Tower kernel: R13: 0000000000000000 R14: 0000154a6003ab78 R15: 0000000000000000
Jan 22 20:49:55 Tower kernel: BUG: Bad page state in process shfs pfn:4c840e
Jan 22 20:49:55 Tower kernel: page:ffffea0013210380 count:1310720 mapcount:0 mapping:0000000000000000 index:0x1
Jan 22 20:49:55 Tower kernel: flags: 0x2ebff0000000000()
Jan 22 20:49:55 Tower kernel: raw: 02ebff0000000000 dead000000000100 dead000000000200 0000000000000000
Jan 22 20:49:55 Tower kernel: raw: 0000000000000001 0000000000000000 00140000ffffffff 0000000000000000
Jan 22 20:49:55 Tower kernel: page dumped because: nonzero _count
Jan 22 20:49:55 Tower kernel: Modules linked in: tun arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod it87 hwmon_vid igb i2c_algo_bit e1000e edac_mce_amd kvm_amd kvm hid_logitech_hidpp k10temp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc i2c_piix4 ahci i2c_core libahci mpt3sas aesni_intel hid_logitech_dj wmi_bmof mxm_wmi aes_x86_64 crypto_simd cryptd ccp raid_class scsi_transport_sas glue_helper button wmi pcc_cpufreq acpi_cpufreq [last unloaded: i2c_algo_bit]

 

Share this post


Link to post
1 hour ago, Pirate said:

Any ideas whats causing this? No error in logs before the crash.

 

Heres a snippet from the crash.

 


Jan 22 20:49:55 Tower kernel: BUG: Bad page state in process shfs pfn:4c8407
Jan 22 20:49:55 Tower kernel: page:ffffea00132101c0 count:262144 mapcount:0 mapping:0000000000000000 index:0x1
Jan 22 20:49:55 Tower kernel: flags: 0x2fbff0000000000()
Jan 22 20:49:55 Tower kernel: raw: 02fbff0000000000 dead000000000100 dead000000000200 0000000000000000
Jan 22 20:49:55 Tower kernel: raw: 0000000000000001 0000000000000000 00040000ffffffff 0000000000000000
Jan 22 20:49:55 Tower kernel: page dumped because: nonzero _count
Jan 22 20:49:55 Tower kernel: Modules linked in: tun arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod it87 hwmon_vid igb i2c_algo_bit e1000e edac_mce_amd kvm_amd kvm hid_logitech_hidpp k10temp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc i2c_piix4 ahci i2c_core libahci mpt3sas aesni_intel hid_logitech_dj wmi_bmof mxm_wmi aes_x86_64 crypto_simd cryptd ccp raid_class scsi_transport_sas glue_helper button wmi pcc_cpufreq acpi_cpufreq [last unloaded: i2c_algo_bit]
Jan 22 20:49:55 Tower kernel: CPU: 4 PID: 25091 Comm: shfs Not tainted 4.19.94-Unraid #1
Jan 22 20:49:55 Tower kernel: Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 5008 06/24/2019
Jan 22 20:49:55 Tower kernel: Call Trace:
Jan 22 20:49:55 Tower kernel: dump_stack+0x67/0x83
Jan 22 20:49:55 Tower kernel: bad_page+0xec/0x106
Jan 22 20:49:55 Tower kernel: get_page_from_freelist+0x9f4/0xd0b
Jan 22 20:49:55 Tower kernel: __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: __do_page_cache_readahead+0x106/0x183
Jan 22 20:49:55 Tower kernel: ondemand_readahead+0x21d/0x22f
Jan 22 20:49:55 Tower kernel: generic_file_read_iter+0x243/0x6d0
Jan 22 20:49:55 Tower kernel: __vfs_read+0xf9/0x132
Jan 22 20:49:55 Tower kernel: vfs_read+0xa4/0x124
Jan 22 20:49:55 Tower kernel: ksys_pread64+0x5d/0x79
Jan 22 20:49:55 Tower kernel: do_syscall_64+0x57/0xf2
Jan 22 20:49:55 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 22 20:49:55 Tower kernel: RIP: 0033:0x154aa5f36e27
Jan 22 20:49:55 Tower kernel: Code: 08 89 3c 24 48 89 4c 24 18 e8 b5 f3 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 48 8b 74 24 08 8b 3c 24 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 04 24 e8 e5 f3 ff ff 48 8b
Jan 22 20:49:55 Tower kernel: RSP: 002b:0000154a7f3f8a50 EFLAGS: 00000297 ORIG_RAX: 0000000000000011
Jan 22 20:49:55 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 0000154aa5f36e27
Jan 22 20:49:55 Tower kernel: RDX: 0000000000020000 RSI: 0000154a602ba000 RDI: 0000000000000407
Jan 22 20:49:55 Tower kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
Jan 22 20:49:55 Tower kernel: R10: 000000001aa6a000 R11: 0000000000000297 R12: 0000154a7f3f8c18
Jan 22 20:49:55 Tower kernel: R13: 0000000000000000 R14: 0000154a6003ab78 R15: 0000000000000000
Jan 22 20:49:55 Tower kernel: Disabling lock debugging due to kernel taint
Jan 22 20:49:55 Tower kernel: BUG: Bad page state in process shfs pfn:4c840d
Jan 22 20:49:55 Tower kernel: page:ffffea0013210340 count:1048576 mapcount:0 mapping:0000000000000000 index:0x1
Jan 22 20:49:55 Tower kernel: flags: 0x2efff0000000000()
Jan 22 20:49:55 Tower kernel: raw: 02efff0000000000 dead000000000100 dead000000000200 0000000000000000
Jan 22 20:49:55 Tower kernel: raw: 0000000000000001 0000000000000000 00100000ffffffff 0000000000000000
Jan 22 20:49:55 Tower kernel: page dumped because: nonzero _count
Jan 22 20:49:55 Tower kernel: Modules linked in: tun arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod it87 hwmon_vid igb i2c_algo_bit e1000e edac_mce_amd kvm_amd kvm hid_logitech_hidpp k10temp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc i2c_piix4 ahci i2c_core libahci mpt3sas aesni_intel hid_logitech_dj wmi_bmof mxm_wmi aes_x86_64 crypto_simd cryptd ccp raid_class scsi_transport_sas glue_helper button wmi pcc_cpufreq acpi_cpufreq [last unloaded: i2c_algo_bit]
Jan 22 20:49:55 Tower kernel: CPU: 4 PID: 25091 Comm: shfs Tainted: G B 4.19.94-Unraid #1
Jan 22 20:49:55 Tower kernel: Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 5008 06/24/2019
Jan 22 20:49:55 Tower kernel: Call Trace:
Jan 22 20:49:55 Tower kernel: dump_stack+0x67/0x83
Jan 22 20:49:55 Tower kernel: bad_page+0xec/0x106
Jan 22 20:49:55 Tower kernel: get_page_from_freelist+0x9f4/0xd0b
Jan 22 20:49:55 Tower kernel: __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __alloc_pages_nodemask+0x150/0xae1
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x35/0x70
Jan 22 20:49:55 Tower kernel: ? __switch_to_asm+0x41/0x70
Jan 22 20:49:55 Tower kernel: __do_page_cache_readahead+0x106/0x183
Jan 22 20:49:55 Tower kernel: ondemand_readahead+0x21d/0x22f
Jan 22 20:49:55 Tower kernel: generic_file_read_iter+0x243/0x6d0
Jan 22 20:49:55 Tower kernel: __vfs_read+0xf9/0x132
Jan 22 20:49:55 Tower kernel: vfs_read+0xa4/0x124
Jan 22 20:49:55 Tower kernel: ksys_pread64+0x5d/0x79
Jan 22 20:49:55 Tower kernel: do_syscall_64+0x57/0xf2
Jan 22 20:49:55 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 22 20:49:55 Tower kernel: RIP: 0033:0x154aa5f36e27
Jan 22 20:49:55 Tower kernel: Code: 08 89 3c 24 48 89 4c 24 18 e8 b5 f3 ff ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 48 8b 74 24 08 8b 3c 24 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 04 24 e8 e5 f3 ff ff 48 8b
Jan 22 20:49:55 Tower kernel: RSP: 002b:0000154a7f3f8a50 EFLAGS: 00000297 ORIG_RAX: 0000000000000011
Jan 22 20:49:55 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 0000154aa5f36e27
Jan 22 20:49:55 Tower kernel: RDX: 0000000000020000 RSI: 0000154a602ba000 RDI: 0000000000000407
Jan 22 20:49:55 Tower kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
Jan 22 20:49:55 Tower kernel: R10: 000000001aa6a000 R11: 0000000000000297 R12: 0000154a7f3f8c18
Jan 22 20:49:55 Tower kernel: R13: 0000000000000000 R14: 0000154a6003ab78 R15: 0000000000000000
Jan 22 20:49:55 Tower kernel: BUG: Bad page state in process shfs pfn:4c840e
Jan 22 20:49:55 Tower kernel: page:ffffea0013210380 count:1310720 mapcount:0 mapping:0000000000000000 index:0x1
Jan 22 20:49:55 Tower kernel: flags: 0x2ebff0000000000()
Jan 22 20:49:55 Tower kernel: raw: 02ebff0000000000 dead000000000100 dead000000000200 0000000000000000
Jan 22 20:49:55 Tower kernel: raw: 0000000000000001 0000000000000000 00140000ffffffff 0000000000000000
Jan 22 20:49:55 Tower kernel: page dumped because: nonzero _count
Jan 22 20:49:55 Tower kernel: Modules linked in: tun arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xt_nat macvlan ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod it87 hwmon_vid igb i2c_algo_bit e1000e edac_mce_amd kvm_amd kvm hid_logitech_hidpp k10temp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc i2c_piix4 ahci i2c_core libahci mpt3sas aesni_intel hid_logitech_dj wmi_bmof mxm_wmi aes_x86_64 crypto_simd cryptd ccp raid_class scsi_transport_sas glue_helper button wmi pcc_cpufreq acpi_cpufreq [last unloaded: i2c_algo_bit]

 

Wow, kernel crash due to shfs, that brings me back down memory lane. Unfortunately I don't have experience with Unraid. Nevertheless a quick search through the forums tells me that shfs is still not the greatest piece of software ever written.

Although I'm over my head here, if I may suggest a path to start troubleshooting your issue, I would try to start a new rtorrent container with fresh /data and /config volumes bound to locations on a local drive. If it works then try again mounting volumes on a separate network mount, finally try a fresh container with volumes on the same network mount. If everything works it may be that some of your old data is corrupted, if it fails, knowing at what exactly step it failed may help you understand what is happening.

 

Kind regards, 

Share this post


Link to post

any idea why this would be required on a newly built server running 6.8.1 vs one that is a few months old.  the new server is only running the binhex_rtorrent docker whereas the other is running several of the other binhex vpn containers and i have never seen the iptable_mangle.ko issue.  only noticed it on the new one after not being able to access the gui while connected via vpn.

 

echo "# force iptable mangle module to load (required for *vpn dockers)" >> /boot/config/go

echo "/sbin/modprobe iptable_mangle" >> /boot/config/go

 

thanks!

Edited by morreale

Share this post


Link to post
10 hours ago, morreale said:

only noticed it on the new one after not being able to access the gui while connected via vpn.

you mean not being able to access the gui OUTSIDE of your lan right?, if you are talking about accessing the gui INSIDE your lan then iptable_mangle has nothing to do with this.

Share this post


Link to post

First off, thank you binhex for these great dockers. I got mine setup pretty easily last night!

 

I have everything working, but I am struggling with the port forward from AirVPN. I created a forward with them for port 7859 external to 7859 internal. I then edited the rtorrent.rc config file so that it has these lines set:

dht.mode.set = on
dht.port.set = 7859

Then in the GUI for ruTorrent, I went to settings -> Bittorrent and changed the port there to 7859.

 

I then restarted the docker.

 

The problem I am seeing is that the port check at the bottom of ruTorrent has the red exclamation and tells me that port 6881 is closed, and if I do a port check from AirVPN, it does not appear to work either. So I am unsure where else I need to change that port. 

 

Ok, unrelated to that I am curious if the deluge-VPN docker supports RSS feeds for downloading. Mostly because I am not a huge fan or rTorrent.

Share this post


Link to post

After some reading, I went into rtorrent.rc file again and uncommented the line about incoming port range, and then set that to 7859. Saved and restarted the docker and now it won't come back up at all. 

 

network.port_range.set = 7859-7859

 

2020-01-23 11:06:43,760 DEBG 'watchdog-script' stdout output:
[info] Removing any rTorrent session lock files left over from the previous run...

2020-01-23 11:06:43,762 DEBG 'watchdog-script' stdout output:
[info] Attempting to start rTorrent...

2020-01-23 11:06:43,765 DEBG 'watchdog-script' stdout output:
Script started, file is /home/nobody/typescript

2020-01-23 11:06:43,796 DEBG 'watchdog-script' stdout output:
Script done, file is /home/nobody/typescript

2020-01-23 11:07:13,010 DEBG 'watchdog-script' stdout output:
[warn] Wait for rTorrent process to start aborted, too many retries

2020-01-23 11:07:13,017 DEBG 'watchdog-script' stdout output:
[info] Autodl-irssi not enabled, skipping startup
[info] Initialising ruTorrent plugins (checking rTorrent is running)...

 

And it just sits there indefinitely, not logging anything else.

Edited by lutiana

Share this post


Link to post
19 hours ago, Cat_Seeder said:

Wow, kernel crash due to shfs, that brings me back down memory lane. Unfortunately I don't have experience with Unraid. Nevertheless a quick search through the forums tells me that shfs is still not the greatest piece of software ever written.

Although I'm over my head here, if I may suggest a path to start troubleshooting your issue, I would try to start a new rtorrent container with fresh /data and /config volumes bound to locations on a local drive. If it works then try again mounting volumes on a separate network mount, finally try a fresh container with volumes on the same network mount. If everything works it may be that some of your old data is corrupted, if it fails, knowing at what exactly step it failed may help you understand what is happening.

 

Kind regards, 

Was weird that it worked with all the other dockers and only rtorrent crashing it, but i found the problem.

It was a 16Gb ram stick that threw errors.

Share this post


Link to post
After some reading, I went into rtorrent.rc file again and uncommented the line about incoming port range, and then set that to 7859. Saved and restarted the docker and now it won't come back up at all. 
 
2020-01-23 11:06:43,760 DEBG 'watchdog-script' stdout output:[info] Removing any rTorrent session lock files left over from the previous run...2020-01-23 11:06:43,762 DEBG 'watchdog-script' stdout output:[info] Attempting to start rTorrent...2020-01-23 11:06:43,765 DEBG 'watchdog-script' stdout output:Script started, file is /home/nobody/typescript2020-01-23 11:06:43,796 DEBG 'watchdog-script' stdout output:Script done, file is /home/nobody/typescript2020-01-23 11:07:13,010 DEBG 'watchdog-script' stdout output:[warn] Wait for rTorrent process to start aborted, too many retries2020-01-23 11:07:13,017 DEBG 'watchdog-script' stdout output:[info] Autodl-irssi not enabled, skipping startup[info] Initialising ruTorrent plugins (checking rTorrent is running)...

 
And it just sits there indefinitely, not logging anything else.

What did you use to edit the file? I suspect line endings have been changed

Sent from my CLT-L09 using Tapatalk

Share this post


Link to post
13 minutes ago, binhex said:

What did you use to edit the file? I suspect line endings have been changed

Sent from my CLT-L09 using Tapatalk
 

I think the restart issue was definitely a type on my part. I re-typed it again, making sure it was right. Saved the file and not it has come up and my port checks out ok. I was using nano to edit it, so no idea how it got goofed up.

 

Does rtorrent have a config check command like Apache and some others do?

Share this post


Link to post
29 minutes ago, lutiana said:

Does rtorrent have a config check command like Apache and some others do?

not that im aware of.

Share this post


Link to post
20 hours ago, binhex said:

you mean not being able to access the gui OUTSIDE of your lan right?, if you are talking about accessing the gui INSIDE your lan then iptable_mangle has nothing to do with this.

I'm newly having this issue as well, while trying to access your qbittorrentvpn container outside of my LAN (I know this is the wrong thread, but it seems like the same issue). Not exactly sure when it started, in the last few days though. Seems ok in-house. I deleted the container and the config for a fresh install and same thing. Any help would be greatly appreciated.

 

Here is the log with UN and PW deleted.

 

ErrorWarningSystemArrayLogin


Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2020-01-24 18:31:49.453085 [info] System information Linux e96e13216ead 4.19.94-Unraid #1 SMP Thu Jan 9 08:20:36 PST 2020 x86_64 GNU/Linux
2020-01-24 18:31:49.539095 [info] PUID defined as '99'
2020-01-24 18:31:49.863142 [info] PGID defined as '100'
2020-01-24 18:31:50.269281 [info] UMASK defined as '000'
2020-01-24 18:31:50.317676 [info] Setting permissions recursively on volume mappings...
2020-01-24 18:31:50.959110 [info] VPN_ENABLED defined as 'yes'
2020-01-24 18:31:51.077181 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2020-01-24 18:34:41.613955 [info] System information Linux e96e13216ead 4.19.94-Unraid #1 SMP Thu Jan 9 08:20:36 PST 2020 x86_64 GNU/Linux
2020-01-24 18:34:41.663126 [info] PUID defined as '99'
2020-01-24 18:34:41.715391 [info] PGID defined as '100'
2020-01-24 18:34:41.873169 [info] UMASK defined as '000'
2020-01-24 18:34:41.921989 [info] Permissions already set for volume mappings
2020-01-24 18:34:41.990786 [info] VPN_ENABLED defined as 'yes'
2020-01-24 18:34:42.049963 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/0C0F5FC9-9A21-4E8F-ADF4-78C22D53E726_us-sf_openvpn.ovpn
2020-01-24 18:34:42.157148 [info] VPN remote line defined as 'remote us-sf.vpnunlimitedapp.com 1194'
2020-01-24 18:34:42.208023 [info] VPN_REMOTE defined as 'us-sf.vpnunlimitedapp.com'
2020-01-24 18:34:42.259106 [info] VPN_PORT defined as '1194'
2020-01-24 18:34:42.313931 [info] VPN_PROTOCOL defined as 'udp'
2020-01-24 18:34:42.363237 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-01-24 18:34:42.413479 [info] VPN_PROV defined as 'custom'
2020-01-24 18:34:42.477205 [info] LAN_NETWORK defined as '192.168.0.0/24'
2020-01-24 18:34:42.527449 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2020-01-24 18:34:42.576336 [info] VPN_USER defined as 'xxxxxx'
2020-01-24 18:34:42.624870 [info] VPN_PASS defined as 'xxxxxx'
2020-01-24 18:34:42.678636 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-01-24 18:34:42.727447 [info] ENABLE_PRIVOXY defined as 'no'
2020-01-24 18:34:42.776571 [info] WEBUI_PORT defined as '8080'
2020-01-24 18:34:42.865980 [info] Deleting files in /tmp (non recursive)...
2020-01-24 18:34:42.912344 [info] Starting Supervisor...
2020-01-24 18:34:44,716 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2020-01-24 18:34:44,717 INFO Set uid to user 0 succeeded
2020-01-24 18:34:44,722 INFO supervisord started with pid 6
2020-01-24 18:34:45,725 INFO spawned: 'start-script' with pid 152
2020-01-24 18:34:45,728 INFO spawned: 'watchdog-script' with pid 153
2020-01-24 18:34:45,729 INFO reaped unknown pid 7
2020-01-24 18:34:45,738 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-01-24 18:34:45,739 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-01-24 18:34:45,739 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-01-24 18:34:45,740 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file doesnt exist, copying default to /config/qBittorrent/config/...

2020-01-24 18:34:45,754 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2020-01-24 18:34:45,759 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2020-01-24 18:34:45,778 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2020-01-24 18:34:45,842 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-01-24 18:34:45,847 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-01-24 18:34:45,852 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-01-24 18:34:45,857 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-01-24 18:34:45,862 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-01-24 18:34:45,866 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-01-24 18:34:45,871 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-01-24 18:34:45,876 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-01-24 18:34:45,881 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-01-24 18:35:00,991 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2020-01-24 18:35:00,993 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.94-Unraid

2020-01-24 18:35:00,993 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2020-01-24 18:35:00,995 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2020-01-24 18:35:00,995 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2020-01-24 18:35:01,044 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2020-01-24 18:35:01,049 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2020-01-24 18:35:01,051 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-01-24 18:35:01,053 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
192.168.0.0/24 via 172.17.0.1 dev eth0

2020-01-24 18:35:01,053 DEBG 'start-script' stdout output:
--------------------

2020-01-24 18:35:01,158 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-01-24 18:35:01,160 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2020-01-24 18:35:01,162 DEBG 'start-script' stdout output:
--------------------

2020-01-24 18:35:01,164 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2020-01-24 18:35:01,394 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:01 2020 WARNING: file 'credentials.conf' is group or others accessible
Fri Jan 24 18:35:01 2020 OpenVPN 2.4.8 [git:makepkg/3976acda9bf10b5e+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan 3 2020
Fri Jan 24 18:35:01 2020 library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10

2020-01-24 18:35:01,395 DEBG 'start-script' stdout output:
[info] OpenVPN started

2020-01-24 18:35:01,395 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:01 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-01-24 18:35:01,403 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:01 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]209.58.135.108:1194
Fri Jan 24 18:35:01 2020 UDP link local: (not bound)
Fri Jan 24 18:35:01 2020 UDP link remote: [AF_INET]209.58.135.108:1194

2020-01-24 18:35:02,182 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:02 2020 [openvpn2.vpnunlimitedapp.com] Peer Connection Initiated with [AF_INET]209.58.135.108:1194

2020-01-24 18:35:08,736 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:08 2020 TUN/TAP device tun0 opened
Fri Jan 24 18:35:08 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-01-24 18:35:08,738 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:08 2020 /usr/bin/ip addr add dev tun0 local 10.200.0.86 peer 10.200.0.85

2020-01-24 18:35:08,740 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:08 2020 /root/openvpnup.sh tun0 1500 1553 10.200.0.86 10.200.0.85 init

2020-01-24 18:35:08,750 DEBG 'start-script' stdout output:
Fri Jan 24 18:35:08 2020 Initialization Sequence Completed

2020-01-24 18:35:08,885 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2020-01-24 18:35:08,886 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-01-24 18:35:09,219 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address '172.217.16.36'

2020-01-24 18:35:09,223 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-01-24 18:35:09,986 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 209.58.135.108

2020-01-24 18:35:10,074 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.200.0.86 different, marking for reconfigure

2020-01-24 18:35:10,079 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2020-01-24 18:35:10,080 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2020-01-24 18:35:10,081 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2020-01-24 18:35:10,602 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2020-01-24 18:35:10,728 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

Share this post


Link to post

@xMaverickx did you run the command as suggested in the log? :-

[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

 

Share this post


Link to post

Im having a weird problem...

rtTorrent i showing it is downloading my torrents but when i go to the folder it is supposed to download to nothing is there.

It says it is downloading to the correct place in the gui and it even uploads when done...

Share this post


Link to post
1 hour ago, PetterH said:

Im having a weird problem...

rtTorrent i showing it is downloading my torrents but when i go to the folder it is supposed to download to nothing is there.

It says it is downloading to the correct place in the gui and it even uploads when done...

okei so i reinstalled the docker, deleted appdata folder and restarted unraid and now it magiclally works... i love server problems... maybe it just needed a restart but hey

Share this post


Link to post
8 hours ago, binhex said:

@xMaverickx did you run the command as suggested in the log? :-


[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

 

Sorry for my ignorance, I'm new to unraid and have only minor Linux experience in general.

 

I saw that line and googled it but couldn't find anything useful so I thought I'd ask before I effed anything up.

 

Do I just type /sbin/modprobe iptable_mangle into the terminal?

Share this post


Link to post
Sorry for my ignorance, I'm new to unraid and have only minor Linux experience in general.
 
I saw that line and googled it but couldn't find anything useful so I thought I'd ask before I effed anything up.
 
Do I just type /sbin/modprobe iptable_mangle into the terminal?
Yes

Sent from my CLT-L09 using Tapatalk

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.