JaY_III

I have been following the RC, but am currently on 6.6.7 Is this: "webgui: Syslog: sort logs" what i was looking for? If so, I guess its time to move to the RC

My wife informed me my HTPC wasn't working last night. However it turns out that unRAID was offline. I attempted to look at the log file, however it doesn't write when the system goes down. I am currently hoping my toddler just pushed the power button and not some other issue is at play. However the true reason my server was off is unknown to me. What I would like to see is an option to write the system log to either the flash drive or a shared drive before a reboot/power off. Or if this is already a feature could someone please point me in the correct direction. Thank you

Coffee Lake just launched on the 5th, so I highly doubt anyone has a built a system for unRAID based on that platform. Its also going to be a while before the non Z based chipsets are out. Current wave of boards are targeted towards enthusiasts, gamers and overclockers mainly. If you are planning a new build, you should wait for a board designed for workstation or server use. Also the first little while, BIOS's tend to have minor issues that could really be problematic for server use. No way i would call day 1 launch BIOS stable for server use. Sorry I dont have a proper answer to your question, but if you were thinking of a new build I would wait a few weeks at the very least to see what errata pops up with that CPU and wait for the inevitable work around. IMHO, Coffee lake is a rushed to market product to stop the momentum Ryzen has. Not saying it will be a bad product, as early results look good. Just saying for server use, you don't want any surprises.

+1 for dark theme this overly white theme is burning my eyes

yeah, I saw that one also but for me I don't want to mess with Sonnar right now since it works prefect. Couch Potato just sucks for me and looking for an alternative. its a separate program, a fork, not a plugin with all the TV features stripped. I should be worth watching that project and see where it ends up

looks like this one is getting more traction https://www.reddit.com/r/usenet/comments/5krgvl/i_created_a_fork_of_sonarr_with_support_for/ https://github.com/galli-leo/Radarr

+1

update went smoothly as always.

if a user account has access to "/" restart the service. If restarting the service doesnt work, restarting the array will. I had the problem when i made an account for my sister, unRAID reboot was required.

What I do is make FTP groups via file structure. So my file structure isn't exactly how my guide has it. and example would be mkdir /tmp/FTP/ mkdir /tmp/FTP/Cessquill mount --bind /mnt/user/Media/Videos /tmp/FTP/Cessquill/Media/ mount --bind /mnt/user/Uploads /tmp/FTP/Cessquill/Uploads mkdir /tmp/FTP/JaY_III mount --bind /mnt/user/ #File Permissions <Directory /tmp/FTP/Cessquill/Media> <Limit WRITE> DenyAll </Limit> </Directory> Then i would jail you too ftpuser /tmp/FTP/Cessquill And jail myself to ftpuser /tmp/FTP/JaY_III I have full access to /mnt/user aka then entire array pretty much and you have read only to the media and upload permissions. Is this the best way to do it, probably not, but it works

Not complaining, or begging for an instant update. Just thought the changelog was relevant. As newer version without a changelog is just a larger number

Change log : http://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-5-2-7-is-released/ba-p/1680663

Spent an hour on it and couldn't figure out how to get the SSH cert to.work properly. So sorry, between my screening kid right now, SFTP being slower and I have OpenVPN already, not sure if I'll look at this in a timely manner

No he is asking how to enable SFTP not setup the FTP for use. If i have time ill tackle that this weekend and post some instructions.

Just got home from work, and wanted to try something simpler before I killed my docker.img and reinstalled all dockers. Clicked on the app remove also remove image yes delete it reinstalled in CA works perfect now. Hopefully they do edit the second post on the announcement and list the issues and simple fixes that we are having. thanks again for pointing me to that. I missed that in the FAQ when I had a quick look over it last night

http://lime-technology.com/forum/index.php?topic=40937.msg481138#msg481138 Even if its just the single container? All the others upgraded without issues

just upgraded to 6.2 and doing my docker updates However this container is the only one I cant update I get this error: "Error: layers from manifest don't match image configuration" restarted docker and i get the same thing

Happy to help. Just trying to give a little back as this plugin solved all my FTP needs when I am away from home. So Thank you

