MidPackPark

Yes! That was it. My scheduler never seems to work when it should. Thank you for such a quick response

This app has worked great for years. Long time user. All of the sudden it will not stay started. It also states there is an update available, will go through the process until "done" but still keeps saying there is an update. I am not super technical however I looked into the setting and don't see anything abnormal. Please help. Thank you! LOG: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] 10-certs.sh: executing... [cont-init.d] 10-certs.sh: exited 0. [cont-init.d] 10-cjk-font.sh: executing... [cont-init.d] 10-cjk-font.sh: exited 0. [cont-init.d] 10-nginx.sh: executing... [cont-init.d] 10-nginx.sh: exited 0. [cont-init.d] 10-vnc-password.sh: executing... [cont-init.d] 10-vnc-password.sh: exited 0. [cont-init.d] 10-web-index.sh: executing... [cont-init.d] 10-web-index.sh: exited 0. [cont-init.d] crashplan-pro.sh: executing... [cont-init.d] crashplan-pro.sh: setting CrashPlan Engine maximum memory to 8192M sh: write error: No space left on device [cont-init.d] crashplan-pro.sh: exited 1. [services.d] stopping services [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] 10-certs.sh: executing... [cont-init.d] 10-certs.sh: exited 0. [cont-init.d] 10-cjk-font.sh: executing... [cont-init.d] 10-cjk-font.sh: exited 0. [cont-init.d] 10-nginx.sh: executing... [cont-init.d] 10-nginx.sh: exited 0. [cont-init.d] 10-vnc-password.sh: executing... [cont-init.d] 10-vnc-password.sh: exited 0. [cont-init.d] 10-web-index.sh: executing... [cont-init.d] 10-web-index.sh: exited 0. [cont-init.d] crashplan-pro.sh: executing... [cont-init.d] crashplan-pro.sh: setting CrashPlan Engine maximum memory to 8192M sh: write error: No space left on device [cont-init.d] crashplan-pro.sh: exited 1. [services.d] stopping services [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

Hello, All of the sudden I can no longer access my Deluge WebUI on the same LAN. I have tried restarting and still nothing. Logs keep repeating this message: 2018-09-17 11:37:25,943 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 3 retries left [info] Retrying in 10 secs... Any ideas on what I should try?

Any thoughts on this? Not sure what to do and I cannot access anything. Kinda screwed at the moment

I took two disks out to replace (I have two parity drives) and when I boot back up the CLI interface is fine but I cannot access GUI through the IP #. CLI Diagnostics file is attached Any ideas? unraid-diagnostics-20171202-1339.zip

Okay. That seemed to solve the problem....for now. Not sure what happened. I've been operating with bonded nic's since the beginning without any issues. Thank you very much for the help guys!!!

Is there a command I can send via SSH to un-bond the nic's? I tried unplugging one of the network cables but still have the same issue

This is the diagnostics file I can ping the server. It does seem to take an abnormally long time to boot up and I see a lot of errors spit out on the boot screen. tower-diagnostics-20171129-1236.zip

Sheesh. I was able to reboot but now I can't access the GUI. I've tried a few different computers and browsers. I can SSH in just fine so everything seems to be up and running. Thoughts?

Okay. So I tried unbonding the network connections and it says: VM manager and Docker service must be Stopped to change I tried stopping both the Docker service and VM manager in the settings but neither will stop and keep defaulting to yes (on)

My USB drive is 97% free according to Krusader

Any ideas? I'm a couple days away from having to purchase and cannot do that if I keep having this problem.

Well it happened again out of the blue. I reset and still get the same problem. Attached is the updated syslog.txt file syslog.txt

Okay back at this... The syslog.txt file is attached Everything seems to be working fine now. Weird. My boot device is only showing 166MB used. Thoughts? Is everything okay? syslog.txt

Does this screenshot help?