mgranger

My processor load seems all over the place. Before I updated to 1.32 the load in zoneminder was 1 or 1.5 with my 4 cameras now after the update it seems closer to high 4 or middle 5's. This is with Mocord. If I set it to just record it does come down quite a bit (which makes sense) my first to cameras say they are at or below 2 fps within zoneminder. My 3rd camera says around 140 fps and the 4th is 1000 fps which is wrong. All are actually set at 2fps in the camera so not sure why they say they are so high.

I have not looked at any ne gr working issues yet but if I pull up the video feed of the camera from the website I get a feed no problem and at the same time I look at the zoneminder image and I am having a problem so it makes me think the network is not the issue. It seems like it is something in zoneminder/unraid somewhere.

I just deleted it and reinstalled and it is already failing. I am using ffmpeg and tcp. i didn't see anything that looks different/wrong but obviously something is off.

They are set at 2 fps on the camera

Is there a way to go back to the old repository before 1.32? I was just going to see if going back helped fix the issue.

Ok i took the SHMEM% to 25 and pinned 2,6 and 3,7. (Yes i am on 6.6) My /dev/shm went up to 35% which makes sense since i lowered the SHMEM% but I am still seeing the same problem on my images.

Ok i turned down the SHMEM% to 50% which was the default. My /dev/shm percent is hovering around 18% which seems good enough. I will try to pin some CPUs to zoneminder if I can figure it out.

This is what I am seeing. I restart the docker and it seems to fix it for awhile but then it eventually goes to this or sometimes worse. This happens to all 4 of my cameras or sometimes just a portion of them. I have already increased the SHMEM to 60% (I have 32 GB on the system)

So i updated to the new 1.32.2 and now I am having issues with the images being blurry. The update before the new layout i didn't have any problems with the blurry images. Is there something that changed that is causing this?

I figured it out. In my default ovpn file i had to list out the password.txt file next to authentication line. Seemed to fix it.

When i use the transmission_vpn i keep getting the following error Using OpenVPN provider: NORDVPN Starting OpenVPN using config default.ovpn Setting OPENVPN credentials... adding route to local network 192.168.1.0/24 via 172.17.0.1 dev eth0 Wed Sep 26 04:42:04 2018 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018 Wed Sep 26 04:42:04 2018 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed Sep 26 04:42:04 2018 neither stdin nor stderr are a tty device and you have neither a controlling tty nor systemd - can't ask for 'Enter Auth Username:'. If you used --daemon, you need to use --askpass to make passphrase-protected keys work, and you can not use --auth-nocache. Wed Sep 26 04:42:04 2018 Exiting due to fatal error

No I did not but that seemed to fix it. Thanks

I have been trying to get nextcloud set up with a reverse proxy with the spaceinvader tutorial however when I do this I keep getting a '500 internal server error' I take a look in the error.log and there is nothing there. What could I be doing wrong? Here is my nextcloud.subdomain.conf: # make sure that your dns has a cname set for nextcloud # edit your nextcloud container's /config/www/nextcloud/config/config.php file and change the server address info as described # at the end of the following article: https://blog.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/ server { listen 443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud nextcloud; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:443; } } Here is my config.php file: I changed my url from what it actually is to test.: <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'oc5vpjwh780k', 'passwordsalt' => 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', 'secret' => 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', 'trusted_domains' => array ( 0 => '192.168.1.100:448', 1 => 'nextcloud.test.com', ), 'overwrite.cli.url' => 'https://nextcloud.test.com', 'overwritehost' => 'nextcloud.test.com', 'overwriteprotocol' => 'https', 'dbtype' => 'mysql', 'version' => '13.0.5.2', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.100:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'user', 'dbpassword' => 'XXXXXXXXXXXXXXX', 'installed' => true, );

I am getting an issue where one or two of my cameras seem to be failing quite often. I don't think my system is overloaded but something seems to be happening. I only have 4 cameras that I am using and 32 GB of RAM which I am sharing 65%. My "South Cam Day" seems to be dropping intermittently as well as my "Driveway Cam Day" Here is a portion of my log file. Not sure if anyone on here can help me out. zm-log1.txt

I went back to 0.61.1 and it seems to be working so it must be something changed within the docker which causes the error. Edit: Well i am still getting the error in 0.61.1 however it seems to be less often and the automation seems to still work probably because it doesn't cut out as often and not at the time it was running the automation. Not sure why it seems better in 0.61.1 but it does seem a little better

