aptalca

The powerdown plugin replaces the standard unRAID powerdown script. No matter how the system is shutdown, powerdown will always be run. Here is the sequence of operations with each different click of the reboot: - Click "Reboot". The emhttp sequence is run to stop the array and reboot. This is the same as pressing the stop button on the webgui, and then clicking reboot. - Click "Reboot" with the CTRL key pressed. Powerdown is executed to stop all running tasks, unmount the drives, and then reboot. This is the same as typing "reboot" at the console. Either sequence gets you the syslog saved. If the array has been stopped when powerdown is called, it will merely save the log and reboot the systen. The difference is that the emhttp initiated reboot can sometimes get hung waiting for a task to stop. This is the situation where you see the unmounting drives message on the screen constantly. Powerdown is a bit more forceful and will shut down the array even if a task is keeping it from doing that. When powerdown is used to shut down the array and unmount the drives, you will see in the log a long list of entries where it is performing the work. If it's only a few lines at the end, the array has already been stopped. The million dollar question is, does the built in apcupsd plugin initiate the emhttp method or powerdown in case of power loss? The gui restart is fine if it hangs, because if someone presses the button, that means someone is watching to make sure it really powers down. But when it's initiated by power loss, that means most likely nobody is watching and if it hangs, you get unclean shutdown. If powerdown is initiated and it is the one that is replaced by the script, no problem. Thanks

I dnt have any Rokus anymore. Why are Roku owners pissed? They just upgraded the player on Roku and smart tvs. Much more usable now. I concur, the new plex roku interface is awesome. In fact, I gotta give props to the plex team because they actually hired the guy who created rarflix (a fan favorite free 3rd party plex app on roku) and he is now developing the new roku interface

pfsense comes to mind

I do have a docker you can use: https://hub.docker.com/r/aptalca/docker-rdp-dev/~/dockerfile/ You can find it in the Community Applications under the name Dockergui-Dev It opens a terminal window, and from there you can install and run whatever you want (Firefox works, but chrome for some reason didn't work at first try) user is nobody and the password is PASSWD EDIT: Updated the docker to a more recent xrdp version and now chromium seems to work as well

Haha at first I thought you meant prison cell [emoji14] Sorry for the totally pointless off topic post

Half of CP's updates have done that to my wanted list. More often than not at the very least it always messes up my qualities list. Yup, database is gone, but at least preserved most of the settings. But like you said, I lost the qualities and the categories, lol At least I don't have to deal with reentering all the api keys (it's especially a pain on mobile)

CouchPotato got a major update today and it borked the docker. While it's running, it auto updates and seems to be fine. But when you restart, it gives errors and does not start. So, if you have a cp docker running, don't stop it until the issue is fixed I opened a ticket on github: https://github.com/needo37/couchpotato/issues/7 EDIT: Somehow my database is borked. If I delete the database, but leave the config.ini it works. But I lost my "Manage" tab contents as older downloads are no longer there (and no I do not trust CP with managing my existing movie library. Last thing I need is CP going through and renaming all the files or even worse, deleting some of them lol)

AmazonEcho Home Automation Bridge container has been updated. Maximum memory set for java so it no longer ties up unnecessary RAM (java by default ties up a certain amount of ram based on total available ram and it can end up hogging a large chunk on high memory environments; on my server it tied up about 1GB out of 8GB for no reason when the same app can easily run on 300MB on rpi) Also the new version allows for custom version installs. Just pass a new environment variable under advanced settings: VERSION=0.X.X If you update and it stops working for you, you can easily go back to the previous version.

2 options: 1) Clipboard works through the side menu you can open by ctrl-alt-shft. Whatever you paste into that box appears in the container clipboard. Whatever you copy inside the container, appears in that box 2) JDownloader2 has a great remote web interface you can set up in its settings. Then you go to my.jdownloader.org from any browser to access your jdownloader interface. No need to copy paste into the container gui

Since you mentioned running VMs, it possible that you might be running out of ram?

Sounds about right. Except, I would probably recommend using mc (it is a part of unraid now). It should be much less scary than rsync for newbies.

Actually, you can move the image file. I have moved it from the cache drive to an SSD outside of the array. All you have to do is, stop docker, move img file, enter the new img path in unraid gui, restart docker. UnRaid webgui is actually pretty smart in the way it treats the image file (props to whoever is responsible). If the image file exists in the location entered, it will use it. If not, it will create a new one. If you stop docker, change the image size to a larger number, and restart, unRaid will automatically resize the existing file and mount it (I assume it uses dd command to add extra bits). You won't have to recreate anything.

You can check your drive for errors. You can also recreate your docker.img. You can also do a memtest (an option during unraid boot) Something is messing up your docker installation, I don't know what. Please double check that your config folder is on the cache drive in a cache only share. Also make sure that you entered that location in the container settings as /mnt/cache/blahblah rather than /mnt/user/blahblah (I don't know why but many people reported problems with using the user share path) Many of us have been using these containers for a long time and they have been very stable.

