Diode663

My Node Red docker recently got borked. It looks like a permissions issue. > [email protected] start > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" 15 Jul 07:53:58 - [info] Welcome to Node-RED =================== 15 Jul 07:53:58 - [info] Node-RED version: v3.0.0 15 Jul 07:53:58 - [info] Node.js version: v16.16.0 15 Jul 07:53:58 - [info] Linux 5.15.46-Unraid x64 LE 15 Jul 07:53:59 - [info] Loading palette nodes 15 Jul 07:54:03 - [info] Dashboard version 3.1.7 started at /ui 15 Jul 07:54:03 - [error] Failed to start server: 15 Jul 07:54:03 - [error] Error: EACCES: permission denied, unlink '/data/.config.nodes.json.backup' root@NAS:/mnt/user/appdata/nodered# ls -all total 228 drwxr-xr-x 1 nobody users 4096 Jun 14 15:55 ./ drwxrwxrwx 1 nobody users 4096 Jun 4 05:32 ../ -rw-r--r-- 1 nobody users 30855 Jun 4 05:49 .config.nodes.json -rw-r--r-- 1 nobody users 30232 Jun 4 05:49 .config.nodes.json.backup -rw-r--r-- 1 nobody users 95 Jun 4 05:32 .config.runtime.json -rw-r--r-- 1 nobody users 543 Jun 4 05:33 .config.users.json -rw-r--r-- 1 nobody users 468 Jun 4 05:33 .config.users.json.backup -rw-r--r-- 1 nobody users 10360 Jun 14 15:55 .flows.json.backup -rw-r--r-- 1 nobody users 79 Jun 4 05:53 .flows_cred.json.backup drwxr-xr-x 1 nobody users 83 Jun 4 05:49 .npm/ -rw-r--r-- 1 nobody users 10366 Jun 14 15:55 flows.json -rw-r--r-- 1 nobody users 107 Jun 4 05:53 flows_cred.json drwxr-xr-x 1 nobody users 19 Jun 4 05:32 lib/ drwxr-xr-x 1 nobody users 20480 Jun 4 05:49 node_modules/ -rw-r--r-- 1 nobody users 67713 Jun 4 05:49 package-lock.json -rw-r--r-- 1 nobody users 440 Jun 4 05:49 package.json -rw-r--r-- 1 nobody users 20498 Jun 4 05:32 settings.js I tried doing a chmod 777 but Im not able to start the container I tried setting the extra parameters flag to --user nobody and that allowed the docker to start but all my flows are missing and I cannot install any nodes. Im not sure where to go from here and any help would be appretiated.

Has anyone found a way around the mongodb problems?

I tried to go back to the latest repository and that wont start at all. I deleted my docker image and started over and still the same result. I get the following error: 2018-10-04 22:14:54.888756 [warn] PUID not defined (via -e PUID), defaulting to '99' 2018-10-04 22:14:54.969258 [warn] PGID not defined (via -e PGID), defaulting to '100' 2018-10-04 22:14:55.023655 [info] Setting permissions recursively on volume mappings... chown: cannot read directory '/var/lib/unifi-video/videos/2ee90163-4814-39bf-aaea-9d89b94246c6/2018/08/26': Structure needs cleaning There isnt anything in the directory as I deleted everything to start completely fresh. I have no idea where I am supposed to go from here. It looks like there is some configuration somewhere left from the previous docker but I have no idea where since I deleted the appdata folder and the whole docker image for everything.

Any updates on how to fix mongodb? Wired tiger isnt supported by the unifi nvr

