Jump to content

drawmonster

Members
  • Content Count

    56
  • Joined

  • Last visited

Community Reputation

3 Neutral

About drawmonster

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

453 profile views
  1. Well, I thought I had figured out my issue, but I'm getting timeouts and webgui freezes with private tracker torrents now as well. But I did get an error message in container logs now, finally. 2020-02-18 18:37:07,030 DEBG 'rutorrent-script' stderr output: 2020/02/18 18:37:07 [error] 687#687: *212 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.18.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.227:9080" Anyone seen this one before?
  2. There are some fixes in those topics I linked too about the GUI freezing up on public torrents. Is it possible to use those on this container? Maybe from the command line or something? @binhex Also, anyone else reading this, are you able to use public torrents without the GUI freezing up constantly? I can recreate my issue very easily by adding any Linux iso torrent using the RARBG trackers. Upon adding, the GUI will quickly start becoming unresponsive. Trying to refresh it will hang and load for a few seconds or minutes or longer. Removing the torrent fixes the issue instantly. Curious if anyone else is experiencing this.
  3. I'm not having any luck searching this thread for the answer I need. Basically, got everything up and running fine. VPN works. GUI works. But as soon as I add a single torrent, the GUI starts freezing up and becomes unresponsive. If I refresh the GUI, it will sit on "Loading" for a random amount of time. A couple minutes sometimes, others it never seems to load the GUI at all. Only changes I've made are the listening port to the one specified by my VPN. Is there something simple that I'm not finding in my searches to fix this? Edit: This appears to be related to "stuck" trackers. Found these threads for reference: and this github issue: https://github.com/rakshasa/rtorrent/issues/180 For me, a certain public tracker would immediately freeze the UI as soon as a torrent using that tracker was added. Removing that torrent would fix the issue. @binhex Have you ever dealt with this sort of issue in the past?
  4. You know us. "PANIC, PANIC, FIRE, DEATH, PANIC, BEES!!!"
  5. Completely removing and reinstalling CA also doesn't work.
  6. Same here. MD5 error and no more apps tab.
  7. Got this up and going with my reverse proxy. Got a couple issues though. I can't set a message for services directly. Global works, but messages, for say Plex, just don't appear. Also the time is off for the messages. If I set it for 3 p.m. my time, the message will have a time of 6 p.m. on the main page. Anyone else seeing these issues?
  8. I added an external USB hard drive last night. It’s plugged directly into my Unraid server. The partition is named “Seeding”. Now I’m getting the above messages via email hourly. So it seems like the hard drive is being seen as an SSD possibly. And it’s trying to take SSD related actions on it. I did find and turn off the “discard” option in Unassigned Devices. I then rebooted the server. Still getting the error though. Anyone had this or know how I can fix it?
  9. Two servers updated without a hitch.
  10. Just had my certificates expire. Restarted the LE container several times, but it never tried to renew the cert. I also backup my appdata every night, so the container gets restarted nightly. Ended up having to run the renew command manually. I had gotten some emails saying the certificates were set to expire today, but I just assumed that was normal and that they would get renewed automatically. Guess not. cronjob running on Sun Nov 17 02:08:00 CST 2019 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/mydomain.com.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certs are not due for renewal yet: /etc/letsencrypt/live/mydomain.com/fullchain.pem expires on 2019-12-26 (skipped) No renewals were attempted. No hooks were run. I found this repeated over and over in the letsencrypt logs. So it new it was expiring, but never renewed it. Is there anything glaringly obvious that would keep the LE container from renewing the certificates automatically?
  11. So I've had a two full Unraid crashes/hangs in the last 3 days. I'm not getting any errors or warnings from Unraid and the physical server keeps running. Unraid just hangs. I have to restart the server, and it will come back up and work fine. It will also try to start a parity check after the reboot. Checking the monitor I have hooked up to the physical server at time of the hang/crash just shows Unraid scrolling errors, getting to the root login, then scrolling more errors. It's a loop. Luckily I had my system log mirrored to my other server at the time of this latest crash. References to "dma" and "ata" in the log makes me think it might be some sort of SAS controller issue? I am using the onboard Broadcom 2308 SAS2 controller on my mobo that then hits the SAS expander in my Supermicro case. Syslog from the crash below and attached system diagnostics I got after it the server was restarted and running normally again. Dec 22 11:18:43 Unraid kernel: ------------[ cut here ]------------ Dec 22 11:18:43 Unraid kernel: kernel BUG at include/linux/dma-mapping.h:268! Dec 22 11:18:43 Unraid kernel: invalid opcode: 0000 [#1] SMP PTI Dec 22 11:18:43 Unraid kernel: CPU: 18 PID: 2214 Comm: kworker/18:1H Not tainted 4.19.88-Unraid #1 Dec 22 11:18:43 Unraid kernel: Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.3 08/23/2018 Dec 22 11:18:43 Unraid kernel: Workqueue: kblockd blk_mq_run_work_fn Dec 22 11:18:43 Unraid kernel: RIP: 0010:ata_qc_issue+0xfc/0x195 Dec 22 11:18:43 Unraid kernel: Code: 8b b5 a0 00 00 00 48 8b b8 40 35 00 00 48 85 ff 74 0c 48 8b 87 10 02 00 00 48 85 c0 75 07 48 8b 05 64 f3 9b 00 83 f9 02 76 02 <0f> 0b 45 31 c0 48 8b 40 30 e8 b1 5e 5a 00 85 c0 79 02 0f 0b 74 6b Dec 22 11:18:43 Unraid kernel: RSP: 0018:ffffc90007023cf0 EFLAGS: 00010002 Dec 22 11:18:43 Unraid kernel: RAX: ffffffff81c678c0 RBX: ffff888842460000 RCX: 0000000000000003 Dec 22 11:18:43 Unraid kernel: RDX: 0000000000000001 RSI: ffff8888398a3bd0 RDI: ffff88905b33d0a8 Dec 22 11:18:43 Unraid kernel: RBP: ffff8888424606d0 R08: 0000000000000087 R09: 0000000000000000 Dec 22 11:18:43 Unraid kernel: R10: 0000000000000200 R11: fefefefefefefeff R12: ffff888842462040 Dec 22 11:18:43 Unraid kernel: R13: ffff8888594cd800 R14: ffff888842460000 R15: ffff8888398a3900 Dec 22 11:18:43 Unraid kernel: FS: 0000000000000000(0000) GS:ffff88905f800000(0000) knlGS:0000000000000000 Dec 22 11:18:43 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 22 11:18:43 Unraid kernel: CR2: 0000145d01098ff8 CR3: 0000000001e0a002 CR4: 00000000001606e0 Dec 22 11:18:43 Unraid kernel: Call Trace: Dec 22 11:18:43 Unraid kernel: ? ata_scsi_verify_xlat+0x22d/0x22d Dec 22 11:18:43 Unraid kernel: ata_scsi_translate+0xdd/0x14d Dec 22 11:18:43 Unraid kernel: ata_scsi_queuecmd+0x254/0x2a8 Dec 22 11:18:43 Unraid kernel: scsi_dispatch_cmd+0xa2/0xca Dec 22 11:18:43 Unraid kernel: scsi_queue_rq+0x395/0x447 Dec 22 11:18:43 Unraid kernel: blk_mq_dispatch_rq_list+0x2b9/0x491 Dec 22 11:18:43 Unraid kernel: ? __switch_to_asm+0x35/0x70 Dec 22 11:18:43 Unraid kernel: ? __switch_to_asm+0x35/0x70 Dec 22 11:18:43 Unraid kernel: ? __switch_to_asm+0x41/0x70 Dec 22 11:18:43 Unraid kernel: ? syscall_return_via_sysret+0x14/0x83 Dec 22 11:18:43 Unraid kernel: blk_mq_sched_dispatch_requests+0xe6/0x14b Dec 22 11:18:43 Unraid kernel: __blk_mq_run_hw_queue+0xaf/0xd6 Dec 22 11:18:43 Unraid kernel: process_one_work+0x16e/0x24f Dec 22 11:18:43 Unraid kernel: worker_thread+0x1e2/0x2b8 Dec 22 11:18:43 Unraid kernel: ? rescuer_thread+0x29e/0x29e Dec 22 11:18:43 Unraid kernel: kthread+0x10c/0x114 Dec 22 11:18:43 Unraid kernel: ? kthread_park+0x89/0x89 Dec 22 11:18:43 Unraid kernel: ret_from_fork+0x35/0x40 Dec 22 11:18:43 Unraid kernel: Modules linked in: tun veth xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs nfsd lockd grace sunrpc md_mod ipmi_devintf mlx4_en mlx4_core igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd ipmi_ssif mpt3sas glue_helper i2c_i801 i2c_core intel_cstate intel_uncore ahci intel_rapl_perf libahci raid_class scsi_transport_sas pcc_cpufreq wmi ipmi_si acpi_pad button [last unloaded: mlx4_core] Dec 22 11:18:43 Unraid kernel: ---[ end trace 0235f654514174a1 ]--- Dec 22 11:18:43 Unraid kernel: RIP: 0010:ata_qc_issue+0xfc/0x195 Dec 22 11:18:43 Unraid kernel: Code: 8b b5 a0 00 00 00 48 8b b8 40 35 00 00 48 85 ff 74 0c 48 8b 87 10 02 00 00 48 85 c0 75 07 48 8b 05 64 f3 9b 00 83 f9 02 76 02 <0f> 0b 45 31 c0 48 8b 40 30 e8 b1 5e 5a 00 85 c0 79 02 0f 0b 74 6b Dec 22 11:18:43 Unraid kernel: RSP: 0018:ffffc90007023cf0 EFLAGS: 00010002 Dec 22 11:18:43 Unraid kernel: RAX: ffffffff81c678c0 RBX: ffff888842460000 RCX: 0000000000000003 Dec 22 11:18:43 Unraid kernel: RDX: 0000000000000001 RSI: ffff8888398a3bd0 RDI: ffff88905b33d0a8 Dec 22 11:18:43 Unraid kernel: RBP: ffff8888424606d0 R08: 0000000000000087 R09: 0000000000000000 Dec 22 11:18:43 Unraid kernel: R10: 0000000000000200 R11: fefefefefefefeff R12: ffff888842462040 Dec 22 11:18:43 Unraid kernel: R13: ffff8888594cd800 R14: ffff888842460000 R15: ffff8888398a3900 Dec 22 11:18:43 Unraid kernel: FS: 0000000000000000(0000) GS:ffff88905f800000(0000) knlGS:0000000000000000 Dec 22 11:18:43 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 22 11:18:43 Unraid kernel: CR2: 0000145d01098ff8 CR3: 0000000001e0a002 CR4: 00000000001606e0 Dec 22 11:18:52 Unraid kernel: ------------[ cut here ]------------ Dec 22 11:18:52 Unraid kernel: NETDEV WATCHDOG: eth0 (igb): transmit queue 2 timed out Dec 22 11:18:52 Unraid kernel: WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:465 dev_watchdog+0x161/0x1bb Dec 22 11:18:52 Unraid kernel: Modules linked in: tun veth xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs nfsd lockd grace sunrpc md_mod ipmi_devintf mlx4_en mlx4_core igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd ipmi_ssif mpt3sas glue_helper i2c_i801 i2c_core intel_cstate intel_uncore ahci intel_rapl_perf libahci raid_class scsi_transport_sas pcc_cpufreq wmi ipmi_si acpi_pad button [last unloaded: mlx4_core] Dec 22 11:18:52 Unraid kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: G D 4.19.88-Unraid #1 Dec 22 11:18:52 Unraid kernel: Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.3 08/23/2018 Dec 22 11:18:52 Unraid kernel: RIP: 0010:dev_watchdog+0x161/0x1bb Dec 22 11:18:52 Unraid kernel: Code: 71 94 00 00 75 39 48 89 ef c6 05 38 71 94 00 01 e8 85 a8 fd ff 44 89 e9 48 89 ee 48 c7 c7 49 1f da 81 48 89 c2 e8 8f 1b af ff <0f> 0b eb 11 41 ff c5 48 81 c2 40 01 00 00 41 39 cd 75 95 eb 13 48 Dec 22 11:18:52 Unraid kernel: RSP: 0018:ffff88885f743ea0 EFLAGS: 00010286 Dec 22 11:18:52 Unraid kernel: RAX: 0000000000000000 RBX: ffff88883099c438 RCX: 0000000000000007 Dec 22 11:18:52 Unraid kernel: RDX: 0000000000000c05 RSI: 0000000000000002 RDI: ffff88885f7564f0 Dec 22 11:18:52 Unraid kernel: RBP: ffff88883099c000 R08: 000000000000000f R09: ffff8880000bb300 Dec 22 11:18:52 Unraid kernel: R10: 0000000000000000 R11: 0000000000000058 R12: ffff88883099c41c Dec 22 11:18:52 Unraid kernel: R13: 0000000000000002 R14: ffff88883a77c940 R15: 0000000000000005 Dec 22 11:18:52 Unraid kernel: FS: 0000000000000000(0000) GS:ffff88885f740000(0000) knlGS:0000000000000000 Dec 22 11:18:52 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Anyone have any ideas what's going on? unraid-diagnostics-20191222-1308.zip
  12. Anyone else getting this error in bottom left corner next to the "Array Started" text? Warning: unlink(/tmp/unassigned.devices/credentials): No such file or directory in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1088 I'm getting it on two seperate Unraid servers. Started a couple days ago with an update and still happening. unraid2-diagnostics-20191203-1235.zip
  13. Has anyone got Organizr Server Authentication working with NPM? https://docs.organizr.app/books/setup-features/page/serverauth Also, I'm coming from using the Letsencrypt container. For my wordpress site, I just dropped it's folder into the "www" directory to get it going. How does that work with NPM? Thanks.
  14. Yeah, that and mounting/umounting the shares seems to fix them temporarily. Just annoying when trying to process 20k files with a container and it keeps dying half way through due to shares disappearing. Which means that all the progress is loss. I'm most likely going to take both servers back to 6.6.7. Having this issue with 6.8, and have terrible performance and iowait in 6.7.