smashingtool

Is this and the config from https://www.linuxserver.io/index.php/2016/07/28/installing-nextcloud-on-unraid/ not working for anyone else all of a sudden. A week or so ago it was working just fine, but now it is broken. I have updated and changed several things on my network and system since then (Router firmware, Unraid version, container updates, etc) and I am struggling to figure out what is breaking this for me. If i try server.com/nextcloud, it just doesn't load period. If I try https://192.168.1.130:444/, it loads, but without CSS, so nothing works and I can't log in. I know this container is under active development, so if that's what broke it, that's fine. But if something on my end with my config broke it, I'd like to try to solve the problem.

I had to forward 2 ports specified in the Syncthing documentation to get decent speeds.

That's disappointing. I've never had a problem with that, even with Syncthing. In fact it was my favorite feature of the lsio containers. Is there any way for me to force it to update or use a specific version? Edit: Of note is that only major version discrepancies will break syncing with clients.

Before the latest container update, I was on Syncthing v0.14.4. After the update, I now seem to be stuck at v0.14.3. Restarting, Starting/stopping, and force updating the container are not resolving it. https://github.com/syncthing/syncthing/releases

Hi there are 2 factors at play here. [*]netdata is in constant development and the docker dev is trying to keep up with the new releases. https://hub.docker.com/r/titpetric/netdata/builds/ [*]there is the bug between unRAID and the docker-hub that shows updates available when there is actually no change. I can't remember now what release fixes the bug. So apologies for the frequent updates, but after all, they are bringing us forward. I guess I'm just not used to docker updates being tied to the application updates themselves. Many apps have a built in updater or update notification, which doesn't require a container update whatsoever. Additionally, all of my linuxserver.io dockers are independent from the apps themselves. So if the guys at linuxserver change something about how the docker itself works, there is an update. But if, for example, Plex itself has an update available, it will just automatically install the next time the container is restarted. The container itself doesn't need to be updated in that scenario.

If this close to stable? I'm getting daily updates for the container itself, and it's starting to get old.

Exactly this is happening to me. I can restart the docker and the passwords and users will stay as I configured them, but if i simply go to the docker container edit page and press save, the user/passwords changed via telnet will reset, but everything on the webgui itself will stay as it was. Seems like a slight security concern

Any idea why this container is not getting updates? My install is at 0.12.19, but 0.12.21 is the latest release, as per https://github.com/syncthing/syncthing/releases. There doesn't seem to be any update functionality within the container itself. I have tried stopping and restarting the container, which works for other LinuxServer.io containers like Plex, but that's not working. My log shows: We are now refreshing packages from apt repositorys, this *may* take a while Update: ERROR Edit: Nevermind. I just deleted it and reinstalled, and now I'm at 0.12.21

The new Apple TV has a very nice Plex App. The third gen apple TV cannot be jailbroken, but the first 2 can. I'd just get the new one though, if that's the issue. Take a look, it's probably the best looking Plex app: https://blog.plex.tv/2015/11/02/plex-on-the-new-apple-tv/ and https://plex.tv/appletv Plus, then all of her progress on shows and movies would by synced across all devices she may use to watch on.

Why not just use something like Plex or Emby?

Restart the plex container

Is there any way to know when the software in a docker (The image?) has an update available? The Docker page only checks for container updates, but that isn't the same thing. I'll sometimes open a container like Plex to have it tell me in the Plex WebUI that an update is available, which i get by restarting the container. Some sort of external notification or autoupdate would be nice. I know that is probably unfeasible, but if it is doable, I'd at least like to voice my desire for it. Thanks!

hi smashingtool, Do you see anything out of the ordinary in either unraid's or unbalance's logs ? The heart of the operation is an rsync command, any error it might come up with should be written to the log. But rsync can also slow down/pause with a failing disk. Let me know if you find any other evidence of what might have happened. I dont see any evidence of a failing disk. Otherwise, here's the main error i found in unBALANCE's logs: I: 2016/02/10 07:50:52 core.go:651: diskmv finished I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: Cannot stat file /proc/32071/fd/70: No such file or directory I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0] I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1) I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]

Thanks, It's great that you made that, I'll give it a shot. My only other question now is whether it's possible to pause or stop unBALANCE after you start it.

I tried to use this to empty a disk so I could format it. It should have finished overnight, but didn't. It stopped at 120 gigs. So this morning I set it to run again, and it stopped at 116 gigs, but ~120 gigs disappeared from my array. I checked my disk shares, and sure enough, the drive that was supposed to be emptied had copies of files that were also on other disks. So now I'm paranoid that I have a bunch of copies of files on various disks. Is that something that the built in unraid mover would ultimately fix? Or am I doomed to have to compare files over my 4 disks for a while?

Probably by editing the config.ini file

Once I added the ports it started working consistently. Before, it would randomly sync(using the relay servers, most likely!), but it never maintained a constant connection to other devices, and i went a few hours where nothing worked. Avoiding the relay servers is better anyway. Higher speeds, more direct of a connection. According to the documentation anyway.

Syncthing is set to listen at tcp://0.0.0.0:22000, both officially and in the config present for this docker. But the container template is not set to forward that. I installed Syncthing yesterday and it was great, but this morning it has had connection issues. I noticed this at that time, and was wondering if it should be a part of the template? There may be a great reason why it's not included, but I figured I would bring it up. Edit: The documentation says to also listen to 21027 with UDP, fwiw.

Did it leave out only the Annuals? Or just random issues?

Okay, so let's say you have a folder of issues for Saga. Open Mylar, and search for Saga in the top search bar. It should pull up lots of results. Go to page 2 and add the Saga with 32 issues. At this point, it should add the comic and scan your current comic folder and notice that you have issues of it.

Thank you. Due to that, I found out that the official Limetech BTSync docker was the culprit for me. It had created a 7GB log file since last night!

It wasn't my thing either until a friend of mine basically forced me to read one. If a Hunter S Thompson type character in a dystopian futuristic society dealing with politics and journalism and a corrupt government sounds interesting, definitely Transmetropolitan. That's what my friend had me read, and I was hooked within a few issues. It starts out slightly slow, but by the end of the third one, I liked it a lot. 60 total. Y - The Last Man is great. Basically, in the first issue (of 60 total), every male mammal on the planet dies except for 2, a guy and his pet monkey. Watching how society reacts to such a thing is explored while the main characters try to figure out what happened and why. Fables is a comic about a bunch of fairy tale and fable characters who had to flee their homelands and move to New York. 150 total. We3 is a short 3 issue comic about 3 prototype animal weapons who escape a test lab and try to survive. Emotional story with basically no spoken words. Saga is like a Star Wars and Romeo and Juliet-ish story mashed together. Unlike the above two, this is an ongoing story. Maus is the famous graphic novel that depicts living in Nazi Germany, but mice are the characters. I believe it is required reading in quite a few college courses these days.

There's lots of great non superhero comics/graphic novels for adults. Let me know if you want some recommendations or options

Another option is to search for the comics themselves and add them manually. Then it will scan the comics and see that you have them. Obviously this is painful if you have a ton of comics.

I've never used this or NZBMegasearch before, but I'm really glad to have access to it now. Thanks for making it!