I thought cache drive had to be BTRFS in order for Docker to work... can anyone please confirm. You are sttoring the Docker.img file on the cache drive right? That used to be the case in earlier v6 betas, where you needed to format the drive to btrfs to host docker images. But then they created the docker.img file. That image file itself is formatted as btrfs so you no longer need the whole cache drive to be btrfs. All docker images are now stored inside that btrfs formatted image file.

Updated openvpn and all I had to do was set the password for the user (it was reset to none) I read in the description that the admin password was different so that didn't throw me off. However, I can no longer use it with Win 10. (Probably due to the fact that Win 10 got an update last night). I can connect, but I don't get a working connection (no access to local machines or the internet). Android devices work just fine with both gateway redirection as well as local network access. Anybody else having issues with openvpn on the latest win 10 update? Thanks EDIT: Magically, 24 hours later it is working again. Win 10 is giving me a lot of wi-fi issues on two different machines. . . Win 8.1 didn't have any issues.

When you open the Apps tab, do you see the categories "Productivity", "Multimedia", etc.? If you do you can find contacts and calendar under "Productivity". When I first started it, those categories didn't show up right away, but they eventually did (I checked after 15 min or so).

Updated JDownloader2 and OpenRemote containers OpenRemote now runs as user nobody instead of root JDownloader2 is now using hurricanehernandez's xrdp v1.3 base. Clipboard should now work. In order to copy/paste to and from the container's gui window, use the menu through ctrl-alt-shft. Whatever you copy within the container should show up in the box in that side menu. Whatever you put into that box will be available in the container's clipboard. Pretty cool, really.

On my installation, calendar and contacts are showing up as approved, not experimental. I think I know what's going on. Your install still has your old calendar and contacts apps on your disk and they are incompatible with 8.1.1 and that's why they show up as experimental. If you manually delete those two folders and restart, it should show the latest market versions of them, which site up with the label "approved" and should work. That's another issue with the upgrade process. It doesn't delete old and deprecated apps and they prevent the new market versions from being displayed. If you exec into the container just delete their folders under /var/www/owncloud/apps/ EDIT: you should probably first try to remove them in the webgui. After you remove them it should start displaying their latest market versions EDIT2: I just enabled contacts in 8.1.1 (I had never used or enabled it before) from the app market and it works just fine. I think you have to delete your contacts folder and reinstall from the market

That's a security issue with any signed certificate. The private key is meant to be kept private. If it is compromised the system is no longer secure. The private key should only be kept on the webserver with the correct limited permissions. If you want to store a backup copy in case the server dies, you should keep an encrypted copy. The only difference between csr vs doing it all on a signing authority is that with csr, your private key is not exposed to anyone but you. But if you have the signing authority generate everything where you enter your details on their website, they generate the private key and let you download it. In other words, your private key is exposed to the signing authority. They don't however keep a copy (they say that if you lose your private key you're toast, so you cancel the certificate and generate a new one). If you don't trust them, then it would be an issue, but I think you have to trust them in the first place because they have the power to sign the certificates and verify. If they wanted to steal your stuff, they could do that in other ways like creating a man in the middle and verifying their fake certificates. They wouldn't need the private key. Anyway, I sent them the csr in my case but I probably would have trusted them to generate the private key for me as well since I trust them with the signing and everything else. And a side note, I think most signing authorities provide the csr option because a lot of hosting providers like to create the csr themselves before adding ssl to your account (ie hostgator shared).

If you don't feel comfortable with rsync, you can use mc in screen to copy it all

Is your local config folder in a cache-only share?

Your first log shows: using existing mysql database But your second shows: moving mysql to config folder Did you delete the mysql folder in your config folder in between? Somehow your install is screwed up. You should try reinstalling the container. To do that, you can click on the container's name in unraid webgui to edit, not change anything and hit save. It should reinstall with the same settings. Based on the line from the second log, you may have lost your mysql database, because it is only supposed to be copied on first install, if there is no existing mysql database in the config folder. You might have to set up your cameras again. Let me know how that goes.

Make sure your docker.img file is not full, and your cache drive (or wherever the configuration files are)

I set the network type to bridged, and I'm running version 8.1.1. Internet is working, despite the warning. I won't add memcache. I'll take a look on the others. I'll send a PR for the required changes to get rid of those errors, and to add memcache if you want to merge it.

It happened to me a couple of times that mysql failed to start for no apparent reason. A following stop/restart fixed it. So you can try that first. If that doesn't work, we'll try to figure out if the mysql database somehow got corrupted. You can enter the container's console with the following: docker exec -it Zoneminder bash You can try to restart mysql and see if it gives an error: service mysql restart and then you can do the following two commands to check mysql logs: TERM=xterm nano /var/log/mysql.log TERM=xterm nano /var/log/mysql.err That should tell you what's wrong