Bigdady92
-
Posts
230 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Bigdady92
-
-
I have 2 10GBT cards installed.
All are loading the ixgbe driver on 6.3.5, will start my testing as I'm able to assign IP's and so far we are golden.
-
Is there anyway to get multiple network interfaces to appear in the stats page? I only see a single interface and want to have all 4 that I currently use displayed.
Sorry for not searching this thread it's 75 pages long
-
7 hours ago, smaka510 said:
seems to work fine with the HP/MELLANOX cards. I transfer files like a beast now. I'm looking at a managed switch as we speak!
Mellanox is still the 10GB with SFP+/GBICs not Ethernet in the RJ45 sense.
I have 3 10GBT cards coming and a netgear 10GBT switch, will set it up and see how the magic works with 6.3.5.
-
also this massively:
Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO ] 21:35:33 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 21:35:33 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 21:35:33 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO ] 21:35:34 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 21:35:34 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 21:35:34 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO ] 21:35:38 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 21:35:38 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 21:35:38 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO ] 21:35:38 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 21:35:38 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO ] 21:35:38 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO ] 21:35:43 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO ] 21:35:43 client:121 Connected to daemon at 127.0.0.1:58846.. -
I've been getting this error constantly and my deluge container is crashing repeatedly. I get errors all the time with connecting and torrent downloads. Any ideas?
kernel: deluged[20403]: segfault at 2b29722f5000 ip 00002b2979713ba7 sp 00002b29722f4118 error 6 in libtorrent-rasterbar.so.8.0.0[2b29795bb000+46f000]
-
Worked like a champ on Windows 10. Created USB drives with this utility all with the latest bleeding edge stuff.
-
How stable is 6.4 RC? I have a 10GBT switch and interested in these cards.
-
Usually Going to network settings, and making sure the default gateway points to your router and setting static DNS addresses of 8.8.8.8 and 8.8.4.4 will fix you upI think of it as an error because at that point plugins and Dockers won't install. No update checks will work etc. It's not a check on github per se but a check against internet access as a whole
Sent from my LG-D852 using Tapatalk
I've got this exact same problem. What would cause this error to appear? This error message is causing all my docker and plugin updates to fail yet I can get to github.com without a problem on my PC.
I set google's DNS to be my 2nd/3rd DNS left my router as 1st when I thought that was the problem.
I'll revise the order and see if that helps. I'll be mega irritated if it's that simple.
-
I think of it as an error because at that point plugins and Dockers won't install. No update checks will work etc. It's not a check on github per se but a check against internet access as a whole
Sent from my LG-D852 using Tapatalk
I've got this exact same problem. What would cause this error to appear? This error message is causing all my docker and plugin updates to fail yet I can get to github.com without a problem on my PC.
-
I love your plugins. UnRAID is not the same without them
Currently getting this error on the Fan Plugin:
Warning: file_get_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 38Warning: file_put_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 40Warning: file_put_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 48
Looks like the reference to your fan controller has changed, maybe you updated unRAID?
Easiest would be to select your appropriate PWM controller (may need to test which one works) and do a new detection of the PWM fan.
updated to 6.3.0. Updated all my plugins. I am hit 'detect' and I see all 10 different pwm modules. I've tried all of them and they still error out.
Do I need to blow away any of the files and reload them?
-
I love your plugins. UnRAID is not the same without them
Currently getting this error on the Fan Plugin:
Warning: file_get_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 38Warning: file_put_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 40Warning: file_put_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 48
Looks like the reference to your fan controller has changed, maybe you updated unRAID?
Easiest would be to select your appropriate PWM controller (may need to test which one works) and do a new detection of the PWM fan.
I havent updated unraid to 6.3 yet but i am today. I moved the boot drive to a new server with vastly different specs so that may be it. I thought unraid would clear everything out on a new config install.
-
I love your plugins. UnRAID is not the same without them
Currently getting this error on the Fan Plugin:
Warning: file_get_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 38Warning: file_put_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 40Warning: file_put_contents(/sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002f/pwm1_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 48
-
Is there a reason why:
mozilla-firefox
is in this repo? Is LT providing us with a GUI now? Is this a package dependency?
-
Steps to update to 1.0
1. Reboot Docker Image
2. Login to Plex
3. Confirm 1.0
Well that was easy...
The default installed docker will read .9.16.3 (or something), once you reboot your docker image you'll see you are updated to 1.0.
-
-
getting a weird error when I first updated the plugin:
dmacias' plugin Repository https://github.com/dmacias72/unRAID-plugins/tree/master/plugins
-
awesome utility. Any news on the updates for this image as i'm seeing complaints from the UI for an update.
-
Because by default it's 80 and just because you want it on 8080 doesn't mean everyone will. So we leave the decision on where to map the host port to the end user. And we never change the default port for the application. It's just kind of the docker way....
Is there any way you can put a comment field in that the user MUST setup a redirect port to something else? I'm looking out for other users who may run into a problem in the future.
Most people hit the button to install and then next to complete the steps and completely miss the ports, leads to a post on the forums, and more work for you.
Twas an idea.
-
Fired up this thing for the first time. Works but I have a question: Why not remap the port docker 80 to another port to not interfere with unraid? I remapped the port to 8080 on mine as I did not want to interefer with unraids built in websever.
-
Does this docker sort, tag, and identify music files in it's database? Is this a web front end for Picard by MusicBrainz?
I'm looking for something to sort through all my mp3s and retag them and was hoping this works for what I want to do.
-
I believe you. Im very puzzled why my image isnt working. I finally see the updates that are occuring in the image:
We are now refreshing packages from apt repositorys, this *may* take a while
(Reading database ... 15447 files and directories currently installed.)
Preparing to unpack .../openjdk-7-jre-headless_7u91-2.6.3-0ubuntu0.14.04.1_amd64.deb ...
Unpacking openjdk-7-jre-headless:amd64 (7u91-2.6.3-0ubuntu0.14.04.1) over (7u85-2.6.1-5ubuntu0.14.04.1) ...
Setting up openjdk-7-jre-headless:amd64 (7u91-2.6.3-0ubuntu0.14.04.1) ...
Installing new version of config file /etc/java-7-openjdk/security/java.security ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
Nov 25 17:58:34 29e2b2ba748c syslog-ng[192]: syslog-ng starting up; version='3.5.3'
UPDATE 2:
After all the packages are updated, THEN you restart the docker image, Then wait and THEN the unifi controller will become accessible.
update 3:
Most Bizzare. I got to the initial accepting of the SSL cert but then the web page hung. I know I'm not cpu/memory/disk/io bound as everything is well below limits.
-
I only changed the Host, not the container as I knew that would muck stuff up. I use Unifi all the time at work so I knew moving 8443 over on the container would be a big no-no.
That being said I said F*** it and purged the container again and reinstalled
root@:/mnt/user/appdata# netstat -apn | grep docker
tcp 0 0 0.0.0.0:8843 0.0.0.0:* LISTEN 11880/docker-proxy
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 11913/docker-proxy
tcp 0 0 0.0.0.0:8880 0.0.0.0:* LISTEN 11867/docker-proxy
tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 11902/docker-proxy
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 11891/docker-proxy
unix 2 [ ACC ] STREAM LISTENING 24042 16421/docker /var/run/docker.sock
unix 2 [ ] STREAM CONNECTED 10708153 16421/docker /var/run/docker.sock
root@:/mnt/user/appdata#
Same error message as above. I've stopped and started the container. Permissions are set for nonbody:users all the way down the path.
Logs:
-----------------------------------
_ _ _
| |___| (_) ___
| / __| | |/ _ \
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|
Brought to you by linuxserver.io
-----------------------------------
GID/UID
-----------------------------------
User uid: 99
User gid: 100
-----------------------------------
We are now refreshing packages from apt repositorys, this *may* take a while
Nov 25 14:49:27 29e2b2ba748c syslog-ng[95]: s
-
I'm running into a similar problem with the docker image not starting the webui.
I remapped the port from 8443 (standard unifi) to 8444 to prevent any additional problems with other applications. The standard ports of:
8080,8081,8843,8880 do not conflict with any of my other applications.
root@:/mnt/user/appdata# netstat -apn | grep 8444
tcp 0 0 0.0.0.0:8444 0.0.0.0:* LISTEN 27453/docker-proxy
root@:/mnt/user/appdata#
I did a netstat and saw that the port 8444 was listening but I'm not seeing anything besides an error page when i hit the main web page console.
This webpage is not available
ERR_CONNECTION_REFUSED
I've deleted both the image and the docker and still having the same problem.
Any ideas?
-
Using unraid as a Hyper-V storage container over ISCSI instead of using NFS/SMB is something I am interested in. Right now I have to invest in using Microsoft's or a crappy NAS solution which doesn't give me the flexibility and cost savings that an ISCSI solution does.
-
1
-
Dynamix - V6 Plugins
in Plugin Support
Posted
Thanks John_M learned something new every day. I'll wait for the update then.