Jump to content

montery

Members
  • Content Count

    67
  • Joined

  • Last visited

Community Reputation

2 Neutral

About montery

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    Canada, Eh?

Recent Profile Visitors

478 profile views
  1. 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!
  2. 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.
  3. 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?
  4. Hey everyone... Ok, I'm really embarrassed to be asking this, but, is there a default Username/Password once you have the docker installed?
  5. 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?
  6. 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.
  7. 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?
  8. 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!
  9. 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.
  10. 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!
  11. 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.
  12. 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!
  13. Ah, well, maybe that's because in my go file has a line in there: # resize tmpfs mount -o remount,size=1024m /var/log That was put in there due to an earlier suggestion to increase it as I have been having this problem for awhile. Here's the output from df -h and df -h / root@Tower:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 1.0G 94M 931M 10% /var/log /dev/sda1 7.5G 179M 7.3G 3% /boot /dev/md1 2.8T 149G 2.6T 6% /mnt/disk1 /dev/md2 1.9T 99G 1.8T 6% /mnt/disk2 /dev/md3 1.9T 593G 1.3T 32% /mnt/disk3 /dev/md4 1.9T 225G 1.6T 13% /mnt/disk4 /dev/md5 1.9T 243G 1.6T 13% /mnt/disk5 /dev/md6 1.9T 1.5T 345G 82% /mnt/disk6 /dev/md7 1.9T 1.3T 593G 69% /mnt/disk7 /dev/md8 1.9T 1.6T 314G 84% /mnt/disk8 /dev/md9 1.9T 1.6T 315G 84% /mnt/disk9 /dev/md10 1.9T 1.5T 341G 82% /mnt/disk10 /dev/md11 1.9T 1.5T 328G 83% /mnt/disk11 /dev/md12 1.9T 1.8T 64G 97% /mnt/disk12 /dev/sdo1 224G 70G 154G 32% /mnt/cache shfs 23T 12T 11T 52% /mnt/user0 shfs 23T 12T 12T 52% /mnt/user /dev/loop0 10G 2.1G 6.3G 25% /var/lib/docker root@Tower:~# df -h / Filesystem Size Used Avail Use% Mounted on - 7.9G 1.9G 6.0G 24% / The latest diagnostics dump is located here: https://drive.google.com/file/d/0B_6rmB4u7fHESGY4T2Y4N1RYMVk/view?usp=sharing I notice that my syslog file is growing hugely, and I'm uncertain as to why. Would certainly contribute to a lack of space! But certainly the /var is something that I need to correct. How do I get Docker to use /var on the cache drive? Thanks!
  14. Hi all! So, for the last little while now, Unraid 6.1.x has been crashing on me unexpectedly. Since upgrading to 6.1.6, at least the GUI crashes (partially) and I can access the terminal prompt, but the server goes off-line. I'm not sure what's causing this, but here's the syslog (attached) and a screen shot of the gui when it's dead, as well as a screen shot of the terminal when I've issued the powerdown script. Any idea which "device" that Powerdown complains about? Also, in the syslog, it complains that the mover has no space... I'll have to look at that drive to see if there is no space there. Thanks in advance! syslog.zip