The documentation is pretty clear on how to setup file permissions. And as the user is already forced to edit all the config files, I don't think that is required to default to read only. Here is an example of how I like to setup the FTP. Step 1: Edit mountscript.sh # Mounts just media for read only # Directory Structure mkdir /tmp/FTP/ mkdir /tmp/FTP/Media mkdir /tmp/FTP/Media/Video mkdir /tmp/FTP/Media/Audio mkdir /tmp/FTP/Media/E-Book mount --bind /mnt/user/Media/Videos /tmp/FTP/Media/Video mount --bind /mnt/user/Media/Music /tmp/FTP/Media/Audio mount --bind /mnt/user/Media/e-book /tmp/FTP/Media/E-Book # Mounts for Apps/Tools/ISO ect # Apps and Tools are Read only # Uploads are Read/Write mkdir /tmp/FTP/Apps mkdir /tmp/FTP/Uploads mount --bind /mnt/user/Backup/apps /tmp/FTP/Apps mount --bind /mnt/user/Uploads /tmp/FTP/Uploads What I have done in Step 1 is create the file structure that will be presented to my FTP users. I am using the /tmp directory so i do not need to use the unmount script. If you do not create your site in the /tmp directory, you must unmount all your shares. I find this simpler as an improper unmount will hang the shutdown. Also note file permisions are not actually set yet. I will do that in step 2: edit proftpd.conf #File Permissions <Directory /tmp/FTP/Media> <Limit WRITE> DenyAll </Limit> </Directory> <Directory /tmp/FTP/Apps> <Limit WRITE> DenyAll </Limit> </Directory> Next you will want to Jail your FTP users into the /tmp/FTP/ directory you have created In unRAID under Users -> Add User Create your user and add this in the discription: ftpuser /tmp/FTP/ Now when the user logs in they will be presented with 3 directories that look like this: Apps (read only) Media (read only) Uploads (read / write) Final Step Login as the user you have created and ensure they have access to what you want to allow. If you find the JAIL is not working and they have access to / on your system, you will need to restart the daemon as I believe the jails are actually setup for the users when the deamon is first started and can not be changed while running. So new users will not be properly jailed.

Do you need to do something special when you shut down this docker? I needed to do a reboot and can no longer talk to my DB "Can't connect to MySQL server on '192.168.1.16' (10061)" I also lost contact with my DB about 3 months ago with the same issue i think. anytime I restart, no more connection with it The only thing i use it for is KODI I have 2 machines running openELEC 6.0.3 that access it. the error file will just grow with the same output more or less repeating itself any help or ideas for me? 8b80faf6a9ba.err.txt

Works perfect. Thank you, and love the change log

Plugin uninstalled System Rebooted Plugin Reinstalled Settings-> ProFTPd-> Status: STOPPED Configuration: Enable ProFTPd: Yes -> Apply Status: RUNNING with version: 1.3.6rc1 System Rebooted Status: RUNNING with version: 1.3.6rc1 restored my settings System Rebooted Settings-> ProFTPd-> Status: STOPPED mountscripts.sh or ProFTPd.conf must be the issue uninstall /reinstall restored only mountscript.sh reboot Status: RUNNING with version: 1.3.6rc1 restored ProFTPd.conf (with restored mountscript.sh) reboot Status: STOPPED Suspect issue with ProFTP.conf is preventing the FTP from auto starting reboot with only ProFTP.conf restored Status: STOPPED So it is 100% something to do with my ProFTP.conf file. If I make any changes to it I can not get the server to auto start proftpd.conf

Power Cycle like this: Main -> Dashboard-> Array Operation-> Check Stop (click stop) -> Reboot/Power Down After reboot Settings-> ProFTPd-> Status: STOPPED JaY_III@unRAID:~# /etc/rc.d/rc.ProFTPd start Renewing userjail... ...OK Starting ProFTPd... ...OK JaY_III@unRAID:~# Settings-> ProFTPd-> Status: RUNNING with version: 1.3.6rc1 Yes at one time I did set the service to disabled when I was testing VM's. I have since re-enabled the service. That was all done here: Settings-> ProFTPd-> Configuration-> Enable ProFTPd : Yes/No

Here it is unraid-diagnostics-20160703-1329.zip

I had to power cycle my box again today and the FTP did not come back up on its own. I Have always had "EnableProFTP:Yes" set