montery

Members
  • Posts

    79
  • Joined

  • Last visited

Everything posted by montery

  1. Thanks guys. Got my plugins all back and operational again. I deleted and recreated my docker.img file, and my dockers are back as well. Unraid was saying my SSD CRC count was going up. Not sure why, so I did a balance and will keep an eye on future crc errors. I think my server is not feeling well! In the end, Unraid did it's job just fine -- it kept my data safe, and kept running during the UPS event. The plugins and dockers... well, they didn't fare as well, but these are community applications so I guess I can expect this. Thanks for you help, and I'll mark this as resolved.
  2. Ah ha! I one by one renamed the following plugins back to .plg, and after rebooting I noticed they were no longer to be found: -rw------- 1 root root 3.1K Jul 12 00:00 /boot/config/plugins/ca.backup2.plg -rw------- 1 root root 6.1K Jul 27 00:00 /boot/config/plugins/ca.update.applications.plg -rw------- 1 root root 66K Aug 16 15:43 /boot/config/plugins/community.applications.plg Is this as simple as re-downloading these plugins? Or is there more I should be looking into? Also, I for some reason have lost the ability to view dockers running in the Docker Container panel on the dashboard. When I view them under Docker, they are there, and operational. Has anyone heard of this happening before?
  3. In order to troubleshoot, should I do a bulk move of all the files in the plugins directory to another directory, and move them back one at a time? I understand that I'd have to reboot after each move to see what breaks. Thanks,
  4. Hi Trurl! Here's what I got... root@Tower:~# ls -lah /boot/config/plugins/*.plg -rw------- 1 root root 8.4K Jan 3 2020 /boot/config/plugins/NerdPack.plg -rw------- 1 root root 5.1K Apr 13 00:00 /boot/config/plugins/advCPaMV.plg -rw------- 1 root root 3.1K Jul 12 00:00 /boot/config/plugins/ca.backup2.plg -rw------- 1 root root 3.5K May 11 08:24 /boot/config/plugins/ca.mover.tuning.plg -rw------- 1 root root 3.9K Jan 28 2020 /boot/config/plugins/ca.turbo.plg -rw------- 1 root root 6.1K Jul 27 00:00 /boot/config/plugins/ca.update.applications.plg -rw------- 1 root root 66K Aug 16 15:43 /boot/config/plugins/community.applications.plg -rw------- 1 root root 3.0K Nov 11 2019 /boot/config/plugins/customtab.plg -rw------- 1 root root 21K Mar 21 16:05 /boot/config/plugins/disklocation-master.plg -rw------- 1 root root 3.6K Jun 20 00:00 /boot/config/plugins/dynamix.active.streams.plg -rw------- 1 root root 6.1K Aug 7 00:00 /boot/config/plugins/dynamix.cache.dirs.plg -rw------- 1 root root 3.0K Jun 24 00:00 /boot/config/plugins/dynamix.local.master.plg -rw------- 1 root root 2.7K Jun 25 00:00 /boot/config/plugins/dynamix.ssd.trim.plg -rw------- 1 root root 4.2K Aug 8 17:04 /boot/config/plugins/dynamix.wireguard.plg -rw------- 1 root root 6.0K Jul 1 00:00 /boot/config/plugins/enhanced.log.plg -rw------- 1 root root 4.7K Aug 15 23:54 /boot/config/plugins/file.activity.plg -rw------- 1 root root 16K Aug 6 00:00 /boot/config/plugins/fix.common.problems.plg -rw------- 1 root root 4.1K Jul 1 00:00 /boot/config/plugins/open.files.plg -rw------- 1 root root 25K May 11 00:00 /boot/config/plugins/preclear.disk.plg -rw------- 1 root root 2.8K Dec 7 2019 /boot/config/plugins/statistics.sender.plg -rw------- 1 root root 7.7K Aug 6 00:00 /boot/config/plugins/tips.and.tweaks.plg -rw------- 1 root root 44K Jul 30 00:00 /boot/config/plugins/unassigned.devices.plg -rw------- 1 root root 3.4K Oct 28 2019 /boot/config/plugins/unbalance.plg -rw------- 1 root root 1.9K Jun 4 14:17 /boot/config/plugins/unlimited-width.plg
  5. Hi guys, If anyone can give me some pointers on what to do next, I would be very appreciative! I replaced my UPSs batteries by hot-swapping them. No big deal, Unraid and the server just kept on going thanks to my Supermicro's redundant power supplies. Anyhow, I noticed that a couple of my dockers were missing their thumbnail icons, and after poking around saw that they were all using wrong IPs (with the bridging dockers set to use 0.0.0.0). Failing to resolve the problem within my limited skill-set, I rebooted -- only to discover that I could not get past the Starting Samba kernel message. Odd, this! So I rebooted into Safe mode, and have provided my diagnostics file. Any advise on how to get back to normal operations? Thank you so much! tower-diagnostics-20200818-1436.zip
  6. Hi team! I've been a long time Headless Kodi+Mysql guy, but it seems the Headless Kodi hack effort has died off. So, I'm looking at Emby and Jellyfin, but Jellyfin feels a little raw at the moment (have to build my own code? Yah, I'm just a lazy end-user...) With Emby, I seem to be in the minority use case - I don't plan on doing any transcoding. So, I'm not sure if I can use Emby just for raw passthrough of all my media? I have one (maybe two) Shield devices on which I watch my media, so I just really want a centralized library that can be updated automatically when Sonarr and Radarr pull something new down. What's the scoop my friends? Thanks!
  7. Just figured out how to turn on signatures. :) Thanks for the feedback, guys! @meepCan I ask what issues you've had with Nvidia? I'm seeing more problems with AMD (reset bug being the big one). Since I don't want to powerdown my server very often, I'm kinda leaning towards Nvidia. Note, I'm not doing any transcoding, or anything like that, which is what seems to be causing the most problem. I like to keep it as simple as I can!
  8. Just following up on my MariaDB woes. It looks like the entire docker container died after logs filled it up (which, in turn appears to be caused after all my shares disappeared). So, following Squid's advice, I deleted my docker image, re-installed all my containers, and MariaDB is happy again. Hope this helps someone else in future!
  9. Hi there, I was getting the endless loop of 200507 18:44:16 mysqld_safe Logging to syslog. 200507 18:44:16 mysqld_safe Starting mysqld daemon with databases from /config/databases So I stopped the container, removed the appdata file(s) and removed (including image) the docker. Downloaded new docker, configured it, and went to check the logs before doing anything else. This is what I found: ErrorWarningSystemArrayLogin [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] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 40-initialise-db: executing... Setting Up Initial Databases Installing MariaDB/MySQL system tables in '/config/databases' ... 2020-05-09 15:52:48 0 [ERROR] InnoDB: Operating system error number 103 in a file operation. 2020-05-09 15:52:48 0 [ERROR] InnoDB: Error number 103 means 'Software caused connection abort' 2020-05-09 15:52:48 0 [ERROR] InnoDB: Cannot rename file './ib_logfile101' to './ib_logfile0' 2020-05-09 15:52:48 0 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2020-05-09 15:52:49 0 [ERROR] InnoDB: Operating system error number 107 in a file operation. 2020-05-09 15:52:49 0 [ERROR] InnoDB: Error number 107 means 'Transport endpoint is not connected' 2020-05-09 15:52:49 0 [ERROR] InnoDB: File (unknown): 'close' returned OS error 307. Cannot continue operation 200509 15:52:49 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.4.12-MariaDB-1:10.4.12+maria~bionic-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760255 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5608d960cc3e] /usr/sbin/mysqld(handle_fatal_signal+0x515)[0x5608d9080cf5] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x1492f4425890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x1492f2d59e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x1492f2d5b801] /usr/sbin/mysqld(+0xa890e7)[0x5608d92950e7] /usr/sbin/mysqld(+0xa8c125)[0x5608d9298125] /usr/sbin/mysqld(+0xc0b858)[0x5608d9417858] /usr/sbin/mysqld(+0xc0d9b6)[0x5608d94199b6] /usr/sbin/mysqld(+0xa72587)[0x5608d927e587] /usr/sbin/mysqld(+0xb26e9d)[0x5608d9332e9d] /usr/sbin/mysqld(+0xa1664d)[0x5608d922264d] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x62)[0x5608d9083d52] /usr/sbin/mysqld(+0x674c09)[0x5608d8e80c09] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x84a)[0x5608d8e81dea] /usr/sbin/mysqld(+0x59e3f9)[0x5608d8daa3f9] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x566)[0x5608d8db08d6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x1492f2d3cb97] /usr/sbin/mysqld(_start+0x2a)[0x5608d8da44ea] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /config/databases Resource Limits: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size unlimited unlimited bytes Max core file size 0 0 bytes Max resident set unlimited unlimited bytes Max processes 386184 386184 processes Max open files 40960 40960 files Max locked memory unlimited unlimited bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 386184 386184 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Core pattern: core Aborted Installation of system tables failed! Examine the logs in /config/databases for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/sbin/mysqld --skip-grant-tables --general-log & and use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /config/databases that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at http://mariadb.org/jira 2020-05-09 15:52:49 0 [Note] mysqld (mysqld 10.4.12-MariaDB-1:10.4.12+maria~bionic-log) starting as process 306 ... 2020-05-09 15:52:49 0 [Warning] Can't create test file /config/databases/3695b5df793a.lower-test mysqld: Can't change dir to '/config/databases/' (Errcode: 107 "Transport endpoint is not connected") 2020-05-09 15:52:49 0 [ERROR] Aborting Did I do the uninstall-re-install process incorrectly? Has anyone seen this before? Thanks in advance for your help!
  10. Thank you! Looks like it's a low level bug that won't be fixed. I guess this is one of those things where we will just have to accept it and reboot. Good bye, 45 days of up time!
  11. Hey there! I'm a very long time Unraid user, and I've been watching and reading about using Unraid as a "do it all" platform: Windows 10 Daily Driver Occasionally some gaming (Civ 6, Cities Skyline, etc) Media Server Media Leech (nzb, radarr, sonarr, etc etc) Unifi Controller for my Wifi Scan to unraid share ... you get the picture, Unraid is at the center of everything I do. I've been very content to have a laptop do my daily driving chores, and for Unraid do it's thing in a server rack. But, two things have changed: I've moved into a condo, and I'm going "oooh... aaahhh..." over the upcoming Microsoft Flight Simulator 2020 release. The FS2020 is making me want to upgrade my hardware so I can play it at ideal settings. That means a Radeon VII + Ryzen 7 Pro 2700X for an AMD solution, or a Intel i7-9800X + NVIDIA RTX 2080 for a Intel/Nvidia solution. I'm not married to AMD or Intel, or Nvidia. I'm also not made of gobs of money, so I'm kinda inclined towards AMD simply for bang : buck ratio. I'd also like to keep my daily-driver fussing around to a minimum. I like some fussing around, but lately I find I don't have as much time to dedicate to my hobby as I would like. <sigh> I also have a Supermicro 846 chassis, which I'd like to continue to use. So my replacement motherboard I'd like to have IPMI, but it's just a like. Since the server/workstation has a noise reducing server rack box that I stuff in right by my knees when I'm at the desk, I guess IPMI is not essential, but I sure do like not having to get down to the floor to see what's up with the server!! I like to experiment (that is, fart around) with other VMs, so it'd be cool if I could do a Macinabox, but it's not mandatory. So, apologies for the long wind-up, but here's my questions: 1) Would you recommend Unraid + Windows 10 VM as a daily driver? 2) Assuming yes, and wanting to have as much Gaming performance as I want for FS2020, and not so much fussing around, which Video card would you recommend? 3) Which Motherboard (32 gigs minimum) + processor would you recommend? I understand IOMMU (and SpaceInvader One really does a fantabulous job of explaining this subject!), so I'm cool with editing xml files and such, though I get slightly less comfortable messing about with extracting vbios. Though, a well written tutorial I can follow. (Ask my wife, I learn to follow instructions well!) I'm leaning towards a an Ryzen 9 3900, and a Radeon RX 5700XT... and a nice X570-A Pro by MSI or perhaps an Asus Pro WS x 570-ACE motherboard. But then I get "scared" by all the problems that people have with doing windows + unraid + gpu Passthroughs and the like. Does anyone have a daily driver that just works for them? So, I bare my anguish to the internet, and I look forward to the community helping me with making decisions on my next build. Thank you!
  12. Hi folks! My server seems to have said "shares? We don't want no steenking shares!" and took them away from me. Googling around I saw someone saying that it's probably caused by the mover log being turned on. I have since turned it off. I haven't rebooted my server, so I attach the diagnostics, and am wondering if a simple reboot will clear the problem, or do I need to do more? Thanks in advance! tower-diagnostics-20200508-1650.zip
  13. I've always liked the ability to add any sized drive to the array. What I would like to see is a mobile friendly version of the GUI! Love unraid, and have been using it since the early days. Continuously impressed at what I can do with it!
  14. Thanks... The issue was entirely my set up. The problem had to do with some oddities in the Cache drive with a cd: user: Transport endpoint is not connected error. I deleted the appdata\unifi-controller folder. A reboot later and a re-install of the docker, and I can assign my user name and password.
  15. Nope... reading the controller manual, it's supposed to ask me for a admin username and password... but it didn't. So I thought the docker had a default username/password for first time setup. Would it be the username/password of the AP's?
  16. Hey everyone... Ok, I'm really embarrassed to be asking this, but, is there a default Username/Password once you have the docker installed?
  17. Ok, this is probably a really stupid question, and I apologize in advance for it, but does this docker require the LetsEncrypt docker in addition, or does it include it?
  18. Nope, I ended up removing the app and upgraded to 6.4. Haven't had the opportunity yet to try again. I'm hoping a new guide will be written with 6.4 in mind.
  19. First, I would like to thank CHBMB for posting his guide, very well written and informative. My only problem seems to be the nextcloud container logs show this error: nginx: [emerg] open() "/config/nginx/proxy.conf" failed (2: No such file or directory) in /config/nginx/site-confs/nextcloud:31 Sure enough, I go into the appdata folder for nextcloud and the proxy.conf file is not there. (Instructions didn't say I should put it there....) My appdata config path for nextcloud points to /mnt/user/appdata/nextcloud I'm wondering if it should instead point to /mnt/user/appdata/letsencrypt? When I put a copy of the proxy.conf file from the letsencrypt container into the nextcloud container, I got nginx: [emerg] BIO_new_file("/config/keys/letsencrypt/fullchain.pem") failed (SSL: error:02FFF002:system library:func(4095):No such file or directory:fopen('/config/keys/letsencrypt/fullchain.pem', 'r') error:20FFF080:BIO routines:CRYPTO_internal:no such file) Should I do this? Or have I missed a step in my letsencrypt configuration?
  20. Ah, ok, actually my port is 3306, so I tried specifying that as well. I also dropped the user and created it manually: CREATE USER 'lychee'@'%' identified by 'pictures'; Grant all on *.* to 'lychee'; Flush privileges; /* Affected rows: 0 Found rows: 0 Warnings: 0 Duration for 3 queries: 0.062 sec. */ I then verified that lychee didn't have an expired password: select user, password_expired from mysql.user ..and I verified my host was set to '%' -- so it should accept a connection from anywhere. I log into Lychee using 192.168.1.200:3306, username/password, and I get the error message above. I check both Lychee and MariaDB logs - clean, even after a shutdown and restart of the services on both. I'm sure I'm doing something elementary that is wrong, but I can't tell what it might be. Thanks again in advance for the help, I do appreciate it. Update: I tried logging into the MariaDB through HeidiSQL using the username/password that I setup for Lychee, and I was able to login successfully through Heidi. I don't know what the issue is with Lychee, but I'm guessing there is something not quite right with Lychee!
  21. The actual error I'm getting is"Unable to connect to host because access was denied, double check host, user-name & password, and check that access from your location is permitted" I opted to let Lychee create the database.
  22. Hi, I have a mariadb in a docker that I use for Kodi already. I've added a user/pass for Lychee in the database. I seem stuck trying to get Lychee to connect to the database. I'm not sure what I'm missing in terms of configuration? I checked the Lychee log, and no issues are reporting in there. Any advice on next steps? Thanks!
  23. Could be a limit of the FTP site you are connecting to. I've seen peak downloads of 34+ mb/sec using this container, and that with 10 concurrent sessions (the other ones vary from 600kb/sec to 4 mb/sec) I don't think it's the container.
  24. Hm, looks like my log filled up due to Supermicro's IMPI fighting with Sensors module of the kernel: Jan 7 05:23:09 Tower kernel: w83795 0-002f: Failed to read from register 0x011, err -6 Jan 7 10:00:41 Tower kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt! Jan 7 10:00:41 Tower kernel: i801_smbus 0000:00:1f.3: Transaction timeout Jan 7 10:00:41 Tower kernel: i801_smbus 0000:00:1f.3: Failed terminating the transaction Jan 7 10:00:41 Tower kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 7 10:00:41 Tower kernel: w83795 0-002f: Failed to read from register 0x010, err -16 Jan 7 10:00:41 Tower kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! I googled around, and the W83795 is the chip my supermicro board uses, and feeds into libsensors. The filling up of the log with the "Failed to read from register xxxxx" error is, according to this a german site: ... because of the built- in attempts Supermicro IPMI simultaneously on the I2C ( SMBus ) access . Either disable the sensor module or IPMI . Haven't seen this before in the logs, so I'll remove these lines from my go script since I'm not using the sensors plugin anymore: # Added for Sensors: modprobe coretemp modprobe jc42 modprobe w83795 /usr/bin/sensors -s We'll see what happens after this!