rlust

I am running Unify video recorder, that is using a lot of space on that image. I need to limit the amount of stored recordings, I guess.

I got it working, found a network issue! Thanks for the quick reply!!!

Something happened this morning and I cannot connect to unread via the web. I have attached my diagnostics file. I can login to console fine. tower-diagnostics-20181125-1057.zip

The logs say the docker has started but the web ui does not launch. 2018-09-22 16:17:11.963238 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin 2018-09-22 16:17:12.025949 INFO AppDaemon: HASS: HASS Plugin Initializing 2018-09-22 16:17:12.027045 INFO AppDaemon: HASS: HASS Plugin initialization complete 2018-09-22 16:17:12.027933 INFO Dashboards are disabled 2018-09-22 16:17:12.028271 INFO API is disabled 2018-09-22 16:17:12.139871 INFO AppDaemon: HASS: Connected to Home Assistant 0.78.2 2018-09-22 16:17:13.477726 INFO AppDaemon: Got initial state from namespace default 2018-09-22 16:17:14.411105 INFO AppDaemon: Reading config 2018-09-22 16:17:14.421794 INFO AppDaemon: /conf/apps/apps.yaml added or modified 2018-09-22 16:17:14.422239 INFO AppDaemon: /conf/apps/apps.yaml added or modified 2018-09-22 16:17:14.422697 INFO AppDaemon: App 'hello_world' added 2018-09-22 16:17:14.424687 INFO AppDaemon: Adding /conf/apps to module import path 2018-09-22 16:17:14.427733 INFO AppDaemon: Loading App Module: /conf/apps/hello.py 2018-09-22 16:17:14.474109 INFO AppDaemon: Initializing app hello_world using class HelloWorld from module hello 2018-09-22 16:17:14.760391 INFO hello_world: Hello from AppDaemon 2018-09-22 16:17:14.763923 INFO hello_world: You are now ready to run Apps! 2018-09-22 16:17:14.765986 INFO AppDaemon: App initialization complete

I have an instance that is running on a Rasp Pi that I have been able to backup and restore to a 3rd system on a OSX MAC several times. I think that there is a permission issue, but not sure where to look.

I am trying to restore a DB from another Domoticz install and getting the following error in the logs: 2017-11-14 09:00:02.684 Error: Restore Database: Could not open backup file for writing!

I am getting the follow message in the log file when starting. The file is in .homebridge. Why is the file not being found? /root/install_plugins.sh: line 7: /root/.homebridge/pluginsInstallList: No such file or directorymv: cannot stat ‘/root/.homebridge/pluginsInstallList’: No such file or directory

Does anyone have an idea on how to set permissions to allow backup and restore.

How do I check user permissions? The Domoticz is located in appdata on my cache drive.

Cannot restore database Error Restore Database: Starting...domoticz: Restore Database: Starting...Error: Restore Database: Could not open backup file for writing!domoticz: Error: Restore Database: Could not open backup file for writing!

How do I upgrade the image to the latest version of node-red? I have tried to use force update but still on 14.6.

Looks like I fixed the issues by moving my docker image file to disk1

Also getting these error messages: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 490 Couldn't create socket: [111] Connection refused

Any ideas here? ower root: mount: /mnt/cache/docker.img is already mounted Jul 5 12:54:01 Tower root: mount error Jul 5 12:54:01 Tower emhttp: shcmd (58133): /etc/rc.d/rc.docker start |& logger Jul 5 12:54:01 Tower root: starting docker ... Jul 5 12:55:01 Tower root: mount: /mnt/cache/docker.img is already mounted Jul 5 12:55:01 Tower root: mount error

Here is a screen shot, I do not have advanced tab. Thanks!

Docker tab missing Have deleted docker image a few times and restarted but still error 0:01 Tower root: mount: /mnt/cache/docker.img is already mounted Jul 4 12:00:01 Tower root: mount error Jul 4 12:00:01 Tower emhttp: shcmd (2152): /etc/rc.d/rc.docker start |& logger Jul 4 12:00:02 Tower root: starting docker docker.cfg tower-diagnostics-20160704-1205.zip

Found the problem, I had a dir directory hanging the unmount process, I removed it and it shutdown. The new config worked on assigning the drives back!! Parity is rebuilding, so far so good! Thanks

I am stuck in a loop of constant "unmounting user shares" prior to running the tool thanks for the reply!

I rebooted and my parity disk and largest data disk are now unassigned. Not shure what to do next. Thanks tower-diagnostics-20160702-1907.zip tower-syslog-20160702-1839.zip tower-smart-20160702-1815.zip

Thanks for the help my parity disk is rebuilding as we speak

I have this same issue, parity disk is disabled but Smart Test looks fine. Started a few days ago. I am on 6.1.1. Looking forward to others results.

Here is the syslog. Thanks! syslog.txt

I started with safe mode and after 20 hours I got the following message on my attached terminal session. essage from syslogd@Tower at Tue Dec 31 03:40:17 2013 ... Tower kernel: Process fuser (pid: 4541, ti=ef9c4000 task=f2d86be0 task.ti=ef9c4000) Message from syslogd@Tower at Tue Dec 31 03:40:17 2013 ... Tower kernel: Stack: Message from syslogd@Tower at Tue Dec 31 03:40:17 2013 ... Tower kernel: Code: 8b 5b 04 39 f3 75 04 31 c0 eb 11 8b 7b 08 83 c7 10 39 f8 75 e3 39 53 0c 75 de 89 d8 5b 5e 5f 5d c3 55 85 c0 89 e5 74 06 8b 50 0c <64> ff 02 5d c3 55 89 c1 89 e5 83 ea 2c ff 51 54 5d c3 55 89 e5 Message from syslogd@Tower at Tue Dec 31 03:40:17 2013 ... Tower kernel: EIP: [<c10aa450>] mntget+0xa/0xf SS:ESP 0068:ef9c5df0 Message from syslogd@Tower at Tue Dec 31 03:40:17 2013 ... Tower kernel: Call Trace: Any ideas on where to look next? Thanks!

I am still having kernel panics, every 8-16 hours. I removed every process down to basic, as suggested and it is still happening I have a terminal window open and captured the following messages. Does this help? root@Tower:~# Message from syslogd@Tower at Sun Dec 29 03:40:52 2013 ... Tower kernel: Process fuser (pid: 31863, ti=edef8000 task=f2dee880 task.ti=edef8000) Message from syslogd@Tower at Sun Dec 29 03:40:52 2013 ... Tower kernel: Stack: Message from syslogd@Tower at Sun Dec 29 03:40:52 2013 ... Tower kernel: EIP: [<c140098e>] _raw_spin_lock+0x8/0x1f SS:ESP 0068:edef9df0 Message from syslogd@Tower at Sun Dec 29 03:40:52 2013 ... Tower kernel: Call Trace: Message from syslogd@Tower at Sun Dec 29 03:40:52 2013 ... Tower kernel: Code: c6 38 d0 75 17 8d 9a 00 01 00 00 89 d0 f0 66 0f b1 19 66 39 d0 b9 01 00 00 00 74 02 31 c9 89 c8 5b 5d c3 55 89 e5 ba 00 01 00 00 <f0> 66 0f c1 10 88 d1 66 c1 ea 08 38 d1 74 06 f3 90 8a 08 eb f6 Connection closed by foreign host. Thanks for any help! syslog-2013-12-29.txt

My system has been getting a kernel panic since I loaded 5.03. It works fine then after several hours it is locked up with a kernel panic message. Any ideas on how to troubleshoot this type of issue? Thanks Randy unraidlog.txt