I am having a lot of issues with this container. The honeywell component went seem to stay connected 2018-04-14 09:06:34 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: 2018-04-14 09:06:34 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: 2018-04-14 09:06:34 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: 2018-04-14 09:52:52 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: ContentTypeError("0, message='Attempt to decode JSON with unexpected mimetype: '",) 2018-04-14 10:06:43 ERROR (SyncWorker_7) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:16:45 ERROR (SyncWorker_37) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:26:48 ERROR (SyncWorker_34) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:30:19 ERROR (SyncWorker_22) [homeassistant.core] Error doing job: Task was destroyed but it is pending! 2018-04-14 10:30:19 ERROR (SyncWorker_22) [homeassistant.core] Error doing job: Task exception was never retrieved RuntimeError: cannot reuse already awaited coroutine 2018-04-14 10:36:47 ERROR (SyncWorker_16) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 10:56:51 ERROR (SyncWorker_11) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:06:52 ERROR (SyncWorker_7) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:26:56 ERROR (SyncWorker_36) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:46:33 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.dark_sky_precip_intensity is taking over 10 seconds 2018-04-14 11:46:54 WARNING (MainThread) [homeassistant.components.sensor] Updating darksky sensor took longer than the scheduled update interval 0:00:30 2018-04-14 11:47:00 ERROR (SyncWorker_31) [homeassistant.components.climate.honeywell] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) 2018-04-14 11:51:35 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.pws_precip_today_in is taking over 10 seconds 2018-04-14 11:51:35 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError() 2018-04-14 14:00:29 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.pws_feelslike_f is taking over 10 seconds 2018-04-14 14:00:29 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError() 2018-04-14 14:36:34 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.pws_temp_high_record_f is taking over 10 seconds 2018-04-14 14:36:34 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()

Are there supposed to be python packages with Home Assistant in Unraid. I looked at my deps/lib/python3.6 folder is something I added for my Sony TV. When I used home assistant prior to unraid there were a lot more folders in here. I copied my files over however did not copy the python folder over which was 3.5. I thought this would populate automatically however nothing is showing up. I am getting errors for my honeywell thermostat and myq garage door and a chromecast and I was wondering if it was related to not having these python files.

Well I looked into it a little more. It may not have been as bad as I thought It looks like my CPU went up 4%-5% when I was running pihole which seems like quite a bit for what it is doing though.

When I use pihole my cpu usage goes way up. is this normal?

Well so I made the database using the command line but when i try to find the database in my appdata/influxdb folder it is not there; but it is there when i use SHOW DATABASE from the command line. Edit: Nevermind I also figured this out. My home-assistant had to point to my IP address rather than localhost. Then it was created in my appdata/influxdb

Sorry i am still learning but how do you command line into a docker? Edit: Nevermind I figured it out.

Is there a way to create a blank database. I am trying to set this up with Home-Assistant but it requires the database to be setup already and I can't figure out how to do this in InfluxDB Docker. I tried the following in terminal but it didn't create a database. $ docker run --rm -e INFLUXDB_DB=home_assistant influxdb /init-influxdb.sh

Well I am not even an amateur on this. Is there a good place to read up more on this. All I have right now is a duckdns. I do have my own domain though but have never set that up for websites although I don't know if this is possible to set up for websites/letsencrypt. I would like to figure this out but not sure where to start. I am sure this is outside the scope of this forum but would take any advice on where to start.

@DZMM I got it to work with your information. I was trying to follow the reverse proxy instructions using https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/ however it did not have information to use Home Assistant however when I used something similar for the home assistant line it did not work. I was hoping to be able to use some of these and add home assistant to it however that did't seem to work. Here is the default file from the above guide. upstream backend { server 192.168.1.3:19999; keepalive 64; } server { listen 443 ssl default_server; listen 80 default_server; root /config/www; index index.html index.htm index.php; server_name _; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; location = / { return 301 /htpc; } location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:8989/sonarr; } location /radarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:7878/radarr; } location /htpc { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:8085/htpc; } location /downloads { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.3:8112/; proxy_set_header X-Deluge-Base "/downloads/"; } #PLEX location /web { # serve the CSS code proxy_pass http://192.168.1.3:32400; } # Main /plex rewrite location /plex { # proxy request to plex server proxy_pass http://192.168.1.3:32400/web; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.1.3:444/nextcloud; } location ~ /netdata/(?<ndpath>.*) { proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://backend/$ndpath$is_args$args; proxy_http_version 1.1; proxy_pass_request_headers on; proxy_set_header Connection "keep-alive"; proxy_store off; } } UPDATE: It seemed to work when I brought those locations into @DZMM default above.

This is probably an easy question but I am learning. I have set up home assistant and I have configured Let's Encrypt to give me a cert so that I am able to access Home Assistant using a DDNS however I am not sure how I get my configuration.yaml to point to the cert and key file which reside in the Let's Encrypt container. I tried setting up a Host Path from Home Assistant but I don't think I did this correctly.