Ockingshay

This is what i get: *** Running /etc/my_init.d/config.sh... ownCloud is not installed - only a limited number of commands are available [invalidArgumentException] Command "upgrade" is not defined. Current default time zone: 'Europe/London' Local time is now: Tue Aug 18 17:59:51 BST 2015. Universal Time is now: Tue Aug 18 16:59:51 UTC 2015. Found pre-existing certificate, using it. /etc/my_init.d/config.sh: line 52: syntax error: unexpected end of file *** /etc/my_init.d/config.sh failed with status 2 *** Killing all processes...

Thanks worked for me. That's been very annoying for a very long time. It's a shame it hasn't been update yet.

You will also want to set container port and host port the same for each docker, if you want transmission to see the port as "open" Obviously choose a different port for each docker though (as mentioned above), otherwise you won't be able to load the webgui.

i've still not managed to successfully get dropbox to start without having to edit it first and then save "no changes" If i simply restart the docker, or reboot the log always shows this: *** Shutting down runit daemon (PID 25)... *** Killing all processes... *** Running /etc/my_init.d/config.sh... Continous console status not requested *** /etc/my_init.d/config.sh failed with status 1 is there a way to find out what status 1 is?

I got around this error by entering the plex server IP address again, even though it was correct and was communicating. After that I could adjust all the other settings and it would save. It happened after I did a plexwatch db import.

The good news is that you don't even need to have plex. It hooks in with sickrage and couchpotato or simply creates a list that you can use manually.

No, i just chose to be polite and not comment on the level of value you see in this request as it's irrelevant ok, ok, back to my hole for me! ...must be the Summer Solstice.

Thanks RobJ for the reply, i believe it was related to a faulting drive and not seen since swapping it. Strange that this error has never been documented on the wiki or forums before now though.

Not really...and hence the "as an example" My dockers are on the cache as well, but the data is on the array. If the docker is using the array data of course it will impact. I'm really not understanding the replies here. This is a feature request forum. If it's not something that will affect you, well great! If it's something that only a few users can benefit from it won't be implemented...rather simple really

Not necessary since the docker service can be stopped or individual dockers can be stopped, and same thing for VMs. Plugins on the other hand actually install things into unRAID that are still there even if the plugin is stopped. Not really the point to be honest. To have to manually stop the services defeats the purpose of going into safe mode. It's not so much the installation of things through the plugins that in the past would cause conflicts, but more about the resources being used when the array comes online. As an example... All my dockers came online despite the array having to rebuild as i swapped out a faulty drive. At the same time Transmission dockers (x4) hammered the drives as it did it's file checks and then Sickrage tried to run a backlog search. So perhaps you haven't had a scenario that would require it, but in some circumstances it certainly is necessary.

As the growing functionality of unRAID improved, safe mode was a great feature to allow the system to run at it's minimum. As that growth has now expanded into Dockers and VMs would it be possible to include these, as well as plugins? It's nice to be able to boot up into safe mode and only have unRAID running.

Having just checked my log, i've noticed a lot of these shfs/user: shfs_fallocate: fallocate: (95) Operation not supported Is it normal? something to be concerned about? Obviously if this isn't enough information i can run the new diagnostics button. Thanks

i just tried this for the first time and was a little surprised not to see anything in the mate docker variable boxes. I installed crash plan first and then mate and when i try to use MS RDP tool for mac, it just says it cannot connect. i used 192.168.0.3:3389 as my details. Is it as simple as install crash plan docker and then install mate docker and then try and connect to serverip:3389 with RDP?

I have the exact same complaint..... There should be some text or something in the overview section of the template to let users know the differences. Or alternatively authors could use the change log / more information section for the same purposes Not a complaint, constructive feedback!

Is there a way dockers that have multiple versions....for example SAB, mumble server etc,who have exactly the same description....can have some sort of definition as to the differences? I presume different authors use different base images, and/or different features applied, but as an end user it's unclear which one to choose.

I was referring to this: http://lime-technology.com/forum/index.php?topic=39028.0

Don't change the container port, change the host port. Ok, but apps like transmission will report the port as closed. Would it be just a gui thing and the port is actually open?

if 2 dockers use the same container port, is it as simple as changing the port number in the docker's "Port Mappings" section in the webgui?

Dropbox Never wants to start on it's own for me. If i reboot or stop and then start i get the following error: *** Killing all processes... *** Running /etc/my_init.d/config.sh... Continous console status not requested *** /etc/my_init.d/config.sh failed with status 1 To get it to work, i have to edit the docker (without actually editing anything), click "save", wait for it to attempt to pull down any new data (which there isn't any) and it's starts just fine. *** Running /etc/my_init.d/config.sh... Current default time zone: 'Europe/London' Local time is now: Fri Jun 5 15:31:44 BST 2015. Universal Time is now: Fri Jun 5 14:31:44 UTC 2015. Continous console status not requested *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 25 Jun 5 15:31:47 Ruby syslog-ng[31]: syslog-ng starting up; version='3.5.3' Therefore "Autostart" is useless for me, anything i'm missing here?

Thanks for the reply. it's rebuilding now. I think the webgui should be more informative on what the next steps one should take to get the array back to 100% healthy.

I started this in the RC3 announcement thread, but thought it would be better to move it out to a new post, so that i can get some advice on what to do next. I just added 4 new drives to my system, which meant getting into my server and adding cables etc. Monthly Parity ran and now it's showing as being in an invalid state. 3 email alerts received: Event: unRAID Disk 8 error Subject: Alert [RUBY] - Disk 8 in error state (disk dsbl) Description: WDC_WD30EFRX-68EUZN0_WD-WMC4N1534644 (sdk) Importance: alert Event: unRAID array errors Subject: Warning [RUBY] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 8 - WDC_WD30EFRX-68EUZN0_WD-WMC4N1534644 (sdk) (errors 4160) Event: unRAID Parity check Subject: Notice [RUBY] - Parity check finished (0 errors) Description: Error code: user abort <------ i didn't abort this (i was fast asleep) Importance: warning stopping the array showed me that unRAID can't find disk8, so it definitely dropped out. Well i've rebooted and the disk has been found and automatically put into slot 8, however it still has the grey triangle (and listed in the faulty row) against it and all i can do is stop and start the array. As it believes the parity is invalid i have no option run run a parity check. I can run a smart test on the drive and it completes without error. How do i get it out of error state? Subject: Alert [RUBY] - Disk 8 in error state (disk dsbl) I have a spare drive, but if my parity is bad, it won't be able to rebuild. The data on this drive is backed up, but there doesn't seem to be an obvious step to correct this issue. syslog.txt.zip

moved to it's own thread

Moved to it's own thread

Just a quick thank you for this plugin. Just added 4 new drives concurrently to my server and it completed perfectly.

But that would mean that I can't access the VM from the LAN... I'll try it, but that's no good.. I asked this question before and you can still access via lan. I'm doing it right now in fact. http://lime-technology.com/forum/index.php?topic=39343.msg366969#msg366969