• Posts

  • Joined

  • Last visited

Everything posted by repomanz

  1. fixed this after more reading: change the container repo to this: ptrfrll/nv-docker-trex:cuda11
  2. @PTRFRLL Hi - thanks for the trex miner container. Running into an issue hoping forum can assist. When starting container I get this in the log: have the following 2 entries assigned in the container: nvidia-smi output:
  3. @dlandon Howdy. I'm running your ML build; has been solid but when rebooted it today it's failing to start up now (been running solid for months). logs: *** Running /etc/my_init.d/ Performing updates... Get:1 focal-security InRelease [114 kB] Hit:2 focal InRelease Hit:3 focal InRelease Get:4 focal-updates InRelease [114 kB] Hit:5 focal InRelease Get:6 focal-security/universe Sources [84.0 kB] Get:7 focal-security/universe amd64 Packages [785 kB] Get:8 focal InRelease [23.9 kB] Get:9 focal-backports InRelease [101 kB] Get:10 focal-updates/main Sources [528 kB] Get:11 focal/main amd64 Packages [151 kB] Get:12 focal-updates/multiverse Sources [21.6 kB] Get:13 focal-updates/universe Sources [226 kB] Get:14 focal-updates/universe amd64 Packages [1055 kB] Get:15 focal-updates/main amd64 Packages [1423 kB] Get:16 focal-updates/multiverse amd64 Packages [39.1 kB] Fetched 4665 kB in 2s (2752 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages will be upgraded: login passwd 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1019 kB of archives. After this operation, 1024 B of additional disk space will be used. Get:1 focal-updates/main amd64 login amd64 1:4.8.1-1ubuntu5.20.04.1 [220 kB] Get:2 focal-updates/main amd64 passwd amd64 1:4.8.1-1ubuntu5.20.04.1 [799 kB] Fetched 1019 kB in 1s (897 kB/s) Preparing to unpack .../login_1%3a4.8.1-1ubuntu5.20.04.1_amd64.deb ... Unpacking login (1:4.8.1-1ubuntu5.20.04.1) over (1:4.8.1-1ubuntu5.20.04) ... Preparing to unpack .../passwd_1%3a4.8.1-1ubuntu5.20.04.1_amd64.deb ... Unpacking passwd (1:4.8.1-1ubuntu5.20.04.1) over (1:4.8.1-1ubuntu5.20.04) ... Setting up passwd (1:4.8.1-1ubuntu5.20.04.1) ... Reading package lists... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/ using existing keys in "/config/keys" *** Running /etc/my_init.d/ Using existing conf folder Copying zm.conf to config folder mv: cannot stat '/root/zm.conf': No such file or directory File zmeventnotification.ini already moved File secrets.ini already moved File already moved File already moved Event notification server already moved Pushover api already moved Using existing ssmtp folder Using existing mysql database folder Copy /config/control/ scripts to /usr/share/perl5/ZoneMinder/Control/ Copy /config/conf/ scripts to /etc/zm/conf.d/ Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp Using existing data directory for cache no crontab for root File objectconfig.ini already moved File already moved File already moved File already moved File already moved File already moved File already moved File already moved Starting services... * Starting Apache httpd web server apache2 * * Starting MariaDB database server mysqld ...done. Aug 2 10:41:12 d1992da2ad0d /etc/mysql/debian-start[1011]: Upgrading MySQL tables if necessary. Aug 2 10:41:12 d1992da2ad0d /etc/mysql/debian-start[1017]: Looking for 'mysql' as: /usr/bin/mysql Aug 2 10:41:12 d1992da2ad0d /etc/mysql/debian-start[1017]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Aug 2 10:41:12 d1992da2ad0d /etc/mysql/debian-start[1017]: This installation of MySQL is already upgraded to 10.3.30-MariaDB, use --force if you still need to run mysql_upgrade Aug 2 10:41:12 d1992da2ad0d /etc/mysql/debian-start[1024]: Checking for insecure root accounts. Aug 2 10:41:12 d1992da2ad0d /etc/mysql/debian-start[1028]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Database already at version 1.36.5, update skipped. Freshening configuration in database Migratings passwords, if any... Loading config from DB 221 entries Saving config to DB 221 entries Starting ZoneMinder: Aug 2 10:41:12 d1992da2ad0d zmpkg[1070]: INF [Sanity checking States table...] DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/ZoneMinder/ line 627. DBD::mysql::st execute failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/bin/ line 325. Aug 2 10:41:12 d1992da2ad0d zmpkg[1070]: ERR [Can't execute log entry 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )': Lost connection to MySQL server during query] Aug 2 10:41:12 d1992da2ad0d zmpkg[1070]: FAT [Can't execute: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)] ZoneMinder failed to start *** /etc/my_init.d/ failed with status 255 *** Killing all processes...
  4. I can get you another copy of the TPS report. haha joking. DJoss - thanks for your support on this container.
  5. Agree - it's a great step in the right direction. For future updates I'm hoping to see some further hardening. Can someone explain the technical authentication details of how the remote access works? Is it my login, pass, 2fa token plus a unique generated ssh key? If those credentials fail what occurs? Block, Reject or hold the session open for a period of minutes?
  6. This is mostly likely because I was already authenticated within my browser sessions with unraid forum but I noticed when I logged in with the my servers plugin it did not prompt me for 2FA which I have enabled. I assume the plugin referenced my authentication session token here. Wonder if it would be better security when setting this up to prompt for 2FA.
  7. Thanks - that fixed it. Can the unraid team add this to the install wiki (unless this will be handled as part of plugin update later)?
  8. There's a few guides out there I can probably leverage around reverse proxy. Ultimately I want my unraid server itself to be behind the proxy while leveraging this new feature. Not too comfortable with having an internet exposed port with a direct shot to unraid os security wise. Is there a technical white paper / write up about this new plugin? Sounds like i need to do some tinkering. I really do like this new plugin.
  9. My unraid machine gets it's DNS from a VM running on unraid so dns is not up at boot. To counter that, I used the download button within your plugin so it was cached at boot. All working now though; next time I'll change DNS to resolve to as a safeguard.
  10. Hi @jonp I'm really like this plugin but before I dive into it would it work behind the one of the nginx proxy containers within different vlans (which includes custom docker networks)? I would like to like to leverage this new feature from the unraid team but put the following behind nginx proxy - unraid server (no vlan) - plexmedia server (container) (external vlan / custom docker network) - homeassistant (VM) (external vlan) thanks!
  11. Hi @ich777 I ran into an issue this morning when upgrading to 6.9.1. I had your latest version of the plugin installed and I had manually downloaded the latest gpu driver before upgrading to 6.9.1. After upgrade to 6.9.1 none of my nvidia gpu enabled containers would start (bad parameter execution). I then went to the plugins page and noticed your plugin had disappeared. I went back into community apps to get it and when I downloaded it the first time the UI told me it was skipping the install because the plugin was already installed however it wasn't listed in the unraid UI (in plugins or settings). I went back to the community plugin page and tried again and this time it allowed me to install. At this point the GPU and GPUID was not recognized. So I disabled docker and renabled docker then went back to the nvidia plugin and the GPU / GPU ID was still not there. Gave the server another reboot and all is working now. My assumption is updates in 6.9.1 maybe related to docker updates was some how interfering with your plugin. Just wanted to report this back to you. Thanks again for your work on this plugin. Much appreciated.
  12. Hi @ich777 just confirming but the proper process with your plugin is to select the latest option?
  13. Hi @ich777 noticed that unraid 6.9.1 is available today (I'm on 6.9). Do I need to consider the plugin version before upgrading to 6.9.1? I'm on the latest as of this writing, checked to see if there was a plugin update and there isn't one so assume I'm on the latest.
  14. Thanks for the clarification @JorgeB
  15. Hi @JorgeB Can you help me clarify this statement. I was on 6.8.3 (brtfs - single ssd cache drive) and have upgraded to 6.9 now that the release is in production. The bit I don't understand is the need to reformat. How will reformatting the cache/ssd help here in context of 6.9 and regarding excessive writes?
  16. Thanks - I'll check out the reddit thread. I suspect may also have something to do with custom docker networks. My plex being accessible remote is on br3 (different subnet)
  17. I had to complete uninstall and remove app data but the plexpms container is now transcoding. Silver lining here, my plex folder size was pretty bloated so this reset helps
  18. Hello @binhex. I'm jumping over to your container but having issues. I don't see my server even if I hit the local IP:port my server doesn't show up. I have a lifetime plex pass account and even logging in to or local I can't see the server. New install; at odds why I can't even see the server local. Ideas?
  19. nvidia-smi (i have plex attempting to transcode but not showing) nvidia plugin
  20. hi @ich777 first thanks for your work around this plugin. Much appreciated. I just migrated to 6.9, have installed the new plugin and my containers I used gpu for are already set with the appropriate parameters / variables and settings within plex. I see the driver version and gpu id within your plugin. I've also rebooted the server. I do see other processes (handbrake for example) being shown. However when using plex, I don't see any attached processes with my video card now. I am running plex's container (plexinc/pms-docker) Does this container have issues being seen with the plugin and gpu? Everything was working pre migration with the deprecated plugin.
  21. Does anyone have a script for this container that does the following? After downloading and the unpack is completed, move related folder and files to a new location? The problem that I have is I have transcoding jobs watching the sab completed folder but they start running as sabnzb is unpacking so the transcoder jobs start processing on incomplete folders and files ( _unpackxyz folder name for example).
  22. I solved my problem. I copied locally the plugin "Tdarr_Plugin_MC93_Migz1FFMPEG" and tuned it a bit. I ended up modifying this line in the plugin to tailor to my needs. response.preset += `,-map 0 -c:v hevc_nvenc -rc:v vbr_hq -cq:v 28 -tune flim -preset slow ${bitrateSettings} ` key change/add: -cq:v 28 -tune flim -preset slow
  23. Hello everyone. New to tdarr and my goal is to replace handbrake since it seems like nvenc h.265 10bit is in an unknown status on when it will come to handbrake. This software is really awesome but I'm having trouble bringing my file size down with decent quality comparable to handbrake. I'm using the migz nvenc gpu plugin. comparison 30gb file, handbrake (gpu h.265) with english only audio and subs get's down to little less than 4gb. With tdarr that number is currently 15gb. Can anyone point me to plugins that can do gpu based nvenc h.265 10bit with decent quality and a much better file size? Or is it possible to convert my current handbrake configuration into the correct ffmpeg cli string (with 10bit) or does anyone have their own non-community plugins that would so something similar? @HaveAGitGat any tips here?
  24. @Djoss Got this in email today. Unsure if that requires container changes but thought I'd pass along. "Beginning March 4, 2021, CrashPlan will require two-factor authentication when logging in to your CrashPlan for Small Business account from the administration console. Use of two-factor authentication helps prevent unauthorized account access."