![](http://upload.forums.unraid.net/live/set_resources_33/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
kamhighway
Members-
Posts
294 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
kamhighway's Achievements
Contributor (5/14)
4
Reputation
-
[Support] Linuxserver.io - Jackett
kamhighway replied to linuxserver.io's topic in Docker Containers
Jackett started working again today. I did not do anything to fix it. -
[Support] Linuxserver.io - Jackett
kamhighway replied to linuxserver.io's topic in Docker Containers
Is anyone having trouble with Sonarr communicating with Jackett? I am running Unraid 6.7.0 with the latest linuxserver.io Sonarr and Jackett dockers which had been working flawlessly. This morning Sonarr reported that none of Jackett's indexers were working. I saw there was an update to Jackett and thought that might fix it. It did not. I noticed that the url Jackett gives for a torznab feed is quite different than what I had in Sonarr when I originally set up Jackett. I updated one of my Sonarr indexers with the new torznab feed but the indexer would not pass the test connection. The only other setting for the Sonarr indexer is API which I left at /api. Does anyone know if that has changed? Thanks in advance. -
Cache shows different files with SMB than AFP
kamhighway replied to kamhighway's topic in General Support
Thanks Squid. I did not where to look. Deleting the share on disk #1 did the trick. Appreciate your insight. -
Cache shows different files with SMB than AFP
kamhighway replied to kamhighway's topic in General Support
Diagnostics, yes, I should have thought of that. Thanks for taking an interest in my problem. media-diagnostics-20181130-1454.zip -
I'm on Unraid version 6.6.5. I regularly access the cache drive from a Mac (on Sierra) using SMB. Yesterday, I mounted the cache drive and saw that it only had 1 folder name "ffmeg" at the top level. When I mount the cache drive using AFP, I was relieved see all the files I expected. I can continue to connect with AFP instead of SMB, but I'm wondering what could be the underlying cause. All of the other shares show identical content whether mounted with SMB of AFP except the cache drive. Does anyone have any idea what could cause this?
-
DiskSpeed, hdd/ssd benchmarking (unRAID 6+), version 2.10.8
kamhighway replied to jbartlett's topic in Docker Containers
@jbartlett, Thank you for this tool. I very much appreciate what you are doing here. Update: Looks like this is the same error message Simon021 posted. I have downloaded the latest docker version and can't seem to get past the initial hardware scan. This is the error message I received: DiskSpeed - Disk Diagnostics & Reporting tool Version: Beta 3a Scanning Hardware 12:01:51 Spinning up hard drives 12:01:51 Scanning storage controllers 12:01:53 Found Controller SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (8 ports) 12:01:53 Found Controller C602 chipset 4-Port SATA Storage Control Unit (4 ports) 12:01:53 Found Controller C600/X79 series chipset 6-Port SATA AHCI Controller (6 ports) 12:01:53 Scanning controllers for hard drives Lucee 5.2.6.59 Error (expression) Message Element at position [9] does not exist in list Stacktrace The Error Occurred in /var/www/ScanControllers.cfm: line 646 644: <CFLOOP index="Key" list="#StructKeyList(HW)#"> 645: <CFLOOP index="PortNo" from="1" to="#ArrayLen(HW[Key].Ports)#"> 646: <CFIF HW[Key].Ports[PortNo].DevicePath NEQ ""> 647: <cfexecute name="/bin/ls" arguments="-l #HW[Key].Ports[PortNo].DevicePath#" timeout="300" variable="tmp" /> 648: <CFSET dir=ListToArray(tmp,Chr(10))> There was a stack trace after this section. I've attached a txt file with the full output. I'm concerned because the message seems to indicate that there is a disk in position 9 that does not exist. If that is the case, that may explain some problems I've been having. If you could tell me if this message means that my Unraid server thinks it has a HD that is not really there, it might be the key to figuring out what's going on with my server. Thank you! Kamhighway DiskSpeed.txt -
unRAID OS version 6.5.0 Stable Release - Update Notes
kamhighway replied to ljm42's topic in Announcements
@Swithblade: Thanks for your suggestion. I reverted back to 6.3.5 so I can't check the logs or settings in 6.5.0. However, when 6.5.0 was running I could access the shares and Sonarr, Plex, (and others) which were running as dockers were also accessible via http. I think that means the network was running ok. -
unRAID OS version 6.5.0 Stable Release - Update Notes
kamhighway replied to ljm42's topic in Announcements
Upgraded from 6.3.5 to 6.5.0, then reverted back to 6.3.5. 6.5.0 worked fine from the web-gui on the monitor at the server. However, when accessing the web-gui from any other machine I got a 500 Internal Server Error which I think this is an nginx error message. Working from the web-gui at the server, I was able to provision the certificate for https, but this did not fix the problem. I've tried booting into the web-gui in safe mode, but this also does not fix the problem. I've removed dynamix.plg as per the instructions in this post. Is there anything else I can check? -
@johnie.black Thanks for pointing me in the right direction. Deleting /boot/config/._Trial.key and Trial.key fixed the problem for me.
-
I set up a new system with UR 6.4.1 using a Trial Key. After about a week I purchased a basic license and it looked like it installed fine. However, I noticed the following errors in the system log. How can I get rid of these errors? It looks like UR is looking at the trial key during bootup. Thank you, Kamhighway Mar 18 09:10:35 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:35 popo root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Mar 18 09:10:36 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:37 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:38 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:39 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:40 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:41 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:42 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:43 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:44 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:45 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:46 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:47 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:48 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:49 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:50 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:51 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:52 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:53 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:54 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:55 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:56 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:57 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:58 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:10:59 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:00 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:01 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:02 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:03 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:04 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:05 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:06 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:07 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:08 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:09 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:10 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:11 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:12 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:13 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:14 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:15 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:16 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:17 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:18 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:19 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:20 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:21 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:22 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:23 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:24 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:25 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:26 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:27 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:28 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:29 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:30 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:31 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:32 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:33 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:34 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:35 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:36 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Mar 18 09:11:37 popo emhttpd: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Trial.key (-3)
-
Its working now. Thank you.
-
[Support] Linuxserver.io - Nextcloud
kamhighway replied to linuxserver.io's topic in Docker Containers
I tried updating this docker but got an error message. Anyone else getting the same error? Error: Error: image lsiodev/nextcloud:latest not found -
Thanks for taking a look. I appreciate it.
-
I am having trouble getting the plugin to remember changes made from the Wake On Lan tab. Here's what I do: 1. Click on "new" button 2. New line shows up with hostname "New", IP Address 192.168.X.XXX, Mac Address XX:XX:XX:XX:XX:XX. It is always the same IP Address and Mac Address. 3. I edit the hostname, IP Address, and Mac Address 4. Status changes to green 5. Click on "Done" whereupon I get sent back to Unraid's Setting tab 6. If I click on Wake On Lan in the Settings Tab, I go back to the Wake On Lan tab of this plugin. The Hostname, IP, and Mac address have all reverted back to what they were in step 2 I have examined wakeonlan.xml and find that the new host does not get saved to the file. If I edit the file to put the new host in manually, it does not show up as a host in the plugins Wake On Lan tab. I am on Unraid 6.3.5. Does this plugin require 6.4? Update: After about an hour, the edits I made to wakeonlan.xml were reflected in the plugin as I had hoped. There must be a cache somewhere that takes a while to update. I had rebooted Unraid hoping that would make the cache read the edited wakeonlan.xml, but that did not work. Waiting an hour did work.
-
Centralising unraid for xbmc/kodi and seedboxs
kamhighway replied to deviousx's topic in General Support
Pulsedmedia supports btsync (now called resilio sync). It works well with gfjardim's btsync docker.