-
Posts
95 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by d2dyno
-
-
I'm getting the same error over and over on the new debian apt mirror docker:
---Something went horribly wrong, can't find the mirror directory!---
Even though from within the container, I can see/ls the directory:
/debian-mirror/data/mirror
-
7 minutes ago, xthursdayx said:
Late post, but hopefully one of you all might see this. I was just wondering how you're handling making your .zshrc and any plugins persistent? Thanks!
I used the User Scripts plugin to run this script on first start of array :
#!/bin/bash # umask setup umask 077 # Variable Setup CONFIG=/boot/config/ssh HOME_SSH=/root/.ssh ZSH="/root/.oh-my-zsh" mkdir -p $HOME_SSH cp $CONFIG/pre-set/* $HOME_SSH chmod 700 $HOME_SSH chmod 644 $HOME_SSH/id_rsa.pub chmod 600 $HOME_SSH/id_rsa chmod 600 $HOME_SSH/authorized_keys ### Install zsh shits HOME="/root" sh -c "$(wget https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh -O -)" umask g-w,o-w chsh -s $(which zsh) env zsh -l newplugins="git tmux zsh-autosuggestions" sed -i "s/(git)/($newplugins)/" /root/.zshrc sed -i "s#\(ZSH_THEME *= *\).*#\1agnoster#" /root/.zshrc echo "cd /mnt/user/" >> /root/.zshrc git clone https://github.com/zsh-users/zsh-autosuggestions $ZSH/custom/plugins/zsh-autosuggestions chmod 700 /root/.oh-my-zsh/custom/plugins/zsh-autosuggestions ### # Copy terminal (zsh) history cp /boot/config/.zsh_history /root
Combined with this array stop script to copy ZSH history and SSH keys:
#!/bin/bash # Copy terminal (zsh) history touch /boot/config/.zsh_history echo "$(cat /root/.zsh_history)" >> /boot/config/.zsh_history # Variable Setup CONFIG=/boot/config/ssh HOME_SSH=/root/.ssh # Copy any new keys on exit rsync -avhW $HOME_SSH/ $CONFIG/pre-set
As for .zshrc (or aliases), I use /boot/config/go to write to /etc/profile on startup (how I was taught here to do it):
# Re-make aliases on boot echo " #### Aliases copied from /boot/config/go #### alias size='du -c -h -d 1 | sort -h' export TERM=xterm-color #### End Aliases ####">>/etc/profile
These are just example aliases and settings, use your own (though I do love that size alias)
- 1
- 5
-
Initially had 0 problems with this plugin and Plex, but now the containers are super touchy, sometimes working with --runtime=nvidia and sometimes not. The error I often get is:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex2' --net='bridge' --cpuset-cpus='25,26,27,28,29,30,31,57,58,59,60,61,62,63' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'VERSION'='latest' -e 'PUID'='99' -e 'PGID'='100' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-1e9824c9-cf6f-9a6d-9b75-dccaa79ba9a1' -p '1901:1900/tcp' -p '32401:32400/tcp' -p '33400:33400/tcp' -v '/mnt/disks/union-thd-plex2/misc/':'/misc':'rw,slave' -v '/mnt/disks/union-thd-plex2/misc2/':'/misc2':'rw,slave' -v '/mnt/disks/union-thd-plex2/misc3/':'/misc3':'rw,slave' -v '/mnt/user/Photos/server2/':'/photos':'rw' -v '/mnt/cache/Transcode/plex2':'/transcode':'rw' -v '/mnt/disks/nvmepool/appdata/plex2':'/config':'rw,slave' --runtime=nvidia 'linuxserver/plex' 598820f4e09e0ac0f5bdb8234210fecdc67487b3d3a3392e094b2683cccd2bdc /usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "process_linux.go:432: running prestart hook 1 caused \"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: cuda error: initialization error\\n\""": unknown. The command failed.
EDIT: so when I run 'watch nvidia-smi' it comes up with my gpu, then later says no devices found.
-
6 minutes ago, CombatMedic said:
Bless you kind sir. I was pulling my hair out trying to find out what I had screwed up on a docker that had been working fine for months.
Same. This should be on the front page / on the github
-
6 hours ago, aptalca said:
Did you read my linked thread above?
Post a full log, post your docker run and check the openvpn log in the config folder
Yes I did. Using bridge as always, tried adding NET_ADMIN via extra arguments, did not change any behaviour.
/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='openvpn-as' --net='bridge' --cpuset-cpus='5,6,37,38' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'INTERFACE'='eth0' -e 'PGID'='100' -e 'PUID'='99' -p '943:943/tcp' -p '11194:11194/udp' -v '/mnt/disks/nvmepool/appdata/openvpn-as':'/config':'rw,slave' --cap-add=NET_ADMIN --label="traefik.protocol=https" --label="traefik.enable=true" --label="traefik.port=943" --label="traefik.frontend.rule=Host:ovpn.example.nl" --restart unless-stopped 'linuxserver/openvpn-as:latest'
-
19 hours ago, jjthacker said:
Has anybody figured out the SESSION ERROR problem? I am another of those affected by this.
I can log in the initial front end page, but only if I use my external domain name. It won't work if I refer to the site using the IP address. It also fails when I try to connect to the admin page, either using IP address or domain name.
I think that it is probably related to my LetsEncrypt proxy configuration, but I don't understand why it broke at the last update. It worked fine until then.
I looked at the link kindly provided by aptalca, but none of the suggested issues seem to belong to my configuration. I already had default and admin locations in my proxy configuration.
I'm getting this on a fresh install. Fresh because the update wiped out my config folder: https://github.com/linuxserver/docker-openvpn-as/issues/108
Getting this in container log
Unpacking openvpn-as (2.8.3-f28d2eae-Ubuntu18) ...
Setting up openvpn-as-bundled-clients (7) ...
Setting up openvpn-as (2.8.3-f28d2eae-Ubuntu18) ...
Automatic configuration failed, see /usr/local/openvpn_as/init.log
You can configure manually using the /usr/local/openvpn_as/bin/ovpn-init tool.
/var/lib/dpkg/info/openvpn-as.postinst: line 68: systemctl: command not found
Stopping openvpn-as now; will start again later after configuring
cat: /var/run/openvpnas.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] -
22 minutes ago, aptalca said:
See the post above yours
Not using jumbo frames is a workaround, not a fix. I use that MTU on purpose, and never had issues except with this plugin.
-
On 3/9/2020 at 2:52 PM, luigi408 said:
I am having an issue installing the Nvidia build. I installed the plugin correct and it was working fine. The issue arrives when I click on the plugin and then the pop up comes up saying: Updating available builds.
The plugin just gets stuck there and nothing happens. It happened to me last time but it went away after a certain amount of time. This time however, I left it for an hour and it still stuck in the Update available builds pop up.
Error in logs after running plugin:
Mar 9 13:02:33 homeserver root: plugin: running: anonymous
Mar 9 13:07:21 homeserver nginx: 2020/03/09 13:07:21 [error] 7664#7664: *3939 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.22, server: , request: "POST /plugins/Unraid-Nvidia/include/exec.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "5e3b627426cedd4703dc2e189d1934123d251c17.unraid.net", referrer: "https://5e3b627426cedd4703dc2e189d1934123d251c17.unraid.net/Settings/Unraid-Nvidia"
How do I fix this? Thank you.
Same exact issue with SFP+ aggregated (802.3ad) NiC, MTU 9000. Also using Unifi gear.
-
Updated my BIOS (On PRIME X399-A went from 0808 -> 1203) and the Quadro now displays. It's very possible the update simply reset settings that needed to be changed too. I kept the 'fake' DP connected just in case. Thanks for all the help!
-
31 minutes ago, CHBMB said:
2. A race condition where the plugin parses for cards at boot before the drivers have loaded.
Are you speaking of this?
On 2/9/2020 at 10:33 AM, CHBMB said:Try running this command and post the output.
nvidia-smi --query-gpu=gpu_name,gpu_bus_id,gpu_uuid --format=csv,noheader | sed -e s/00000000://g | sed 's/\,\ /\n/g'
If so, the output is:
nvidia-smi --query-gpu=gpu_name,gpu_bus_id,gpu_uuid --format=csv,noheader | sed -e s/00000000://g | sed 's/\,\ /\n/g' No devices were found
Quote1. Issue of DP not being connected
I bought these to see if that will resolve it: https://www.amazon.com/gp/product/B075873RJR
-
-
The nvidia-smi one? That says no devices found, same message as web GUI.There should be a command somewhere in this thread you could issue to check if the card is working. It was posted by chbmb a few pages back I think. You did download the nvidia build using the plugin? Or did you just install the plugin?
Yes, installed following instructions in the OP (install plugin, use plugin to install Nvidia unraid OS).
Sent from my HD1905 using Tapatalk
-
Just installed this 6.8.2 version, to complement my new P2000. However after installing this modded unraid version, powering off my system, installing the P2000, and powering the server back on, the Nvidia plugin shows "No devices were found". Checking lspci/System Devices, it shows the card is indeed installed:
IOMMU group 18:[10de:1c30] 0a:00.0 VGA compatible controller: NVIDIA Corporation GP106GL [Quadro P2000] (rev a1)
[10de:10f1] 0a:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
I read somewhere I need to connect something to the DisplayPort for the GPU to be recognized, but the server is just in a rack with no monitor so that's not ideal (except maybe a fake DisplayPort device). Anyone know the best course of action?
-
I had a similar issue, but with non hard-linked files. I think it had more to do with rsync itself. I ended up using rclone move to finish the task of removing orphaned/ already copied files from my cache drive (which was a remarkable 2TB).
-
I opted to remove the whole file, because just removing notifyCalc still left me with an error about 2019/05/20 16:38:26 Unable to start the app: configuration variable provided but not defined: notifyMove.
After removing the conf file, unbalance now starts.
-
4 hours ago, jbrodriguez said:
Upgraded to 6.7.0 and unbalance is running normally.
root@lucy:~# uname -a Linux lucy 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz GenuineIntel GNU/Linux root@lucy:~# ps aux | grep unbalance nobody 4808 0.0 0.3 107864 10324 ? Sl 10:06 0:00 /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 root 5199 0.0 0.0 3908 2228 pts/0 S+ 10:10 0:00 grep unbalance
So, for those having issues, try this on the command line
killall unbalance /usr/local/emhttp/plugins/unbalance/unbalance -port 6237
This is to check the output.
Post the result.
killall unbalance unbalance: no process found ✘ ⚡ root@TheiaHD /mnt/user /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 configuration variable provided but not defined: notifyCalc Usage of /usr/local/emhttp/plugins/unbalance/unbalance: -apiFolders="/var/local/emhttp": folders to look for api endpoints -checkForUpdate=1: checkForUpdate: 0 - dont' check; 1 (default) - check -config="/boot/config/plugins/unbalance/unbalance.conf": config location -dryRun=true: perform a dry-run rather than actual work -folders="": deprecated - do not use -logdir="/boot/logs": pathname where log file will be written to -notifyPlan=0: notify via email after plan operation has completed (unraid notifications must be set up first): 0 - No notifications; 1 - Simple notifications; 2 - Detailed notifications -notifyTransfer=0: notify via email after transfer operation has completed (unraid notifications must be set up first): 0 - No notifications; 1 - Simple notifications; 2 - Detailed notifications -port="6237": port to run the server -refreshRate=250: how often to refresh the ui while running a command (in milliseconds) -reservedAmount=512: Minimun Amount of space to reserve -reservedUnit="Mb": Reserved Amount unit: Mb, Gb or % -rsyncArgs="-X": custom rsync arguments -verbosity=0: include rsync output in log files: 0 (default) - include; 1 - do not include 2019/05/20 15:11:39 Unable to start the app: configuration variable provided but not defined: notifyCalc
-
On 5/18/2019 at 6:47 PM, manolodf said:
I start the Unbalance but it perpetually shows as "Stopped" even when I enable it and apply.
May 18 18:45:58 Tower ool www[31806]: /usr/local/emhttp/plugins/unbalance/scripts/start
May 18 18:45:58 Tower sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/usr/bin/bash -c /usr/local/emhttp/plugins/unbalance/unbalance -port 6237Same issue here on 6.7.0
-
I cannot add my server via the app for some reason. Tried http, https, and the port the controller plugin shows, with true same reason - app brings me back to an empty page. Also the blue button seems to be missing text. Video:
-
On 2/25/2019 at 10:17 AM, dmacias said:On 2/24/2019 at 6:35 AM, d2dyno said:Would it be possible to include vnstat 2.1? I would really like to upgrade, but can't find any slack packages for this version
I'll try and compile it when I get time.
Have you been able to compile this?
-
14 hours ago, gilahacker said:
Dunno if I'll actually see any difference myself (sightly faster downloads? smoother remote streams?) but I'm glad to see that Limetech included it just the same.
BBR is primarily meant to improve OUTGOING speeds, as it was designed initially for YouTube to cut down on bandwidth waste. My use case for BBR is a 40+ MB/s speed improvement in seeding on torrent clients from a gigabit connection. Multiple high bandwidth Plex streams and downloading from your server outside of your network would likely see a performance increase as well.
-
Would it be possible to include vnstat 2.1? I would really like to upgrade, but can't find any slack packages for this version 😞
-
Can mediainfo be updated to the latest version? Thanks!
-
1 minute ago, Stupifier said:
Apologies.....you referring to Oh-My-Zsh
Yep, though nerdpack is what I used to install zsh, as you said 😀 then oh my zsh must be installed on top of that.
-
3 hours ago, dmacias said:4 hours ago, d2dyno said:[mention=11874]dmacias[/mention] LFTP is throwing this error on my installation:
lftp: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
I don't think upgrading the package from the plugin will work since it's the same version. Turn on uninstall and deselect lftp. Click apply. Then check for updates and apply the new package
This must be what it was, thanks
[PLUG-IN] NerdTools
in Plugin Support
Posted
Looking for `iotop`, `lftp`, `libmediainfo`/`mediainfo` and `vnstat` to be added.