weirdcrap
-
Posts
461 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by weirdcrap
-
-
35 minutes ago, Squid said:
Wrong csrf_token means what trurl stated: Another browser on another device was active before the reboot of the server and is still pointed at the server's (or plugin's) web page
Missing csrf_token means that the plugin is not up to date (or the author has not updated it to handle the security requirements)
You were right, I did leave one browser window open I totally forgot about. That's what I get for checking on the server from so many other servers on the network.
Now that I fixed that CSRF error my ghost device is gone as well. I guess it had something to do with the browser session I had left open on the other machine.
-
25 minutes ago, trurl said:
Unassigned Devices is part of unRAID even if you don't have the plugin installed. The plugin just adds functionality to let you do things with the unassigned devices.Your screenshot is showing the unassigned device but it doesn't have any of the added functionality.
And your diagnostics does show the disk, but not any SMART for it which is not unusual for USB. Is it actually unplugged? Or did you just not expect to see it in the Unassigned Devices tab (which is normal)?
As for wrong csrf, do you have any other computer or an android or iphone app accessing your server? Are all your plugins up-to-date?
@trurlThat disk has been unplugged for hours and is sitting on my desk at home so it should not still be showing in UD, that's why I was concerned about it. Thanks for the info about it being a part of UnRAID, I was not aware it was so heavily integrated.
I did see some bits about having the controlr app installed with the associated plugin which I did have but have already uninstalled and it did not fix the issue.
@SquidCome to think of it I may have a browser open on a machine in the server room I was using on Friday, that is probably the cause of the wrong csrf_token error.
-
On 2/4/2017 at 3:07 PM, dgaschk said:
This is repeating over and over again on two servers that where updated to 6.3.0 last night. All plugins are current.
Feb 4 01:38:18 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:19 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:25 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:29 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:31 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:37 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:40 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:43 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:49 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:51 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
I am still having this issue, though mine all show wrong csrf_token instead of missing. Hopefully someone can help me out.
Running UnRAID 6.3.2 and as far as I know I was running the latest UD and preclear, I had CA AutoUpdate setup for the plugins to run weekly.
I came in to the office last night to hook up a drive and setup a file copy to run over night. I hooked up a usb 3.0 external wd passport drive to the front port of the server and noticed a kernel panic flash across the screen and then the power light went out and the server rebooted. On booting and loading the UnRAID OS with the drive still plugged in UnRAID crashed again.
I shut the server off, unplugged it, let it sit for five minutes, plugged it back in and it booted fine.
When I looked at the log it was getting hit every five seconds with wrong csrf_token errors from both the preclear plugin and UD. I found some other threads were people saw clearing their browsers and uninstalling re-installing fixed it so I tried that, but the issue persisted. I use Chrome mainly if that makes a difference.
I decided to uninstall it for the time being so the logs wouldn't fill up because I didn't want to work on it in the middle of the night. I unplugged the drive, cleared the /boot/ directory of any files folders I found relating to the plugins and rebooted the server.
Even with the plugins uninstalled I am still seeing the UD section on my Main tab with a phantom disk for the USB hard drive listed as /dev/sda (see attached snippet). I checked and fdisk -l does not show a /dev/sda at all so the underlying Linux kernel does not see the drive still.
Diagnostics are attached, you can see in the log that as soon as I attempt to re-install UD my log immediately starts getting wrong csrf_token errors again.
I would prefer to be able to keep UD and preclear so I would appreciate some help in fixing whatever happened.
-
Can the PMS/docker be downgraded to a public version?
https://github.com/linuxserver/docker-plex#setting-up-the-application
The "fun" part is finding an exact version number that doesn't end up a 404 in the Git pull. I have one saved I used to fall back due to Roku issues.
x.x.x.xxxx-xxxxxxx
Its about 3 or 4 weeks back as of today? Hope that helps.
ps. no this is NOT a dvr version number.
*mod - don't post plexpass version numbers
I am also having Roku issues, Plex has become unwatchable for me. Does anyone have a solution? Is it just to roll back to this magical x.x.x.xxxx-xxxxxxx version number where Roku playback wasn't completely f*cked?
-
Hi all,
i think i am having dramas getting this going, should the webui take hours to become available?
The download and building of database *seems* fine.
but starting of the server / webui i don't seem to be having any luck with
Mine was working fine for about a week. Now the logs look the same as they did when it was working but the page just says waiting infinitely and it doesn't respond to queries from applications. Going to Try deleting everything and starting again like CHBMB suggested and see if it sorts itself out. Otherwise I might just download the VM image from their site and use that to run it from my Windows box where it will hopefully be less temperamental.
-
Hello,
I want to be able to use one of the trackers for couchpotato,
i have successfully searched and find results on cardigann but i can't get it to work in couchpotato.
How am i suppose to conffigure it in couchpotato - > settings -> sercher ?
using TorrentPotato?
Thank you
No idea. Better off asking in couchpotato forum or torrentpotato if you get no replies from anyone else here.
Under the TorrentPotato section you put in the TorrentPotato link for that tracker from Cardigann into the host field. You then put the Cardigann API key into the Pass key field. Leave the username field blank (I haven't seen anything require this field).
Make sure the box at the begginning of the field next to host is checked as this shows that you want to enable that searcher. That should be all you need.
-
One more request for the Public version of Jackett.
Please, and thank you!
What's the Public version?
A fork of Jackett that includes support for public trackers not just private ones.
-
Follow up question on this, what kind of update interval does this use to pull changes from MusicBrainz? Is it weekly? As changes are made? Do I need to restart the container to pull new data?
-
Could you possibly answer my question at the very end of my monster post, did the place on the flash drive logs are saved get moved? my /boot/logs folder doesn't appear to have been touched since mid September...
Recent unRAID releases have begun saving syslog.txt to the root of the flash. Powerdown saved timestamped logs and diagnostics to the logs folder, so perhaps you uninstalled powerdown in September? I believe they are talking about adding configurable saving of logs and diagnostics, and I believe the Tips and Tweaks plugin has features to do it also.
That sounds about right, I uninstalled it whenever he announced that he was discounting support for the powerdown plugin.
So UnRAID only saves the most recent shutdown log now?
EDIT: I installed dlandon's tips and tweaks plugin to regain the syslog archiving as I find it indispensable to be able to look back at past logs for troubleshooting intermittent issues.
Sent from my Nexus 6P using Tapatalk
-
These are always a little tough to deal with, because there's little I can say to help. At least in your case, it didn't affect anything if you were not using any USB ports. After it was disabled, any USB ports using usb1 would not work.
The only thing I can say is - keep updating. It's a bug, somewhere, but difficult to know where. Because it's an IRQ, it's low level, almost certainly below all unRAID modules. So it could be a bug in a driver, or the kernel, or the motherboard BIOS, or the firmware on a device.
What is concerning though is that IRQ assignments like most others are dynamic, and can change between boots. So this time it appears to be assigned to certain USB ports you weren't using, but next time it could be assigned to something you *are* using. Long ago, I had it happen to the USB port my boot drive was plugged in, and to my network card, and to some of my SATA ports! That means I either lost the flash drive, or the network, or some of my drives, and sometimes 2 of those together!
If it happens again and something stops working, just reboot.
Thanks for the reply. So far after two reboots it has always been IRQ #16 that has problems and it seems to happen after I have tried to plugin a USB device and mount it with unassigned devices as far as I can tell. Neither time has it affected a port or set of ports that have something important plugged in like my APC or the boot flash.
Like I said I had issues with UAD yesterday with a device and didn't notice anything in the log about the IRQ until this morning. Then after the reboot I tried to plug in a completely different device and the same thing happened. I can't recall if both times it was usb1. I will try updating my test box to the latest RC even though it isn't having this issue and if everything seems stable I will upgrade NODE next.
Could you possibly answer my question at the very end of my monster post, did the place on the flash drive logs are saved get moved? my /boot/logs folder doesn't appear to have been touched since mid September...
-
I upgraded from 6.2.2 to 6.2.4 two-three days ago and I haven't really been watching the logs much. Since the upgrade to 6.2.4 I have noticed the following in my system log twice now, once this morning and once this afternoon (even after rebooting in between):
Nov 11 17:12:08 Node kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Nov 11 17:12:08 Node kernel: CPU: 0 PID: 11501 Comm: emhttp Not tainted 4.4.30-unRAID #2 Nov 11 17:12:08 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015 Nov 11 17:12:08 Node kernel: 0000000000000000 ffff88081f203e70 ffffffff8136f79f ffff8807e5674800 Nov 11 17:12:08 Node kernel: 0000000000000000 ffff88081f203e98 ffffffff8107f8ce ffff8807e5674800 Nov 11 17:12:08 Node kernel: 0000000000000000 0000000000000010 ffff88081f203ed0 ffffffff8107fb9b Nov 11 17:12:08 Node kernel: Call Trace: Nov 11 17:12:08 Node kernel: <IRQ> [<ffffffff8136f79f>] dump_stack+0x61/0x7e Nov 11 17:12:08 Node kernel: [<ffffffff8107f8ce>] __report_bad_irq+0x2b/0xb4 Nov 11 17:12:08 Node kernel: [<ffffffff8107fb9b>] note_interrupt+0x1a0/0x22e Nov 11 17:12:08 Node kernel: [<ffffffff8107d8d1>] handle_irq_event_percpu+0xe2/0xf0 Nov 11 17:12:08 Node kernel: [<ffffffff8107d915>] handle_irq_event+0x36/0x54 Nov 11 17:12:08 Node kernel: [<ffffffff810803c5>] handle_fasteoi_irq+0x8c/0xf4 Nov 11 17:12:08 Node kernel: [<ffffffff8100e0e8>] handle_irq+0x17/0x1b Nov 11 17:12:08 Node kernel: [<ffffffff8100db3e>] do_IRQ+0x46/0xc2 Nov 11 17:12:08 Node kernel: [<ffffffff8162a6c2>] common_interrupt+0x82/0x82 Nov 11 17:12:08 Node kernel: <EOI> Nov 11 17:12:08 Node kernel: handlers: Nov 11 17:12:08 Node kernel: [<ffffffff814b1e61>] usb_hcd_irq Nov 11 17:12:08 Node kernel: Disabling IRQ #16
Here is my lsdev output (I haven't restarted UnRAID again yet tonight, bunch of people streaming):
Device DMA IRQ I/O Ports ------------------------------------------------ 0000:00:02.0 f000-f03f 0000:00:1f.2 27 f060-f07f f080-f083 f090-f097 f0a0-f0a3 f0b0-f0b7 0000:00:1f.3 f040-f05f 0000:02:00.0 e000-e0ff 0000:03:00.0 29 d000-d01f d020-d023 d030-d037 d040-d043 d050-d057 0000:04:00.0 30 c000-c01f c020-c023 c030-c037 c040-c043 c050-c057 7-edge 7 ACPI 1800-1803 1804-1805 1808-180b 1810-1815 1820-182f 1850-1850 acpi 9 ahci c000-c01f c020-c023 c030-c037 c040-c043 c050-c057 d000-d01f d020-d023 d030-d037 d040-d043 d050-d057 f060-f07f f080-f083 f090-f097 f0a0-f0a3 f0b0-f0b7 cascade 4 dma 0080-008f dma1 0000-001f dma2 00c0-00df dmar0 24 dmar1 25 ehci_hcd:usb1 16 ehci_hcd:usb2 23 eth0 28 fpu 00f0-00ff i801_smbus 18 f040-f05f i8042 1 12 it87 0a35-0a36 0a35-0a36 keyboard 0060-0060 0064-0064 parport0 5 0378-037a PCI 0000-0cf7 0cf8-0cff 0d00-ffff c000-cfff d000-dfff e000-efff pic1 0020-0021 pic2 00a0-00a1 pnp 04d0-04d1 0680-069f 0a00-0a0f 0a20-0a2f 0a30-0a3f 164e-164f 1854-1857 1c00-1cfe 1d00-1dfe 1e00-1efe 1f00-1ffe ffff-ffff ffff-ffff ffff-ffff PNP0C04:00 00f0-00f0 r8169 e000-e0ff rtc0 8 0070-0077 serial 03f8-03ff timer 0 timer0 0040-0043 timer1 0050-0053 vga+ 03c0-03df xhci_hcd 26
and my proc/interrupts
CPU0 CPU1 CPU2 CPU3 0: 30 0 0 0 IR-IO-APIC 2-edge timer 1: 2 0 0 0 IR-IO-APIC 1-edge i8042 5: 0 0 0 0 IR-IO-APIC 5-edge parport0 7: 20 0 0 0 IR-IO-APIC 7-edge 8: 46 0 0 0 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 12: 4 0 0 0 IR-IO-APIC 12-edge i8042 16: 100001 0 0 0 IR-IO-APIC 16-fasteoi ehci_hcd:usb1 18: 0 0 0 0 IR-IO-APIC 18-fasteoi i801_smbus 23: 29 0 0 0 IR-IO-APIC 23-fasteoi ehci_hcd:usb2 24: 0 0 0 0 DMAR-MSI 0-edge dmar0 25: 0 0 0 0 DMAR-MSI 1-edge dmar1 26: 1098951 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd 27: 1357019 0 0 0 IR-PCI-MSI 512000-edge 0000:00:1f.2 28: 29824263 0 0 0 IR-PCI-MSI 1048576-edge eth0 29: 1010454 0 0 0 IR-PCI-MSI 1572864-edge 0000:03:00.0 30: 20852 0 0 0 IR-PCI-MSI 2097152-edge 0000:04:00.0 NMI: 0 0 0 0 Non-maskable interrupts LOC: 14841433 13022098 13103008 12792463 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 Performance monitoring interrupts IWI: 2 1 2 1 IRQ work interrupts RTR: 0 0 0 0 APIC ICR read retries RES: 3403886 3696337 3346919 3162996 Rescheduling interrupts CAL: 16277 10323 9302 10017 Function call interrupts TLB: 422395 427894 417297 509851 TLB shootdowns TRM: 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 Machine check exceptions MCP: 105 105 105 105 Machine check polls ERR: 20 MIS: 0 PIN: 0 0 0 0 Posted-interrupt notification event PIW: 0 0 0 0 Posted-interrupt wakeup event
I don't have any USB devices plugged in to my UnRAID besides the data cable for my UPS which appears to still be working fine as it is reporting stats. I have attached my Diagnostics log. I checked and I have the latest BIOS version from Gigabyte for my motherboard.
I have another Unraid server with some different hardware and I haven't seen any of these USB issues with it and it's also on 6.2.4
Edit:
Furthermore, I hadn't plugged any USB devices into my server in a few months so I can't say when this started but yesterday and today on 6.2.4 when I try to mount a USB device with unassigned devices I see a number of USB reset errors after I try to mount them through unassigned devices. It shows the spinning mounting animation and then just disappear.
I can manually navigate to the /mnt/disks/ folder and see the device but when trying to copy or read files I receive an i/o error.
Here is an excerpt from my system log with the USB resets:
Nov 11 09:57:37 Node kernel: usb 3-2: new high-speed USB device number 4 using xhci_hcd Nov 11 09:57:38 Node kernel: usb-storage 3-2:1.0: USB Mass Storage device detected Nov 11 09:57:38 Node kernel: scsi host15: usb-storage 3-2:1.0 Nov 11 09:57:39 Node kernel: scsi 15:0:0:0: Direct-Access Wearable AirStash A02 PQ: 0 ANSI: 0 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: Attached scsi generic sg12 type 0 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Write Protect is off Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Mode Sense: 1b 00 00 00 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] No Caching mode page found Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Assuming drive cache: write through Nov 11 09:57:39 Node kernel: sdm: sdm1 Nov 11 09:57:39 Node kernel: sd 15:0:0:0: [sdm] Attached SCSI removable disk Nov 11 09:57:55 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:58:11 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:58:12 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log unassigned.devices.log Nov 11 09:58:29 Node mount.exfat: volume was not unmounted cleanly Nov 11 09:58:44 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:59:02 Node kernel: usb 3-2: reset high-speed USB device number 4 using xhci_hcd Nov 11 09:59:07 Node kernel: usb 3-2: device descriptor read/64, error -110 Nov 11 09:59:18 Node kernel: usb 3-2: USB disconnect, device number 4 Nov 11 09:59:18 Node kernel: sd 15:0:0:0: [sdm] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Nov 11 09:59:18 Node kernel: sd 15:0:0:0: [sdm] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 11 10:02:04 Node sshd[21977]: Accepted publickey for chris from 162.218.150.130 port 58951 ssh2: RSA SHA256:SYxfyeDR9+KFcVaAl11Xt+D5um7ctM81aeKdqdGqv24 Nov 11 10:02:10 Node su[22036]: Successful su for root by chris Nov 11 10:02:10 Node su[22036]: + /dev/pts/2 chris:root Nov 11 10:03:31 Node mount.exfat: failed to read directory cluster 0x7 Nov 11 10:03:31 Node kernel: Buffer I/O error on dev sdm1, logical block 1320, async page read Nov 11 10:04:12 Node mount.exfat: failed to write super block Nov 11 10:05:14 Node kernel: usb 3-10: new high-speed USB device number 5 using xhci_hcd Nov 11 10:05:14 Node kernel: usb-storage 3-10:1.0: USB Mass Storage device detected Nov 11 10:05:14 Node kernel: scsi host16: usb-storage 3-10:1.0 Nov 11 10:05:15 Node kernel: scsi 16:0:0:0: Direct-Access Wearable AirStash A02 PQ: 0 ANSI: 0 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: Attached scsi generic sg12 type 0 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Write Protect is off Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Mode Sense: 1b 00 00 00 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] No Caching mode page found Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Assuming drive cache: write through Nov 11 10:05:15 Node kernel: sdm: sdm1 Nov 11 10:05:15 Node kernel: sd 16:0:0:0: [sdm] Attached SCSI removable disk Nov 11 10:05:31 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:05:47 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:10:41 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:10:57 Node kernel: usb 3-10: reset high-speed USB device number 5 using xhci_hcd Nov 11 10:14:26 Node kernel: usb 3-10: USB disconnect, device number 5 Nov 11 10:16:02 Node kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd Nov 11 10:16:02 Node kernel: usb-storage 4-1:1.0: USB Mass Storage device detected Nov 11 10:16:02 Node kernel: scsi host17: usb-storage 4-1:1.0 Nov 11 10:16:03 Node kernel: scsi 17:0:0:0: Direct-Access Monster MONSTER DIGITAL PMAP PQ: 0 ANSI: 6 Nov 11 10:16:03 Node kernel: sd 17:0:0:0: Attached scsi generic sg12 type 0 Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] 120999936 512-byte logical blocks: (62.0 GB/57.7 GiB) Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Write Protect is off Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Mode Sense: 23 00 00 00 Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] No Caching mode page found Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Assuming drive cache: write through Nov 11 10:16:05 Node kernel: sdm: sdm1 Nov 11 10:16:05 Node kernel: sd 17:0:0:0: [sdm] Attached SCSI removable disk Nov 11 10:18:13 Node kernel: usb 4-1: USB disconnect, device number 2 Nov 11 10:18:22 Node kernel: usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd Nov 11 10:18:22 Node kernel: usb-storage 4-2:1.0: USB Mass Storage device detected Nov 11 10:18:22 Node kernel: scsi host18: usb-storage 4-2:1.0 Nov 11 10:18:23 Node kernel: scsi 18:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: Attached scsi generic sg12 type 0 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB) Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Write Protect is off Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Mode Sense: 23 00 00 00 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Nov 11 10:18:23 Node kernel: sdm: sdm1 Nov 11 10:18:23 Node kernel: sd 18:0:0:0: [sdm] Attached SCSI removable disk Nov 11 10:18:37 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Nov 11 10:18:49 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log unassigned.devices.log Nov 11 10:18:55 Node emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
I tried the slots on the front of the case and the back of the motherboard and I tried multiple devices.
I hooked up an SSD in an orico USB 3 drive enclosure and with an NTFS file system, error. Hooked up a random flash drive formatted in exfat, error. However when I hooked up my monster digital USB 3.0 flash drive that I know i have hooked up to Unraid before I didn't get an error and everything worked fine (this was also exfat formatted).
I know the log shows that the drive I attached was not unmounted cleanly but this also happened with the Orico USB 3.0 enclosure with a freshly formatted SSD in it so I don't think the unclean removal is the cause.
On an unrelated note did LimeTech change where system logs are saved to on the flash with V6.x? I went to grab logs from the past few weeks and noticed that according to the log/folder time stamps a log hasn't been saved to my flash (/boot/logs) since September 18th and I know I have rebooted quite a few times since september.
EDIT2: I also noticed this at the very beginning of my syslog:
spurious 8259A interrupt: IRQ7
which appears to have been reported by other users in the 6.2.x announcement threads.
Sent with tapatalk
-
Just the data folder or both the config and data folders?
both
Sweet, finally started working this morning. Thanks!
-
Just the data folder or both the config and data folders?
-
I am having an issue with this docker. It appears that it is failing to initialize the database (see the line marked >>>> <<<<<):
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] postgresql-log-dir: applying... [fix-attrs.d] postgresql-log-dir: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 05-timezone: executing... Current default time zone: 'America/Chicago' Local time is now: Thu Nov 10 15:47:46 CST 2016. Universal Time is now: Thu Nov 10 21:47:46 UTC 2016. [cont-init.d] 05-timezone: exited 0. [cont-init.d] 10_add_user: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10_add_user: exited 0. [cont-init.d] 20-brainzcode: executing... [cont-init.d] 20-brainzcode: exited 0. [cont-init.d] 30-initialise-database: executing... >>>>>>>>>>>> [b][cont-init.d] 30-initialise-database: exited 9.[/b] <<<<<<<<<<<<<<<<< [cont-init.d] 40-config-redis: executing... [cont-init.d] 40-config-redis: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [372] 10 Nov 15:47:48.718 # Server started, Redis version 2.8.4 [372] 10 Nov 15:47:48.718 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
The log then just sits there and doesn't move. See attached for my mappings. I triple checked my code for metabrainz and it is correct as well.
This is what I see when I try to view the WebUI:
08006 DBI connect('dbname=musicbrainz_db','abc',...) failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?The db file is indeed missing and the folder/file permissions look correct so I'm not sure why it would not have been created:
drwxrwxrwx 1 nobody users 116 Nov 10 15:43 .
drwxrwxrwx 1 nobody users 138 Nov 10 15:12 ..
-rw-rw-rw- 1 chris users 1675 Aug 5 14:56 PolyphemusAutomationSetup
drwxrwxrwx 1 nobody users 0 Sep 13 17:03 calibre
drwxrwxrwx 1 nobody users 32 Nov 10 15:58 mbrainzData
drwxrwxrwx 1 nobody users 44 Nov 10 15:58 musicbrainz
drwxrwxrwx 1 nobody users 48 Sep 17 17:02 plex
root@VOID:/mnt/cache/appdata# cd mbrainzData/
root@VOID:/mnt/cache/appdata/mbrainzData# ls -al
total 0
drwxrwxrwx 1 nobody users 32 Nov 10 15:58 .
drwxrwxrwx 1 nobody users 116 Nov 10 15:43 ..
drwxr-xr-x 1 nobody users 0 Nov 10 15:58 dbase
drwxr-xr-x 1 nobody users 0 Nov 10 15:58 import
drwxr-xr-x 1 nobody users 0 Nov 10 15:58 redis
root@VOID:/mnt/cache/appdata/mbrainzData#
-
As a quick test, put the following in your unmount script so you can see if it is being executed when you don't expect it.
logger "My unmount script is running..."
Ok, so that will print that line to the logger daemon so we can see it in the syslog? I have added the line to the beginning of the unmount script.
I will move those system log errors to a separate support thread and see if anyone can shed some light on them. If it is indeed a heat issue I will have to talk to my boss and see if he will let me turn down the A/C in the server room or I will have to order an after market CPU cooler.
-
I noticed those in the system log this morning when I was trying to troubleshoot this. They python error took place right around the time I was upgrading from 6.19 to 6.2 and I haven't seen it pop up since (I upgraded 9/18 around 9-10AM)
I have never seen the CPU temp spike over 45C and utilization is generally pretty low (less than 10%) unless plex is transcoding heavily. What part of those messages makes you think the CPU is over heating?
Sep 19 22:30:42 Node kernel: ------------[ cut here ]------------ Sep 19 22:30:42 Node kernel: WARNING: CPU: 0 PID: 27309 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e() Sep 19 22:30:42 Node kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii Sep 19 22:30:42 Node kernel: CPU: 0 PID: 27309 Comm: Threadpool work Not tainted 4.4.19-unRAID #1 Sep 19 22:30:42 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015 Sep 19 22:30:42 Node kernel: 0000000000000000 ffff8803c77ebee0 ffffffff8136a68e 0000000000000000 Sep 19 22:30:42 Node kernel: 00000000000000ec ffff8803c77ebf18 ffffffff8104a39a ffffffff81055502 Sep 19 22:30:42 Node kernel: fffffffffffffdfe 0000000000014f98 000000000000000d 000000000000a0b7 Sep 19 22:30:42 Node kernel: Call Trace: Sep 19 22:30:42 Node kernel: [<ffffffff8136a68e>] dump_stack+0x61/0x7e Sep 19 22:30:42 Node kernel: [<ffffffff8104a39a>] warn_slowpath_common+0x8f/0xa8 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] ? SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff8104a457>] warn_slowpath_null+0x15/0x17 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff81620a2e>] entry_SYSCALL_64_fastpath+0x12/0x6d Sep 19 22:30:42 Node kernel: ---[ end trace 753ae045f3fb133e ]---
This: x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii
But I don't know that much about these faults. Reardless, I don't think is is good.
I agree I never like seeing those messages but so far I haven't been able to find any information on what exactly that kernel error means.
-
I noticed those in the system log this morning when I was trying to troubleshoot this. They python error took place right around the time I was upgrading from 6.19 to 6.2 and I haven't seen it pop up since (I upgraded 9/18 around 9-10AM)
I have never seen the CPU temp spike over 45C and utilization is generally pretty low (less than 10%) unless plex is transcoding heavily. What part of those messages makes you think the CPU is over heating?
EDIT: Well apparently when I setup the Dynamix CPU temp plugin I picked the wrong sensor, when plex is really hammering the CPU it gets up to around 58-60C but that is still well below the thermal throttling threshold for the processor.
The UnRAID case sits in an air conditioned server room so besides cranking up the fans manually on the fan controller my only other options to address a CPU temp issue would be to buy an aftermarket CPU cooler.
-
For the start script, that's where you would get it... In theory if there is nothing showing for the unmount one, then the script has never run since the last reboot, and therefore has never itself unmounted the shares
Diagnostics may also shed some light (and if you could point out a rough time the mount became unavailable it would be helpful)
The mounts became unavailable sometime in the last 24 hours, sorry I can't be more specific I haven't really checked on it much. The only reason I noticed is my couchpotato was pissed off because it couldn't find the remote share it uses. I have a diagnostic log attached to my OP in this thread.
-
I didn't think to check the script logs, where do I view them? I only see a log icon next to my mount script?
Can't remember off the top of my head if I put the time of execution in the logging for the start / stop scripts (not at home at the moment).Thanks, I would tend to agree with you if not for my previous experience with powerdown. Once I disabled the script that had the umount commands to remove the shares they would stay up and never drop until I manually removed them.
The weird behavior makes me think there has to be some kind of signal unRAID is issuing that is tricking these plugins into thinking that the array is being stopped or something like that (of course I am just guessing).
But if the scripts logs available through user.scripts shows only a single execution, then its not unRaid.
Nevermind, found it. I don't even see a log having been generated for the unmount script so I guess the plugin hasn't run the script at all.
Like I said before I am just going off what I have experienced previously with the PowerDown plugin and when I disabled the K00 script prior to the v2.23 release I no longer had an issue.
I have disabled the schedule for the unmount script in user.scripts for now and I will see if they stay mounted...
-
Thanks, I would tend to agree with you if not for my previous experience with powerdown. Once I disabled the script that had the umount commands to remove the shares they would stay up and never drop until I manually removed them.
The weird behavior makes me think there has to be some kind of signal unRAID is issuing that is tricking these plugins into thinking that the array is being stopped or something like that (of course I am just guessing).
-
Hi Squid, not sure if you can help me with an issue I am having that has come back up now that powerdown is deprecated for v6.2.
In powerdown I had K and S scripts that would mount and remove remote share mounts when the array was stopped and started. Prior to powerdown v2.23 I had issues where my mounts would mysteriously disappear that were solved by simply disabling the K script. The changes dlandon made in v2.23 of his excellent script fixed my issues and my shares stayed mounted without any problems. Now that I have moved to unRAID v6.2 and started using your user scripts plugin my issue has returned. I am randomly losing my remote share mounts after only a day or so of having them mounted. The scripts are set to run on array start and array stop so they shouldn't be executing for any other reason and I don't see any evidence of them running randomly in the system log. I have attached my diagnostics zip to this post.
Here is a copy/paste of my post from the powerdown thread that shows what my scripts contain and some other details:
Wondering if someone can help me with a behaviour I noticed after setting up a K and S script to mount remote SSHFS shares for my automation setup. I have attached my system log, let
Before finding out I could use the powerdown plugin to run script files when the array starts/stops I was manually mounting my remote SSHFS shares each time I started the machine. The SSHFS shares would stay up without issues for weeks until I manually removed them. Now that I have setup a K00 and S00 script I have begun noticing that I randomly seem to be losing some of my SSHFS shares. On Saturday I noticed my automation setup was no longer finding recent downloads and upon checking what was mounted all three of my SSHFS mounts were gone. Then again this afternoon (8/28) I noticed Sonarr wasn't pulling in my downloads and it had just been working about four or five hours ago so I checked mount and sure enough my remote SSHFS share for tv downloads was missing.
Now I have no definitive proof that this is being caused by the powerdown plugin, I only have circumstantial guess work based on never having this issue until I created a K00 and S00 script and added them to the powerdown plugin following your instructions. For more information on SSHFS commands I am using check out my post over here: https://lime-technology.com/forum/index.php?topic=50974.msg489503#msg489503
I looked through the system log for today and I didn't see the powerdown script initiating the scripts like you normally see, for example:
Aug 25 16:04:26 Node rc.unRAID[13532][13537]: Processing /etc/rc.d/rc.unRAID.d/ start scripts.
Aug 25 16:04:26 Node rc.unRAID[13532][13541]: Running: "/etc/rc.d/rc.unRAID.d/S00.sh"
The only odd thing I noticed in the logs from today was apcupsd restarting around 4AM:
Aug 28 04:40:01 Node apcupsd[11573]: apcupsd exiting, signal 15
Aug 28 04:40:01 Node apcupsd[11573]: apcupsd shutdown succeeded
Aug 28 04:40:04 Node apcupsd[3015]: apcupsd 3.14.13 (02 February 2015) slackware startup succeeded
but I was using Sonarr long after that and it was all working fine.
Here is my K00 script:
#! /bin/bash umount /mnt/cache/.watch/tv-remote umount /mnt/cache/.watch/movies umount /mnt/cache/.watch/music-remote
and my S00 script:
#! /bin/bash sshfs [email protected]:private/deluge/data/couchpotato/ /mnt/cache/.watch/movies/ -o StrictHostKeyChecking=no -o allow_other -o Ciphers=arcfour -o Compression=no -o IdentityFile=/mnt/cache/.watch/PolyphemusAutomationSetup sshfs [email protected]:private/deluge/data/sonarr/ /mnt/cache/.watch/tv-remote/ -o StrictHostKeyChecking=no -o allow_other -o Ciphers=arcfour -o Compression=no -o IdentityFile=/mnt/cache/.watch/PolyphemusAutomationSetup sshfs [email protected]:private/deluge/data/headphones/ /mnt/cache/.watch/music-remote/ -o StrictHostKeyChecking=no -o allow_other -o Ciphers=arcfour -o Compression=no -o IdentityFile=/mnt/cache/.watch/PolyphemusAutomationSetup
If anyone has any ideas on why this might have started all of a sudden I am all ears.
EDIT: Just lost another share about three minutes ago, going to test if my theory is correct by removing the K00 script and seeing if the shares then stay mounted. I renamed K00.sh to KXX.sh and ran the update script command so now to wait and see if my shares stay in place.
EDIT2: Alright six days since I removed the K00 script and not a single remote mount has been lost.
-
Is it possible to run mono with the debug switch in this container?
I am having an issue with sonarr and the devs on their forum say the stack trace logs are pretty much useless without mono in debug mode.
EDIT: In fact while I am here I may as well ask the community about my issue as well. I am having issues with certain shows/episodes/possibly NZBs being added to NZBGet from Sonarr while others work with no issue.
I have made no changes to either my Sonarr or NZBGet setup in weeks and this issue just started happening yesterday afternoon.I have verified that Sonarr can connect to NZBGet by using the "test" button in the download client page of the Sonarr settings. I restarted UnRAID as well on the off chance that something was hung up in the system.
Here is a pastebin of my sonarr log from yesterday: http://pastebin.com/xyJN8jnQ
and here is a link to my thread over on the sonarr forums if it helps at all: https://forums.sonarr.tv/t/request-failed-failed-to-add-nzb/11596
The error message that stands out to me and would explain why the NZB fails to add is: [v2.0.0.4230] System.IO.IOException:
"Error writing request ---> System.Net.Sockets.SocketException: The socket has been shut down"
But if the connection between Sonarr and NZBGet was closed then why do other shows and even other episodes from the same show work fine?
to modify the startup settings for sonarr , exec into the container
docker exec -it <container-name> bash
and modify the file
/etc/service/sonarr/run
Ok, I am completely new to messing around with mono and editing stuff in Docker containers so bear with me.
This is what is in the run file: XDG_CONFIG_HOME="/config/xdg" exec /sbin/setuser abc mono /opt/NzbDrone/NzbDrone.exe -nobrowser -data=/config
so would I just append the debug switch here?
XDG_CONFIG_HOME="/config/xdg" exec /sbin/setuser abc mono --debug /opt/NzbDrone/NzbDrone.exe -nobrowser -data=/config
Or just put it at the end of the line?
XDG_CONFIG_HOME="/config/xdg" exec /sbin/setuser abc mono /opt/NzbDrone/NzbDrone.exe -nobrowser -data=/config --debug
-
Is it possible to run mono with the debug switch in this container?
I am having an issue with sonarr and the devs on their forum say the stack trace logs are pretty much useless without mono in debug mode.
EDIT: In fact while I am here I may as well ask the community about my issue as well. I am having issues with certain shows/episodes/possibly NZBs being added to NZBGet from Sonarr while others work with no issue.
I have made no changes to either my Sonarr or NZBGet setup in weeks and this issue just started happening yesterday afternoon.I have verified that Sonarr can connect to NZBGet by using the "test" button in the download client page of the Sonarr settings. I restarted UnRAID as well on the off chance that something was hung up in the system.
Here is a pastebin of my sonarr log from yesterday: http://pastebin.com/xyJN8jnQ
and here is a link to my thread over on the sonarr forums if it helps at all: https://forums.sonarr.tv/t/request-failed-failed-to-add-nzb/11596
The error message that stands out to me and would explain why the NZB fails to add is: [v2.0.0.4230] System.IO.IOException:
"Error writing request ---> System.Net.Sockets.SocketException: The socket has been shut down"
But if the connection between Sonarr and NZBGet was closed then why do other shows and even other episodes from the same show work fine?
-
Back up and running for me! Thank you if anything was done behind the scenes!
Fixed for me as well, looks like the missing python package was added to resolve the issue.
Tower cases with 5.25" drive bays top to bottom...
in Hardware
Posted · Edited by weirdcrap
I actually have a 10 disk server built in an 804, it works great. I like that:
-I can store the SSDs up in the front panel of the case
-It has built in fan filters to help keep the insides dust free
-It supports large after market CPU coolers like the Cryorig H7
-as someone who's old server is built in a massive Antec 1200 v3 with 20 drives in it that thing is massive, heavy, and unwieldy to carry, even with two people. This thing spreads the weight out throughout the case and is nice and compact.
My one complaint is the second cage full of drives is right over the power supply and with a standard sized power supply I barely have enough clearance to get all the drives connected. I am in the market to find a "stout" power supply that will make it not quite so tight.