I pulled the latest beta and this is what the error log shows: 1538543889.216 2018-10-03 01:18:09.216/EDT: ERROR [uv.db.svc] Failed to acquire client connection Interrupted while waiting to connect in MongoDb-Connecting 1538543899.217 2018-10-03 01:18:19.217/EDT: ERROR [uv.db.svc] Failed to acquire client connection Timed out after 10000 ms while waiting to connect. Client view of cluster state is {type=Unknown, servers=[{address=127.0.0.1:7441, type=Unknown, state=Connecting, exception={com.mongodb.MongoException$Network: Exception opening the socket}, caused by {java.net.ConnectException: Connection refused (Connection refused)}}] in MongoDb-Connecting This is from the mongo log: 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] MongoDB starting : pid=4628 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=8ff897d7fbb2 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] db version v3.4.17 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] git version: 7c14a47868643bb691a507a92fe25541f998eca4 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2n 7 Dec 2017 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] allocator: tcmalloc 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] modules: none 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] build environment: 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] distmod: ubuntu1604 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] distarch: x86_64 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] target_arch: x86_64 2018-10-03T01:18:22.710-0400 I CONTROL [initandlisten] options: { config: "/usr/lib/unifi-video/conf/mongodv3.0+.conf", net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, operationProfiling: { mode: "off", slowOpThresholdMs: 500 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", engine: "mmapv1", journal: { enabled: true }, mmapv1: { preallocDataFiles: true, smallFiles: true }, syncPeriodSecs: 60.0 }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } } 2018-10-03T01:18:22.743-0400 I STORAGE [initandlisten] exception in initAndListen: 28662 Cannot start server. Detected data files in /usr/lib/unifi-video/data/db created by the 'wiredTiger' storage engine, but the specified storage engine was 'mmapv1'., terminating 2018-10-03T01:18:22.743-0400 I NETWORK [initandlisten] shutdown: going to close listening sockets... 2018-10-03T01:18:22.743-0400 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-7441.sock 2018-10-03T01:18:22.743-0400 I NETWORK [initandlisten] shutdown: going to flush diaglog... 2018-10-03T01:18:22.743-0400 I CONTROL [initandlisten] now exiting 2018-10-03T01:18:22.743-0400 I CONTROL [initandlisten] shutting down with code:100 It looks like the old db was stored as wiredtiger but it isnt converting it.

It just said that the connection timed out. I tried the first command but it comes up as mongo not found. Is it possible i just didnt wait long enough for the DB to convert? The docker log didnt really give me any indication that something was actually happening. I was on the previous beta and pulled down new docker about an hour ago and it seemed to be stuck on upgrading maybe I will try it again since i tried to go back to the latest branch and broke everything.

I am afraid I have no experience with mogodb. I looked at the logs and as you said mongo was just in a restart loop.

I keep hanging when upgrading to 3.10 beta 1. On the website it just shows updating forever. Looking over at the beta forums it seems to be a common problem.

Just something to think about, I swore up and down that port 80 wasnt blocked by my isp because I got on the phone with them a few months ago and had them open it up. Well I checked again and sure enough it was closed. it got reset for some reason or another, so make doubly sure that it is open, especially if Optimum is your isp. Also I must have updated my docker 5 minutes after you posted the new version because I dont see any talk of the new fields, notably the validation field. But after forcing an update everything works. Thank you guys. Is this container capable of forwarding to a service on a different ip? I would like to add my idrac but its on a different ip/ adapter. If this is possible are there any examples?

Im going nuts over here. I have had plex up and running perfectly for months. Now something has changed and I am not sure if its a cert thing or not. Last night my friend couldnt reach my server, but I could reach it from my phone not on wifi and at my work computer. Plex also showed that it was accessible from outside my network. Now it shows that the remote connection is no longer accessible. I can access it outside my network. and when I try to connect I get a NET::ERR_CERT_COMMON_NAME_INVALID error. Im not sure if this has to do with my reverse proxy or plex or something else. I updated and restarted my edgerouter x, I checked updates on plex and the letsencrypt docker. I checked to make sure requests were going through the firewall and they were as they always have been. I am not sure where the problem lies. Anyone else having this issue? #PLEX location /web { # serve the CSS code proxy_pass http://192.168.1.5:32400; } # Main /plex rewrite location /plex { # proxy request to plex server proxy_pass http://192.168.1.5:32400/web; } This is the plex related section of my default file for nginx

The other day I happened to check out my unraid dashboard and noticed my cpu was stuck at 50% and my system was chugging down nearly 200 watts. I checked out netdata to try to find the culprit. I noticed it was my win 10 vm and it had been like that for hours. Well I used vnc to see what was going on and it had blue screened. So I restarted the vm and all was well. I'm wondering if there is a watchdog to restart the vm if it becomes unresponsive so it doesn't double my power usage without me noticing for long periods of time. Sent from my SM-G930V using Tapatalk

Another vote for iscsi. For pretty much all of the use cases that were stated. It would be nice to carve out a section of the cache for a target.

that explains it. thank you for all of your hard work.

I have my backups set to run at 3 am every day but it doesn't automatically run. It only works when I do a manual backup. Any ideas?

So here is what i tried: I disabled HTTPS then restarted - wont load the gui I changed the HTTPS port and restarted - wont load the gui Is there something I am missing here?